Back to Home

TimeLockVault

Wallet
0xed44f3c20814...fab9ed643735
FrontierContract #5,453Source VerifiedEdit this contract
Deployed December 20, 2015 (10 years ago)Block 719,439

A 2015 time-lock vault: deposit ETH to lock it ~20 years, withdraw after it expires.

Frontier EraVerified Source

Historical Significance

Early example of a self-custody time-lock vault on Ethereum, known in community lore for its long lock period and sizeable balance.

Context

In December 2015, Ethereum was five months old and Solidity was at version 0.1.x. Formal auditing practices, security tooling, and established patterns for time-locked contracts did not yet exist. Developers were experimenting directly with on-chain logic without the benefit of later community knowledge around common pitfalls. The concept of a personal time-lock savings vault was a natural early experiment, and several variations appeared in this period. The absence of testnets in common use and the experimental culture of the time meant that contracts with subtle logical errors were regularly deployed to mainnet with real ETH.

Key Facts
Deployment Block
719,439
Deployment Date
Dec 20, 2015, 06:47 AM
Code Size
459.0 B
Gas at Deploy
157,585
Transactions by Year
20151
20171
201810
20232
20252
20267

Description

Send ETH to lock it for a fixed duration (~20 years); send a 0-value transaction (or call withdraw()) to take it back once the lock expires. One active lock per address. Source reconstructed from the 433-byte on-chain runtime: compiling with solc v0.1.7 (optimizer ON) yields exactly 433 bytes with the same physical function-body layout and 12 of 14 internal blocks byte-identical, including the full withdraw guard (balance>0 && unlockTime>0 && now>unlockTime). The residual is a ~3-opcode optimizer stack-scheduling artifact of the exact original build.

Source Verified

source_reconstructed

Source reconstructed from on-chain runtime. solc v0.1.7 (optimizer ON) -> 433/433 bytes, exact body order, 12/14 bodies byte-identical; residual ~3 opcodes of optimizer stack-scheduling.

Heuristic Analysis

The following characteristics were detected through bytecode analysis and may not be accurate.

Detected Type: Wallet

Bytecode Overview

Opcodes459
Unique Opcodes69
Jump Instructions23
Storage Operations17

External Links

Related contracts