Back to Home

Ping

Utility
Part of The Cyrus Adkisson Collection
0x657849c4d05f...0ba1d071a047
FrontierContract #867Exact Bytecode MatchEdit this contract
Deployed September 5, 2015 (11 years ago)Block 189,361

Ping, half of a cross-contract return value test

Frontier EraVerified Source

Historical Significance

An early mainnet example of inter-contract communication in Solidity. Part of a systematic tutorial series that documented learning Solidity from scratch during Ethereum's first months.

Context

Frontier and Homestead era deployment.

Key Facts
Deployer
Cyrus Adkisson(0xcf684d...ad1bac)
Deployment Block
189,361
Deployment Date
Sep 5, 2015, 05:45 PM
Code Size
1.2 KB
Gas at Deploy
333,946
Transactions by Year
20152

Description

One half of a two-contract experiment in whether an Ethereum contract can read a non constant return value from another contract, which web3 and geth could not do at the time. Ping holds the address of a Pong, calls into it transactionally, and stores what comes back so it can be read afterwards.

Source Verified

SolidityExact bytecode match(1,277 bytes)
Compiler: v0.1.3+

Exact creation bytecode match. Author Cyrus Adkisson published source at https://github.com/cyrusadkisson/solidity-baby-steps/blob/master/contracts/45_ping.sol. Batch-matched against 357 deploy TXs from deployer 0xcf684dfb8304729355b58315e8019b1aa2ad1bac.

Historian Categories

Experimental
Heuristic Analysis

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

Detected Type: Utility

Bytecode Overview

Opcodes1,277
Unique Opcodes97
Jump Instructions35
Storage Operations20

External Links

Related contracts