Back to Home

Alarm

Wallet
Part of The Piper Merriam Collection
0x07307d0b136a...d706389c4588
FrontierContract #2,541Source VerifiedEdit this contract
Deployed October 23, 2015 (10 years ago)Block 429,088

The first scheduled-transaction service on Ethereum, enabling smart contracts to schedule future function calls—deployed by Piper Merriam in October 2015.

Frontier EraVerified Source

Historical Significance

The Ethereum Alarm Clock was the first on-chain transaction scheduler on Ethereum, introducing the keeper/automation pattern that became foundational to DeFi. It demonstrated that arbitrarily complex Solidity libraries could be deployed on Frontier mainnet.

Context

October 2015 was Ethereum's Frontier era. Smart contract development was nascent—the Solidity compiler was at v0.1.6, geth was the primary client, and the absence of native scheduling was already a pain point for developers wanting to build time-dependent applications such as auctions, subscriptions, or options contracts.

Key Facts
Deployer
Piper Merriam(0xd3cda9...293601)
Deployment Block
429,088
Deployment Date
Oct 23, 2015, 08:45 PM
Code Size
8.9 KB
Gas at Deploy
2,575,605
Transactions by Year
201510
20164
20171
20233
20251
202622

Description

The Ethereum Alarm Clock (contract name: Alarm) was deployed at block 429,088 (October 23, 2015) by Piper Merriam, whose Ethereum address 0xd3cda913deb6f67967b99d67acdfa1712c293601 is hard-coded into the protocol's documentation as the default donation benefactor. The contract introduced a primitive but functional scheduler for the Ethereum Virtual Machine: by paying a small deposit, any account or contract could register a future block height at which a target function should be called. A network of "callers"—independent keepers—would monitor pending calls and execute them in exchange for a bounty drawn from the deposit.

The contract's source code, compiled with Solidity v0.1.6, shipped with a complete suite of utility libraries authored by Merriam himself: StringLib (integer-to-string conversion), a custom AccountingLib, and a SchedulerLib—together comprising more than 90,000 bytes of verified Solidity source. This made it one of the largest and most modular Solidity codebases deployed on Ethereum mainnet in the Frontier era, and an early demonstration that real application logic could live entirely on-chain.

The Ethereum Alarm Clock addressed a fundamental limitation of smart contracts: they cannot initiate actions autonomously. Without an external trigger, a contract can only respond to incoming transactions. Merriam's solution prefigured the modern "keeper" and "gelato" automation ecosystems that would emerge years later. The v0.7 deployment at block 429,088 was a mature iteration of the service; the project's GitHub shows active development from at least August 2015.

The project continued through multiple versions. Later iterations of Ethereum Alarm Clock (EAC) would influence Chainlink Automation, Gelato Network, and other scheduling protocols. The donationBenefactor constant in v1.0's documentation still points to Merriam's address, a direct link between the 2015 Frontier-era deployment and the modern codebase.

Source Verified

Etherscan verified
Heuristic Analysis

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

Detected Type: Wallet

Bytecode Overview

Opcodes9,114
Unique Opcodes246
Jump Instructions362
Storage Operations73

External Links