Understand the system.
Build with confidence.

Find the right reference

Current protocol versions

The contract launch domain for new launches is community-nft-launchpad.manifest.v5, with economicsVersion: 5: public minting costs one FLOOR plus a 0–10% creator fee (default 10%) collected in FLOOR, sold for quote through the collection’s Uniswap V4 pool, and paid to recipients in quote. If a sale cannot complete, unsold fees stay pending for a later mint or permissionless sellMintFees() call. Deployed v4 collections retain their original FLOOR-denominated fee payouts; collections launched before v5 keep their original fee terms. Public preparation transport and metadata commitment versioning are separate: the preparation envelope remains version 1, and metadata uses JPEG_MARKETS_METADATA_V1. Do not reuse an old deployment ABI or relabel indexed state.

The code is the source of truth: SPEC.md, docs/mint-economics.md, contracts/src/, and the validators in launch/ and services/src/prepare-collection.mjs.

Integrate the protocol

Use verified deployed contract bindings, the compiled ABIs, and the user’s own wallet. Public minting and NFT deposits share the collection’s configured opening delay; token trading begins with pool activation.

Networks

JPEG Markets supports collections on Base and Robinhood Chain. Each collection belongs to one network; its NFTs, FLOOR token, paired token, vault, and pool all use that network.

Use the collection’s published deployment bindings. Network support does not mean a collection is available on both chains. Verify the RPC chain ID, coordinator runtime, module hash, router and final launch receipt independently for each deployment. See Base’s network reference.