Back to Home

IPFSTest

program
0xf4a56662f396...8cdebd90bc6f
FrontierContract #7,920Exact Bytecode MatchEdit this contract
Deployed February 5, 2016 (10 years ago)Block 958,095

A minimal contract storing a single IPFS CIDv0 hash on-chain as a public string. Deployed by Thomas Bertani / Oraclize on Feb 5, 2016.

Frontier EraVerified Source

Historical Significance

The contract is an early on-chain example of the "Ethereum as pointer layer, IPFS as content layer" pattern: a single immutable string variable holding a CIDv0 hash. The pattern later became ubiquitous in NFT metadata and token URI schemes, but in February 2016 it was still being tested in the wild by a small number of teams working at the intersection of Ethereum and IPFS.

Context

The contract was deployed during the Frontier era, five weeks before the Homestead hard fork on March 14, 2016. It was compiled with Solidity v0.2.0, which had been released on December 2, 2015. Oraclize (later Provable) was at this time building out its oracle service, which used IPFS for delivery and proof storage.

Key Facts
Deployment Block
958,095
Deployment Date
Feb 5, 2016, 03:30 PM
Code Size
517.0 B
Gas at Deploy
169,915

Description

IPFSTest is a one-line contract deployed on February 5, 2016 (block 958,095) that holds a single piece of data: the IPFS CIDv0 hash Qmd8ijSKemAE1NX2CbFcBP8wbtTweb4uqKKrd7aJe7bDN1. The contract consists of a single public string state variable named x, which compiles to an auto-generated x() getter (selector 0x0c55699c) and a constructor that copies the hardcoded string into storage slot 0. There are no setters, no access control, no events, and no other functions. The value is set at deploy time and cannot be changed.

The contract was deployed by 0x0047A8033CC6d6Ca2ED5044674Fd421F44884dE8, the same key that deployed the earlier GetSet proxy attributed to Thomas Bertani of Oraclize. Six blocks later (block 958,101) the same key deployed a byte-for-byte identical contract at 0x4b26dcf0981355c8b1f8190f116945322a62a96a. Both contracts encode the same hardcoded IPFS hash.

The content at the referenced CID is no longer retrievable through public IPFS gateways. A 2026 retrieval check against the IPFS DHT returns "no providers found for the given CID," meaning no peer is advertising that hash.

Source Verified

SolidityExact bytecode match(517 bytes)
Compiler: soljson

Exact bytecode match (init + runtime). Runtime: 279 bytes. Creation: 517 bytes (238 bytes init). Byte-for-byte identical sibling deployed 6 blocks later at 0x4b26dcf0981355c8b1f8190f116945322a62a96a by the same key.

Heuristic Analysis

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

Detected Type: program

Bytecode Overview

Opcodes517
Unique Opcodes110
Jump Instructions23
Storage Operations11

External Links