Back to Home

0x964c...879e

Token
Part of The Cyrus Adkisson Collection
0x964ce92fcb68...a9ce6233879e
FrontierContract #774Exact Bytecode MatchEdit this contract
Deployed September 3, 2015 (11 years ago)Block 179,566

The second incrementer from the solidity-baby-steps tutorials, written to show what a transactional call looks like from geth.

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 3 September 2015, during the Frontier era.

Key Facts
Deployer
Cyrus Adkisson(0xcf684d...ad1bac)
Deployment Block
179,566
Deployment Date
Sep 3, 2015, 12:04 PM
Code Size
1.3 KB
Gas at Deploy
392,479
Transactions by Year
20154

Description

Example 21 of the solidity-baby-steps tutorial series, deployed by the author of the series. increment takes an amount and adds it to a counter, writing a short status string into storage as it goes so that the caller can tell from geth which branch ran. The source carries the geth command line it was written to demonstrate. Anyone can call increment; the creator address is recorded but never checked.

Source Verified

Exact bytecode match(1,363 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

Opcodes1,363
Unique Opcodes111
Jump Instructions78
Storage Operations33

External Links

Related contracts