Back to Home

mike()

Token
0x87c5ea1c0c81...2f72e717a3f8
Tangerine WhistleContract #25KExact Bytecode MatchEdit this contract
Deployed November 12, 2016 (9 years ago)Block 2,613,865

A fixed-supply token with transfers and spending approvals, and an owner who can withdraw the ether the contract holds, deployed November 2016.

Tangerine Whistle EraVerified Source

Historical Significance

The contract answers standard() with the string Token 0.1, a version label the ethereum.org tutorial used before ERC-20 had a number. Tokens carrying that string are datable by it: they were copied while the interface was still the tutorial's own convention rather than a ratified standard, and the field disappeared once ERC-20 gave the shape a name.

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
mike
Symbol
Decimals
0
Key Facts
Deployment Block
2,613,865
Deployment Date
Nov 12, 2016, 08:23 PM
Code Size
1.1 KB
Gas at Deploy
504,735

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. There is no owner and no way to create further units: the supply written at deployment is the whole supply. It was deployed as mike, with the symbol □ and an opening supply of 50 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,092 bytes)
Compiler: v0.4.2+

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,092
Unique Opcodes122
Jump Instructions63
Storage Operations22

External Links

Related contracts