Back to Home

Test

Experimental
0xad1a41f7e5ff...254fa73851e4
FrontierContract #1,544Exact Bytecode MatchEdit this contract
Deployed September 24, 2015 (10 years ago)Block 284,512

An 86-byte contract with one function, test1(bytes32), which writes its argument into the single storage slot and nothing else.

Frontier EraVerified Source

Historical Significance

A write-only storage probe. The name test1 is the giveaway: this is somebody checking that a transaction could put a value into contract storage at all, in a period when the compiler, the client and the JSON-RPC layer were each new enough to be the reason something did not work. Contracts like this were the unit tests of 2015, run against mainnet because there was nowhere better.

Context

Deployed 2015-09-24 by 0x62a496c75751c67e600f5d04e763b85d4069af8e. One instance of this runtime is known. The selector could not be recovered from 4byte and survived a 514,800-signature brute force; it was finally resolved as test1(bytes32) through the openchain signature database. Source recovered by exact runtime bytecode match, verified on Sourcify and Etherscan.

Key Facts
Deployment Block
284,512
Deployment Date
Sep 24, 2015, 06:48 PM
Code Size
103.0 B
Gas at Deploy
42,945

Description

The entire contract is one setter. test1(bytes32) at selector 0x8108ffc0 takes a 32-byte value and stores it in slot 0. There is no getter, no access control, no event and no fallback, so the value can be overwritten by anyone and can only be read by inspecting storage directly rather than through a call.

Source Verified

SolidityExact bytecode match(103 bytes)
Compiler: v0.1.3+
Heuristic Analysis

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

Detected Type: Experimental

Bytecode Overview

Opcodes103
Unique Opcodes28
Jump Instructions6
Storage Operations2

External Links

Related contracts