What is available today

Separate the deployed platform from prospective contract extensions.

This handbook describes the existing art platform and current client. It does not turn a design proposal into a deployed contract feature.

Available in the deployed platform

Code-page NFTs and historical posts, art projects referencing code transactions, sequential edition mints, project artist/team administration, royalty-manager clones, optional hosted or contract-generated metadata, and the artist-script runtime described here.

The touch-control declaration is a viewer convention. It adds interface support without changing the deployed art contracts or editing posted artwork.

Active development and design work

The repository has a separate Hardhat mint-gate project under contracts/new-art/. Its existence and local tests are not proof that a gate is deployed or configured for a particular release. Verify an actual deployment, permissions and routing before relying on one.

The proposed retrofit includes an archive for preserved source and project reserve/token mechanisms. Batch minting, minting into a reserve, token redemption and related sale flows require their own implemented, reviewed and configured contracts. They are not parameters of the deployed anyoneMintProjectEdition method.

A VRF or delayed randomness/reveal integration is likewise not supplied by the current generic viewer or mint method. An artist needing stronger allocation guarantees should settle that protocol before making release promises.

Immutables.co may eventually be presented as code.immutables.art. The branding change has not been assumed by these contract instructions.

Before documenting a new capability as live

Verify the deployed address and chain, source and ABI, project configuration, who can bypass or change it, how collectors interact with it, how the viewer reconstructs the result, and what happens when a dependency fails. Update the human chapters and LLM reference together.

Repository references: contracts/new-art/README.md and docs/RETROFIT_CONTRACT_SPEC.md. These are development/design references, not a deployment registry.