History needs a paper trail.
NFT Archaeology is a community archive of early Ethereum collections, maintained by the team behind PixelMap with contributing researchers.
What the archive represents.
The current collection index contains 37 records from 2015–2019, all on Ethereum. Dates, descriptions, asset properties and concerns come from historicalNFTs ↗. The index is not a claim of complete coverage.
Contract behavior is the primary evidence for technical assertions. Creator statements and contemporary sources help establish intent and context. A historical “first” needs a precise definition and supporting evidence; it is not inferred from age alone.
Each entry links to its exact source revision and record history. Development and marketplace status describe the source snapshot, not a current certification. Where editorial review dates are absent, the interface says so.
Attributes, not a single verdict.
The interface presents supply, storage, standards, wrapper behavior and recorded concerns independently. The old API’s numerical score and grade remain in the downloadable data for compatibility, but are not used to rank historical significance or safety.
That legacy formula begins at 100, subtracts 5 for inactive development, 10 for non-fixed supply, 5 for a non-fungible flag recorded false, 5 for absent marketplace verification, and 10 for storage other than on-chain or IPFS. It adds 8 for on-chain storage and subtracts 6 per warning or 25 per alert. Scores can exceed 100. These policy choices are not a measure of historical importance.
Recorded concerns are reviewable statements, not a complete security audit. An empty concerns list means no concerns are recorded in that source snapshot.
Researching the 0xzxch list.
The contract leads are attributed to @0xzxch’s source post ↗ and captured from the original list ↗. Names, dates and source categories are retained as source assertions.
- Every source address receives an Ethereum mainnet runtime-code and ETH-balance check at the same recorded block.
- Actual runtime bytecode is preserved in downloadable per-contract artifacts. SHA-256 hashes and the block hash anchor the capture.
- A limited EVM disassembly collects recognized PUSH4 operands. These are heuristic method signals; not an ABI, a proof of behavior, or an NFT classification.
- When a supportsInterface selector appears, read-only ERC-165, invalid-ID, ERC-721 and ERC-1155 probes are captured with a 30,000-gas limit.
- Sourcify is checked for verified source and ABI. Provider verification status and exact runtime equality against the snapshot are recorded separately. A failed lookup does not imply source is unavailable everywhere.
- Exact, case-insensitive original or wrapper address matches identify existing catalogue entries. Names alone do not establish equivalence.
- Human evaluation must establish ownership, transfer behavior, supply, storage, wrapper relationships, maintenance evidence and security concerns before a candidate becomes a collection entry.
ETH held is not an estimate of recoverable or claimable funds. Withdrawal-like ABI names are only leads. Permissions, beneficiaries, deposits, liabilities, proxies and historical state must be reviewed. The site performs no wallet interactions or transactions.
Automated evidence capture: 2026-11-18 · block 26443825 ↗. Human review status is recorded separately.
Download research provenance ↓Source lookup coverage.
Sourcify returned a rate-limit response stating that this API is for single-contract lookups, not bulk collection. Bulk source requests were stopped. Previously captured responses are preserved; remaining addresses have runtime bytecode and balance artifacts with source lookup explicitly incomplete. The script permits one explicit --lookup-address=0x... lookup at a time and does not retry rate limits.
Every address still has actual runtime bytecode and exact balance evidence. Source lookup failures and skipped lookups remain explicit; a bytecode capture is not a recovered Solidity source file.
Leave the next researcher a trail.
Editorial changes stay in historicalNFTs ↗. Propose an issue or pull request with:
- The exact original, wrapper, or related contract addresses.
- What is being asserted, and what remains uncertain.
- Source code links, transaction hashes, block numbers, contemporary references and dates.
- Evidence for each relevant field: distinct ownership and transfers, supply, storage, wrapper reversibility, maintenance and concerns.
- A human review date and reviewer identity, if an actual review has been performed.
The website downloads a pinned data revision at build time. After a data change is reviewed and merged, advancing the frontend pin publishes the new snapshot.
Reuse the research.
Downloads include the source revision and separate source records from generated fields. Bookmarks are browser-local, and filtered collection, research and comparison views can be shared by URL.
Collection dataset ↓ · Research evidence index ↓ · Source pin ↗
