The art is committed.
Reveal makes it visible.
A fixed assignment, with a clear path from placeholder to artwork.
Artwork is fixed before launch
The local folder helper sorts files for review. Canonical protocol preparation shuffles public artwork assignments, then commits them before activation; folder order is not a promise of which artwork a public mint receives.
Metadata preparation commits the artwork assignment before activation. Reveal publishes an existing assignment; it does not select a new image or run a fresh random draw.
Public mints receive sequential IDs, skipping reserved team IDs. An ID may first display placeholder art. Ownership and artwork visibility are different states.
Images and metadata travel together
Each metadata file describes a piece and points to its image. The canonical preparation path requires verified IPFS content and compares it with locally retained bytes before producing launch artifacts. Keep the image files as well as the metadata.
A local preview, generated CID, or copied URL does not prove content is pinned on the public IPFS network. Publishing and continued availability require a real hosting and recovery plan.
Keep the private handoff safe
The public manifest contains the commitment. Private assignments and salts belong in the separate encrypted recovery package. Never put that package or its key into public docs, a frontend build, or an agent’s shared transcript.
Illustrative art in the playground
Test collections use sourced artwork from mfers, CrypToadz, and Blitmap for illustration. These test NFTs are independent of the originals. Some reuse original IPFS metadata; others use demo metadata wrappers or local raw-CID mirrors. Those local mirrors are not public pins.
Original collection links identify the source. They do not imply partnership, ownership of an original NFT, or endorsement.