Back to Home

EF1 ABI Test (foo() address)

Unknown
0xdf8eb001f293...e4a09bd9e48d
FrontierContract #1,328Exact Bytecode MatchEdit this contract
Deployed September 20, 2015 (10 years ago)Block 262,005

A 77-byte contract deployed by the Ethereum Foundation wallet on September 20, 2015. Implements foo() returning a 21-byte constant value, requiring the PUSH21 o

Frontier EraVerified Source

Historical Significance

Part of the earliest known ABI compliance testing on Ethereum mainnet. The Ethereum Foundation's operational wallet deployed these contracts to test ABI dispatch and return encoding as the standard was being finalized.

Context

Deployed 52 days after Frontier launch. The EF1 wallet (0x5eD8Cee6b...) was used for Foundation operational transactions. Three ABI test contracts were deployed in a 6-hour window on Sep 20, 2015.

Key Facts
Deployer
Ethereum Foundation(0x5ed8ce...8fad9f)
Deployment Block
262,005
Deployment Date
Sep 20, 2015, 08:48 AM
Code Size
92.0 B
Gas at Deploy
40,720

Description

EF1 ABI Test Suite

On September 20, 2015, the Ethereum Foundation wallet 0x5eD8Cee6b63b1c6AFce3AD7c92f4fD7E1B8fAd9F deployed three ABI test contracts in a 6-hour window:

Time (UTC)AddressFunctionReturns
06:280xe30608b5foo()uint256(5)
08:480xdf8eb001foo()address
09:350x441e72c6bar(uint256)x + 2

foo() (selector 0xc2985578) returns a fixed 21-byte value 0x05CBAeB5B771Cf21b59f17Ea9c70915A27041E5409. The extra leading byte makes it 21 bytes, pushed via PUSH21 (0x74).

The bytecode uses the pre-ABI dispatcher pattern: PUSH29 with 2^224, then DIV against CALLDATALOAD(0) to extract the 4-byte selector. This hand-crafted low-level EVM style predates Solidity's standardized PUSH1 0xe0 / EXP sequence.

Cracked in 2026 using solc 0.5.17 Yul strict-assembly. The 21-byte constant is the key detail.

Source Verified

yulExact bytecode match(92 bytes)
Compiler: solc 0.

Exact bytecode match. 77 bytes. Critical detail: return value is 21 bytes (PUSH21), not a standard 20-byte address.

Heuristic Analysis

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

Detected Type: Unknown

Bytecode Overview

Opcodes92
Unique Opcodes48
Jump Instructions4
Storage Operations2

External Links