AdminCheckV2

Experimental

0x592621b77374...0a4504f26259

FrontierContract #5,554Exact Bytecode MatchEdit this contract

Deployed December 22, 2015 (10 years ago)Block 732,635

A test contract that writes a bool flag based on whether the caller matches a hardcoded admin address, with kill, get, and getBool functions.

Frontier EraVerified Source

Historical Significance

Part of a series of iterative prototypes by a prolific Frontier-era developer. Shows the progression from read-only admin checks to persistent state writes, a pattern that evolved into multi-party escrow contracts with 72 production instances.

Context

Deployed on December 30, 2015 during the Frontier era. Developers were learning Solidity patterns like packed storage (address + bool in one slot) and constructor initialization.

Key Facts

Deployer

0x8b9346...73766e

Deployment Block

732,635

Deployment Date

Dec 22, 2015, 09:42 PM

Code Size

245.0 B

Gas at Deploy

98,175

Transactions by Year

20153

Deployment Transaction: 0x9cae109e8f392a12...8e7a0bf91dade463

Description

An evolution of the AdminCheck (test-v1) contract by the same developer. Adds a constructor that sets the owner to msg.sender, a bool state variable (flag), and a getBool() function to read it. The test() function writes the result of an admin address comparison to storage instead of just returning it.

Part of a series of iterative prototypes by a developer who deployed over 400 contracts between December 2015 and May 2016. This contract builds on the hardcoded admin check pattern from test-v1, adding persistent state tracking. The owner and flag are packed into slot 0 (address at bits 0-159, bool at bit 160).

The contract was selfdestructed shortly after deployment, deployed just 63 blocks after its predecessor test-v1.

Source Verified

SolidityExact bytecode match(245 bytes)

Compiler: soljson

View verification proof

Exact bytecode match (init + runtime). 245 bytes creation code (34 init + 211 runtime), no constructor args. Contract is selfdestructed.

Historian Categories

Experimental

Heuristic Analysis

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

Detected Type: Experimental

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

Opcodes245

Unique Opcodes67

Jump Instructions9

Storage Operations8

Verified Source Available

Source verified through compiler archaeology and exact bytecode matching.

View Verification Proof

Show source code (Solidity)

contract T {
    address owner;
    bool flag;

    function T() { owner = msg.sender; }

    function kill() { suicide(owner); }

    function get() returns (address) { return owner; }

    function getBool() returns (bool) { return flag; }

    function test() {
        flag = (msg.sender == 0x8b9346aa412b52954b5138dbb72adab97273766e);
    }
}

External Links

Etherscan Verified Source (if any)

Related contracts

Store

Same deployer

A simple key-value store contract with set, get, and kill functions, deployed during the Frontier era.

0x621492...3512fcDecember 14, 2015

AdminCheck

Same deployer

A test contract that checks if the caller matches a hardcoded admin address, with kill and get functions.

0x49efab...82c595December 22, 2015

Digix

Same era

The earliest known attempt to deploy a smart contract on Ethereum mainnet (Aug 7 2015, thanateros.eth). Ran out of gas before code deposit; creation bytecode reconstructed exactly.

0x9a049f...a977a0August 7, 2015

Test

Same era

The earliest known Ethereum contract with executable runtime code. A single function go() that returns the string "eth", compiled with the first publicly available Solidity compiler (v0.1.1).

0x651629...8c21faAugust 7, 2015

Greeter

Same era

An early Ethereum contract that returns the string “Hello World!” when called.

0xfea8c4...8b08ebAugust 7, 2015

Greeter

Same era

One of six HelloWorld Greeter deployments by Linagee on Ethereum Frontier Day 1 - same source, same compiler, greeting: 'Hello World!'

0xd464e6...dc98f3August 7, 2015