Back to Home

Standard_Token

Token
0xdc3153c4a6bd...4e7b1ca8f965
FrontierSource VerifiedEdit this contract
Deployed August 13, 2015 (11 years ago)Block 81,666

A token built to the pre-ERC-20 Standardized Contract APIs, with sendCoin and coinBalanceOf in place of transfer and balanceOf.

Frontier EraVerified Source

Historical Significance

Written before ERC-20 was proposed, when the shared vocabulary for tokens was the wiki page on Standardized Contract APIs. The names it uses, sendCoin and coinBalanceOf, are the ones that transfer and balanceOf replaced, and the approve mechanism here predates the allowance triple that became the standard. It shows what a token interface looked like while the question was still open.

Context

Ethereum's Frontier network went live on 30 July 2015. The chain carried almost no applications in its first months: what was deployed was mostly tutorial code, token experiments and registries, written in a Solidity that was itself only a few months old and compiled from the geth console.

Key Facts
Deployment Block
81,666
Deployment Date
Aug 13, 2015, 10:40 PM
Code Size
3.0 KB
Transactions by Year
20151
20252

Description

A fixed supply token written against the Standardized Contract APIs that the ethereum wiki carried before ERC-20 existed. Its interface is sendCoin(value, to), sendCoinFrom(from, value, to), coinBalance() and coinBalanceOf(address), and the transfer event is named CoinTransfer. The whole supply is created to the deployer in the constructor and can never be increased.

Delegation works differently from the allowance mapping that ERC-20 later settled on. approve grants an address blanket permission to move the approver's balance, approveOnce grants a single transfer up to a stated value and clears itself when used, and unapprove revokes both. A standing approval takes precedence over a one-time one.

Transfers return false rather than reverting when the balance is short, so a caller that ignores the return value can believe a failed transfer succeeded.

Heuristic Analysis

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

Detected Type: Token

Bytecode Overview

Opcodes3,101
Unique Opcodes171
Jump Instructions76
Storage Operations35

External Links

Related contracts