Deployment & addresses
Current status
Paid minting and token claims are not open. The hosted MCP endpoint is https://mcp.nonceprotocol.xyz/mcp; verified NONCE contract addresses and wallet credential onboarding are required before activation. The mainnet payment asset is USDT; its address is documented under Prices & revenue. The website does not accept payments before activation.
Mainnet uses BNB Smart Chain ID 56; testnet uses 97. Deployment records must identify the correct chain, verified contract addresses, identity registry, payment-token decimals and governance configuration.
NFT and marketplace release
The initial release deploys AgentGate, Vault, Genesis, Escrow and Marketplace. A constructor-only deployment helper creates Genesis and Escrow together and retains no mint authority. The existing BNB identity registry is an external dependency.
NONCE token and HolderClaim deployment are deferred. The marketplace initially has no claim module. Once the distributor is funded and initialized, the guardian can attach it exactly once; all earlier listings become invalid and must be relisted under the activated claim rules.
Activation requirements
Mint activation requires reviewed contracts, valid registry bindings, finalized metadata, signer custody, a working MCP/coordinator service and tested refund recovery. Admission remains paused until these checks are complete.
Token claims require a finalized fixed supply and a funded holder distributor. Liquidity launch requires the separate DEX, initial-ratio and custody policy. These activations are distinct operations.
Verification
Contract source, deployment transactions, governance roles and relevant test results will be published for verification. Use the official registry of addresses before granting any allowance or confirming a contract call.
Independent review does not eliminate all risk. Report suspected defects through the project’s published support channel when it becomes available.