Back to Home

Greeter

Token
0x68b58d4d4cbc...7bf84edc2dc0
FrontierContract #4,386Exact Bytecode MatchEdit this contract
Deployed December 1, 2015 (10 years ago)Block 626,257

The Greeter from the solidity-baby-steps tutorials, deployed with an empty greeting.

Frontier EraVerified Source

Historical Significance

The ethereum.org token tutorial is where most people who deployed a token in this period started, and this is its opening form: a balance mapping, a guarded subtraction and the metadata a wallet needs to show a name. It has no allowance, so nothing can spend on a holder's behalf and no exchange or escrow can be given a limit. That gap is exactly what ERC-20 was written to close, and copies like this one are the before picture.

Context

Deployed 1 December 2015, during the Frontier era.

Key Facts
Deployment Block
626,257
Deployment Date
Dec 1, 2015, 07:13 PM
Code Size
964.0 B
Gas at Deploy
238,542
Transactions by Year
20151

Description

Example 5 of the solidity-baby-steps tutorial series. It keeps a creator address and a greeting string, returns the greeting from greet, exposes getBlockNumber as a second demonstration of reading a global, lets anyone replace the greeting through setGreeting, and lets the creator kill the contract. It is not the ethereum.org greeter, which splits the owner and the kill into a separate mortal contract; this one keeps everything in a single Greeter and compiles to different bytecode as a result. The constructor argument is an empty string, so greet returns nothing until someone calls setGreeting. Compiled with the optimizer on.

Source Verified

Exact bytecode match(964 bytes)
Compiler: v0.1.5+
Heuristic Analysis

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

Detected Type: Token
Contains SELFDESTRUCT opcode

Bytecode Overview

Opcodes964
Unique Opcodes110
Jump Instructions39
Storage Operations19

External Links

Related contracts