Back to Home

IMG

other
0x2fabe69843e9...e5568986c7a1
ByzantiumSource VerifiedEdit this contract
Deployed January 21, 2018 (8 years ago)Block 4,943,545

On-chain JPEG of a tabby cat: a 128x128 JFIF baseline image returned as a hex-text string by a single read() function. January 2018.

Byzantium EraVerified Source

Historical Significance

A pure on-chain image storage proof of concept from January 2018, the same era when CryptoPunks (June 2017) had pioneered on-chain pixel-art via CREATE2 stubs and Etheria (October 2015) had stored its block grid in storage. IMG is among the simplest and most direct on-chain image storages in Ethereum history: 1,138 bytes of JPEG, no Merkle proofs, no IPFS, no chunking, just a string literal compiled into runtime bytecode. It captures a moment in 2018 when developers were still experimenting with the boundaries of what Ethereum could store and serve.

Context

Deployed 20 January 2018, near the all-time-high of the 2017-18 bull market (ETH peaked at $1,432 on 13 January 2018, eight days before this contract was deployed). Solidity was at v0.4.11+commit.68ef5810 and the optimizer was on. EIP-170 (1.3.4 max contract code size of 24,576 bytes) had been in effect since Spurious Dragon (November 2016), so an 1,138 byte image fit comfortably within the contract size limit.

Key Facts
Deployment Block
4,943,545
Deployment Date
Jan 21, 2018, 12:49 AM
Code Size
3.6 KB
Gas at Deploy
1,052,857

Description

IMG is a Solidity contract whose only state and only function is a hard-coded JPEG file. The single read() function returns the contents of a 1,138 byte 128x128 JFIF baseline JPEG image as a space-separated string of hex bytes ('FF D8 FF E0 00 10 4A 46 49 46 00 01 01 00 00 01 00 01 ...'). When decoded back to binary, the bytes form a renderable JPEG image of a tabby cat.

The contract has no constructor logic, no events, no storage, no access control, and no economics. Its purpose is purely to encode an image into Ethereum's permanent state by encoding it as a string literal in a function return value. The deployer 0xd766d89d3492df23f2b5a6df1720184c725d9f48 wrote no other contracts of note.

Identified during the 2018 contract lake survey as the only contract in the entire 2018 dataset whose return data is a fully renderable image when interpreted as JPEG. Other on-chain image experiments from the same era stored images via CREATE2 stub patterns or split them across multiple storage slots; IMG is the simplest and most direct approach: paste the bytes into a string return literal and let solc store them in code.

Source Verified

SolidityEtherscan verified
Compiler: v0.4.11

Author-published source verified on Etherscan. Contract is a single read() returning a hex-text JPEG. To recover the image: read() and parse the hex string into bytes.

Heuristic Analysis

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

Detected Type: other

Bytecode Overview

Opcodes3,732
Unique Opcodes90
Jump Instructions16
Storage Operations47

External Links