Back to Home

datafeed

Token
0x65ede742c636...b7c3dc4e25fb
FrontierContract #1,014Exact Bytecode MatchEdit this contract
Deployed September 9, 2015 (11 years ago)Block 209,032

The datafeed example from the ethereum dapp-bin standardized contract APIs, a single owner key value oracle.

Frontier EraVerified Source

Historical Significance

The ethereum.org token tutorial is where most people who deployed a token in this period started, and this is its opening form: a balance mapping, a guarded subtraction and the metadata a wallet needs to show a name. It has no allowance, so nothing can spend on a holder's behalf and no exchange or escrow can be given a limit. That gap is exactly what ERC-20 was written to close, and copies like this one are the before picture.

Context

Deployed 9 September 2015, during the Frontier era.

Key Facts
Deployment Block
209,032
Deployment Date
Sep 9, 2015, 05:16 PM
Code Size
356.0 B
Gas at Deploy
120,095
Transactions by Year
20153

Description

The datafeed contract from the standardized contract APIs directory of the ethereum dapp-bin repository, one of the reference interfaces published so that early contracts could agree on how to read a price or a measurement from one another. The constructor records the deployer as owner. set takes a bytes32 key and a signed 256 bit value and writes it to storage when the caller is the owner; there is no else branch, so a call from anyone else succeeds and changes nothing. get returns the value stored under a key. get is declared as an ordinary function rather than a constant one, so a caller reading it through a transaction pays for the call even though it writes nothing.

Source Verified

Exact bytecode match(356 bytes)
Compiler: v0.1.1+
Heuristic Analysis

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

Detected Type: Token

Bytecode Overview

Opcodes356
Unique Opcodes51
Jump Instructions11
Storage Operations6

External Links

Related contracts