Back to Home

token (faucet)

Token
0x7b484f9272c9...0f31be92b6e7
FrontierContract #6,306Exact Bytecode MatchEdit this contract
Deployed January 10, 2016 (10 years ago)Block 826,605

A minimal subcurrency with a faucet mechanic. Call token() to claim 10,000 coins or any amount desired. Deployed Jan 10 2016.

Frontier EraVerified Source

Historical Significance

A subcurrency that hands out its own units on request, with no sale and no allocation to the deployer. Distribution was the unsolved half of every early token: a fixed supply credited to its creator leaves everyone else with nothing to hold, and a faucet was the simplest answer anyone had before crowdsales and airdrops existed.

Context

Ethereum's Frontier network went live on 30 July 2015. Contracts were compiled and deployed from the geth console, there was no test network in common use, and the material people copied from was the ethereum.org tutorials, the Solidity documentation and the go-ethereum wiki. Almost everything deployed in these months is somebody trying the tools.

Key Facts
Deployment Block
826,605
Deployment Date
Jan 10, 2016, 11:42 AM
Code Size
294.0 B
Gas at Deploy
95,185
Transactions by Year
20166
20251

Description

A concise early subcurrency contract featuring a faucet mechanic. Calling token(uint amount) initializes the caller's balance, and if amount is 0 it defaults to 10,000 tokens. This pattern allowed open distribution without a pre-mine. The contract uses a single mapping (coinBalanceOf) with a public auto-getter, and emits CoinTransfer events on every transfer. There is no owner, no mint function and no supply cap: anyone can seed their own balance. Based on the classic ethereum.org "Coin" tutorial, this variant strips away the issuer/exchange complexity in favor of simplicity. The three selectors (token, sendCoin, coinBalanceOf) match the tutorial structure exactly. Compiler: Native C++ solc v0.2.0 (commit 67c855c5, Jan 20 2016 build) with --optimize. The optimizer produces EXP-based selector dispatch, compressing the runtime to just 276 bytes.

Source Verified

SolidityExact bytecode match(294 bytes)
Compiler: v0.2.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

Opcodes294
Unique Opcodes81
Jump Instructions15
Storage Operations9

External Links

Related contracts