Contract 0xc9534b5f81a7...6bb5b35a2085

Utility

0xc9534b5f81a7...6bb5b35a2085

FrontierContract #4,183Exact Bytecode MatchEdit this contract

Deployed November 23, 2015 (10 years ago)Block 585,115

The storage example where set calls get and throws the answer away

Frontier EraVerified Source

Context

Deployed in November 2015 on the Frontier chain.

Key Facts

Deployer

0x23ee0a...3edbb9

Deployment Block

585,115

Deployment Date

Nov 23, 2015, 03:01 PM

Code Size

99.0 B

Gas at Deploy

43,993

Transactions by Year

20151

Deployment Transaction: 0xb15fc9ce37215d11...386b5bbdbffff070

Description

The set and get pair from the Solidity documentation's opening example, with set calling get immediately after writing and discarding what comes back. The call is real, not optimised out, so the deployed code carries a jump into the getter and straight back. It reads like someone checking that an internal call compiled the way they expected.

Source Verified

Exact bytecode match(99 bytes)

Compiler: v0.1.6+

View verification proof

Heuristic Analysis

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

Detected Type: Utility

Frontier Era

The initial release of Ethereum. A bare-bones implementation for technical users.

Block span: 0 — 1,149,999

July 30, 2015 — March 14, 2016

Bytecode Overview

Opcodes99

Unique Opcodes43

Jump Instructions7

Storage Operations2

Verified Source Available

Source verified through compiler archaeology and exact bytecode matching.

View Verification Proof

Show source code (Solidity)

// Submitted by EthereumHistory (ethereumhistory.com)
contract SimpleStorage {
    uint storedData;
    function set(uint x) {
        storedData = x;
        get();
    }
    function get() constant returns (uint) {
        return storedData;
    }
}