Back to Home

MyToken

Token
0x65c4e65113db...cca9e66c5ed2
FrontierContract #322Source VerifiedEdit this contract
Deployed August 19, 2015 (11 years ago)Block 110,635

The first contract on Ethereum mainnet to carry transfer(address,uint256), deployed 19 August 2015. Balances live in a public mapping, and the transfer returns nothing and emits no event.

Frontier EraVerified Source

Historical Significance

Measured across every contract created on Ethereum mainnet from the Frontier launch on 30 July 2015, this is the first appearance of the function signature transfer(address,uint256), the one method ERC-20 would be built around. It arrives in block 110,635 on 19 August 2015, three months before ERC-20 was proposed as ethereum/EIPs issue #20 on 19 November 2015, and it is the barest possible form of the idea: a balance is moved and nothing else happens. There is no event, so nothing offchain can observe that a transfer occurred, and no return value, so a caller cannot tell success from failure. Closing those two gaps is most of what the standard later did.

Key Facts
Deployment Block
110,635
Deployment Date
Aug 19, 2015, 09:36 AM
Code Size
419.0 B
Gas at Deploy
134,142
Transactions by Year
20151

Description

Deployed 19 August 2015, three weeks after the Frontier genesis block. Balances live in a public mapping named balances. transfer(address,uint256) checks the sender's balance, returns silently when it is short, and otherwise subtracts and adds. It declares no return value and no event, so a caller has no way to observe whether the transfer happened except by reading balances again. Runtime 344 bytes, optimizer off.

Source recovered by compiling against solc v0.1.3+commit.028f561d, reproducing the deployed runtime exactly. The creation bytecode is not reproduced by any archived build: the contract predates every release in solc-bin, so the constructor was emitted by a development build that was never published. Etherscan compares the runtime, so the source verifies there regardless.

Source Verified

exact_runtime_bytecode_match
Compiler: v0.1.3+
Heuristic Analysis

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

Detected Type: Token

Bytecode Overview

Opcodes419
Unique Opcodes49
Jump Instructions12
Storage Operations9

External Links

Related contracts