One platform. Clear boundaries.

Mint is a testnet first NFT platform. The approved core includes standard collection creation, minting, marketplace discovery and activity, creator and user profiles, regular leaderboards, analytics, and chain indexing. Testnet readiness means the code is prepared for controlled deployment and acceptance testing. It does not mean every feature is enabled or approved for mainnet.

A standard primary mint uses a creator selected mint price and a Mint platform fee equal to 2.5% of mint proceeds. Network gas is separate. Mint collections communicate a fixed 15% creator royalty through ERC 2981 on supported secondary sales.

ERC 2981 communicates royalty terms but cannot force an external marketplace to pay them. Every wallet approval should identify the network, contract, quantity, price, platform fee, royalty information, and estimated gas.

Mint is designed as a noncustodial interface. Users retain control of wallet keys and approve their own blockchain transactions. Mint does not request seed phrases or private keys and cannot reverse a finalized blockchain transaction.

The soft staking model does not transfer an NFT into Mint custody. The NFT stays in the user wallet. A transfer ends eligibility after finalized ownership verification, even if the NFT later returns to the same wallet.

Soft staking pools may offer token rewards or offchain points. A founder supplied reward wallet retains the token inventory. The staking router may pull only an approved claim amount directly from that wallet to an eligible user, subject to allowance and signed claim controls.

Changing the reward asset or founder reward wallet requires a 72 hour cooldown. When a token pool reaches 20% or less of its funded reference amount, administrators receive a low balance warning and users see a low pool amount notice. The feature remains disabled until deployed contracts, finalized NFT transfer correlation, real dashboard data, and funded wallet tests are accepted.

Marketplace prices, bids, volume, ownership, listing state, verification, profile activity, points, and leaderboard positions depend on finalized indexed data. They may be delayed, incomplete, or corrected after reorganization handling and reconciliation.

Verification, rankings, skins, points, achievements, popularity, and profile presentation are product signals. They do not represent an investment recommendation, guarantee of authenticity, legal status, future value, or entitlement to compensation.

Mint uses Cloudflare based application infrastructure, D1 data storage, RPC services, chain indexers, block explorers, wallets, and permanent metadata services such as Arweave. Public wallet activity and permanent metadata may remain visible indefinitely.

Offchain records are used for product operation, security, support, reconciliation, and legal compliance. Provider terms, retention schedules, international transfer bases, privacy request channels, and the final subprocessor list require approval before mainnet.

Privileged roles should remain separated across treasury, deployment, timelock governance, launch approval, and staking claim signing. Feature flags, pause controls, cooldowns, signed claims, environment validation, secret scanning, dependency checks, contract tests, and deployment reconciliation reduce operational risk.

Automated checks do not replace qualified legal review, an independent smart contract security audit, or real wallet acceptance testing against deployed addresses.

Before mainnet or real value activity, Mint requires a finalized operator identity, governing law, eligibility and sanctions rules, support and privacy contacts, provider agreements, jurisdiction review, production role holders, external contract review, verified deployment evidence, monitoring, incident response, backups, rollback procedures, and completed acceptance tests.

See the Documentation hub, Terms, Privacy Policy, and Risk Disclosures for the connected operating package.