Back to Home

0x5787...7060

Utility
0x57871303a7d6...562e557d7060
FrontierContract #777Exact Bytecode MatchEdit this contract
Deployed September 3, 2015 (11 years ago)Block 180,125

The Solidity tutorial subcurrency, compiled without the optimiser

Frontier EraVerified Source

Historical Significance

The Solidity documentation opened with a subcurrency because it is the smallest program that is obviously a program about money: an issuer, a ledger and a transfer that refuses to overdraw. Everything a token standard later argued about, who may create units, who may move them, what a client is told when they move, is present here in the form it took before anyone had proposed a standard at all.

Context

Deployed in September 2015 on the Frontier chain, compiled with solc v0.1.1 and the optimiser off.

Key Facts
Deployment Block
180,125
Deployment Date
Sep 3, 2015, 04:13 PM
Code Size
751.0 B
Gas at Deploy
225,131
Transactions by Year
20152

Description

The Coin example from the August 2015 Solidity Tutorial. The account that deploys it becomes the minter and is the only one who may create units through mint. Holders move balances with send, which checks the sender's balance, adjusts both entries and emits a Send event carrying the sender, the receiver and the amount. queryBalance reads any address's balance. There is no total supply and no approval mechanism, so it predates the token interface that ERC-20 would later standardise. The functions were written in the order send, queryBalance, mint, which the compiler preserves in the deployed layout.

Source Verified

Exact bytecode match(751 bytes)
Compiler: v0.1.1+
Heuristic Analysis

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

Detected Type: Utility

Bytecode Overview

Opcodes751
Unique Opcodes90
Jump Instructions20
Storage Operations11

External Links

Related contracts