Full release readiness

Current state

Stage

Mainnet readiness

Devnet identity

Completed and verified

Public trust baseline

Completed

Release tooling

Ready with fail-closed gates

Devnet metadata URI

Signed and verified

Tokenomics

Owner-approved

Devnet custody

Temporary single controller; allocation blocked

Mainnet mint

Not created

Completed work

• fixed NX1 identity, Token-2022 and a target maximum of 1 billion;
• Devnet mint, supply, metadata, treasury and authorities verified through RPC;
• no freeze authority, transfer fee, transfer hook or permanent delegate;
• official domain, metadata JSON, logo, whitepaper and disclosures published;
• Mainnet commands require an immutable SHA-256 manifest and full release gate;
• the temporary Devnet controller is limited to testing; allocation, liquidity and finalization remain blocked until multisig;
• release ceremony, tokenomics, vesting, security review and post-launch procedures prepared.

Remaining blockers

1. Multisig: before on-chain allocation or Mainnet, three isolated signers, a 2-of-3 threshold and tested recovery are required.
2. Legal and tax: written assessment for each launch and promotion jurisdiction.
3. Security: independent review of scripts, wallet, treasury and issuance procedure.
4. Closed pilot: Devnet compatibility, replay, recovery and support testing.
5. Ceremony: independent reconciliation of manifest, RPC, addresses, supply and authorities before signatures.

Any missing evidence automatically blocks Mainnet preflight. A label on this page never replaces on-chain state or a signed written document.

Approved economic baseline

Ecosystem programs

40% · 400,000,000 NX1 · ≥48 months

Treasury

25% · 250,000,000 NX1 · multisig and reporting

Team

15% · 150,000,000 NX1 · 12 + 36 months

Partners

5% · 50,000,000 NX1 · 6 + 24 months

Liquidity

10% · 100,000,000 NX1 · separate approval

Community and grants

5% · 50,000,000 NX1 · limits and reports

This is an approved economic baseline, not a promise of distribution. Any change must be published and re-approved before the Mainnet manifest is signed.

Full release sequence

1. close every release gate and publish the final manifest hash;
2. create the Mainnet mint with only approved metadata extensions;
3. issue the exact supply to a multisig-controlled treasury;
4. verify and fund published allocation and vesting accounts;
5. permanently revoke mint authority after independent reconciliation;
6. publish the mint, transactions, report and circulating-supply method;
7. only then separately approve liquidity and apply for verification.

Verification and markets

Verification confirms a canonical mint; it does not confirm safety or value. Jupiter verification is relevant only after Mainnet metadata and verifiable liquidity. CoinGecko requires active trading on a tracked market. Artificial volume, hidden market making and listing spam are prohibited.

Official references: Solana token verification, Jupiter verification, CoinGecko listing.