Back to Home

0x321a...d8de

Utility
Part of The Piper Merriam Collection
0x321a1e5e0ef1...d60ab9dcd8de
FrontierContract #3,581Exact Bytecode MatchEdit this contract
Deployed November 8, 2015 (10 years ago)Block 508,899

The Ethereum Alarm Clock entry point, which creates one contract per scheduled call

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 door onto the service that answered that: a contract pays in advance to be called later, and whoever sends the transaction at the right block collects the fee. Giving each scheduled call its own funded contract, rather than a row in a table, means the money for a call is held by the call, which is what makes the promise enforceable without trusting the scheduler.

Context

Deployed in November 2015 on the Frontier chain by the account behind the Ethereum Alarm Clock, which deployed the whole system from one address. It reproduces exactly at the released solc v0.1.6+commit.d41f8b7c 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
508,899
Deployment Date
Nov 8, 2015, 12:41 PM
Code Size
4.6 KB
Gas at Deploy
1,308,576
Transactions by Year
20155
20162

Description

The public face of the Ethereum Alarm Clock. A contract that wants to be called at a future block calls the scheduler with the target block, the gas to forward, the payment and the call data, and the scheduler deploys a dedicated call contract funded with the ether it was sent. It keeps the queue of upcoming calls in an ordered index so that callers can find what is due, and it holds the default fees and the window in which a call may be claimed. The scheduling logic is in the linked SchedulerLib and the ordered index in GroveLib.

Source Verified

Exact bytecode match(4,709 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

Opcodes4,709
Unique Opcodes215
Jump Instructions217
Storage Operations23

External Links

Related contracts