Back to Home

0x7dd6...5adf

Unclassified
Part of The Piper Merriam Collection
0x7dd677b54fc9...bdfa12c75adf
FrontierContract #8,761Exact Bytecode MatchEdit this contract

Bytecode verified via sibling

This contract shares identical runtime bytecode with a verified contract (0x5ef9a933...) which has been verified through compiler archaeology.

Deployed February 12, 2016 (10 years ago)Block 994,807

A heartbeat contract that proves the Ethereum Alarm Clock is still executing calls

Frontier EraVerified Source

Historical Significance

A liveness proof written as a contract rather than a status page. The deployed copy pays three ether per call where the published source pays two, which is the only difference between them.

Context

Deployed in the Homestead era, when Ethereum had no scheduled transactions of its own and a service had to be watched to be trusted.

Key Facts
Deployer
Piper Merriam(0xd3cda9...293601)
Deployment Block
994,807
Deployment Date
Feb 12, 2016, 10:22 PM
Code Size
1.2 KB
Gas at Deploy
351,107
Transactions by Year
20164

Description

CanaryV7 keeps one value, the timestamp of the last time it was poked. Each poke schedules the next one with the Alarm Clock and pays three ether for it, so as long as the service keeps executing scheduled calls the timestamp keeps moving. If it stops moving the service has stopped, and anyone can read that from the chain without trusting an operator. Deployed in February 2016 by 0xd3cda913deb6f67967b99d67acdfa1712c293601, the account of Piper Merriam, and recovered from pipermerriam/ethereum-alarm-clock.

Source Verified

Exact bytecode match(1,198 bytes)
Compiler: v0.2.0-
Heuristic Analysis

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

Detected Type: Unclassified

Bytecode Overview

Opcodes1,198
Unique Opcodes144
Jump Instructions58
Storage Operations30

External Links

Related contracts