Back to Home

Trade(TC)

Token
0xc7a30a42fd38...6392e6171fc1
DAO ForkContract #23KExact Bytecode MatchEdit this contract
Deployed August 27, 2016 (10 years ago)Block 2,149,840

A fixed-supply token with transfers and third-party allowances, deployed August 2016.

DAO Fork EraVerified Source

Historical Significance

This is the tutorial revision that added delegated spending, and it did it with approveAndCall: the allowance is set and the spender is called in the same transaction, so a contract learns about its allowance at the moment it is granted. It solved the problem ERC-20's plain approve leaves open, that a contract cannot notice an approval, and it was dropped from the standard anyway because it requires the spender to be a contract. The idea returned years later as ERC-777 and ERC-1363.

Context

Homestead arrived in March 2016 and the ethereum.org tutorials were rewritten around the transfer and balanceOf names that ERC-20 was standardising. Deploying a token had become a matter of filling in four constructor arguments, and most of the deployments of this period are exactly that.

Token Information
Token Name
Trade
Symbol
TC
Decimals
9
Key Facts
Deployment Block
2,149,840
Deployment Date
Aug 27, 2016, 07:29 PM
Code Size
1.5 KB
Gas at Deploy
638,589

Description

A token from the ethereum.org tutorial. Balances sit in a public balanceOf mapping and transfer(to, value) moves them, throwing rather than returning false when the sender is short and checking the recipient's balance for overflow before adding to it. An allowance mapping lets a holder authorise another address to spend a limited amount through transferFrom. ApproveAndCall sets the allowance and calls receiveApproval on the spender in the same transaction, so a spending contract learns of its allowance at the moment it is granted. There is no owner and no way to create further units: the supply written at deployment is the whole supply. It was deployed as Trade, with the symbol TC and an opening supply of 2,700,000 base units at 9 decimal places and it answers standard() with the string Token 0.1, the label the tutorial used before ERC-20 had a number.

Source Verified

Exact bytecode match(1,566 bytes)
Compiler: v0.3.3+

Historian Categories

Token
Heuristic Analysis

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

Detected Type: Token
Has ERC-20-like patterns

Bytecode Overview

Opcodes1,566
Unique Opcodes131
Jump Instructions85
Storage Operations35

External Links

Related contracts