Where the image lives
The NFT does not point to a hosted PNG. Its tokenURI returns inline metadata, and the image field contains an SVG assembled from contract-readable layers. A marketplace needs an RPC connection, not an image server.
Technical notes / plain language
How the object actually works.
A compact reference for collectors, marketplaces and builders. No mythology, just the storage, rendering and metadata boundaries.
What compact DNA means
Each token stores small trait identifiers instead of copying the full SVG into token storage. The renderer resolves those IDs against the shared layer archive. This keeps mint storage compact while every final image stays reproducible.
Why SSTORE2 is used
SVG bytes are written once into contract bytecode and read by pointer. It is substantially cheaper than normal storage for large immutable blobs and lets many tokens reuse the same source layer.
What can evolve
Canonical DNA keeps the original six traits. Head, clothing, glasses and mouth can expose later visual states. Unlocking V2 or V3 changes the displayed artwork, not the historical trait lineage.
What OpenSea reads
OpenSea reads tokenURI, then indexes its attributes and inline image. Metadata refresh is required after an evolution or mutation transaction before a marketplace reflects the new display state.
What remains external
Wallet connection, RPC transport, marketplace offers and the Normies API are external interfaces. The core Vitalik artwork remains contract-driven; those services provide access or optional cross-collection context.
One verification path.
Select a token, decode tokenURI, inspect its attributes and compare the live SVG layers in one place.
Inspect a token