Back to Home

LilyCoin(ל)

Token
0x54808b9ec046...b82930d5bc5a
DAO ForkContract #22KExact Bytecode MatchEdit this contract
Deployed August 5, 2016 (10 years ago)Block 2,017,072

A fixed-supply token with transfers and allowance spending, 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
LilyCoin
Symbol
ל
Decimals
2
Key Facts
Deployment Block
2,017,072
Deployment Date
Aug 5, 2016, 09:00 PM
Code Size
2.8 KB
Gas at Deploy
990,105

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 LilyCoin, with the symbol ל and an opening supply of 10,000,000 base units at 2 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(2,902 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

Opcodes2,902
Unique Opcodes134
Jump Instructions104
Storage Operations41

External Links

Related contracts