Back to Home

MKToken(MKC)

Token
0x1ab9e0c234b6...11d0345a91de
Tangerine WhistleContract #25KExact Bytecode MatchEdit this contract
Deployed October 26, 2016 (9 years ago)Block 2,507,310

A fixed-supply token with transfers and allowance spending, deployed October 2016.

Tangerine Whistle 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

By late 2016 ERC-20 had settled the interface a token was expected to answer, and the ethereum.org tutorial was still where most people copied one from. OpenZeppelin's contracts were not yet the default, so the code behind a token of this period is usually the tutorial's, with the constructor arguments changed and nothing else.

Token Information
Token Name
MKToken
Symbol
MKC
Decimals
0
Key Facts
Deployment Block
2,507,310
Deployment Date
Oct 26, 2016, 12:51 AM
Code Size
1.6 KB
Gas at Deploy
598,121

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 records what each spender has been authorised for. 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 MKToken, with the symbol MKC and an opening supply of 0 units, indivisible 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,615 bytes)
Compiler: v0.4.0+

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,615
Unique Opcodes129
Jump Instructions90
Storage Operations31

External Links

Related contracts