Back to Home

0xbcbf...ab62

Utility
Part of The Piper Merriam Collection
0xbcbf4d2ce032...3b23a56eab62
FrontierContract #2,360Exact Bytecode MatchEdit this contract
Deployed October 22, 2015 (10 years ago)Block 419,862

The first Ethereum Alarm Clock, a single contract holding the whole scheduling service

Frontier EraVerified Source

Historical Significance

Nothing on Ethereum runs unless an account sends a transaction, so a contract cannot wake itself at a future block. This is the first shape the answer took, one contract holding the queue, the bonded callers and the accounting together. It was rebuilt within weeks as a scheduler that deploys a separate contract per call, so the pair of designs sits on chain side by side: the monolith, and the split that replaced it once the cost of holding everything in one contract became clear.

Context

Deployed in October 2015 on the Frontier chain. It reproduces exactly at the released solc v0.1.6 with the optimiser on, but Etherscan cannot verify it: the link time library addresses cannot be supplied for compilers of this vintage.

Key Facts
Deployer
Piper Merriam(0xd3cda9...293601)
Deployment Block
419,862
Deployment Date
Oct 22, 2015, 12:50 AM
Code Size
8.9 KB
Gas at Deploy
2,575,605
Transactions by Year
20157
20231
202625

Description

The original Ethereum Alarm Clock, before the design was split into a scheduler and one contract per call. A single contract holds the request queue, the bonded caller pool and the accounting. A contract that wants to be called later registers the target address, the call data, the block it is due at and the gas to forward; bonded callers take turns from a rotating pool, each getting an exclusive window on a scheduled call before it opens to anyone, and are reimbursed at the gas price anchored when the call was scheduled. Four libraries are linked in at deployment: AccountingLib for balances, GroveLib for the ordered index of upcoming calls, ResourcePoolLib for the caller rotation and ScheduledCallLib for the call lifecycle.

Source Verified

Exact bytecode match(9,114 bytes)
Compiler: v0.1.6+
Heuristic Analysis

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

Detected Type: Utility

Bytecode Overview

Opcodes9,114
Unique Opcodes245
Jump Instructions362
Storage Operations73

External Links

Related contracts