Whitepaper-lite

Role of NX1

NX1 is intended for verifiable participation by users, partners, creators, communities and developers in Nexus One programs. Balances and ownership should be confirmed by a public blockchain, while material treasury activity should have a published purpose and report.

NX1 is not an in-app balance or replacement for Nexus Coins; a right to equity, revenue, profit or corporate voting; a promise of yield, price growth or buyback; or a condition for accessing ordinary communication and collaboration features.

Utility boundaries

• Prove wallet-linked participation using on-chain data.
• Take part in advisory web votes for grants and ecosystem programs.
• Voluntarily support creators and communities on the web.
• Fund publicly documented development, integration and security-research grants.

NX1 must not buy reach, ranking, moderation outcomes or Premium access. Product access and internal purchases remain separate from NX1.

Economics

The Mainnet target is a maximum fixed supply of 1,000,000,000 NX1 with no inflation after final issuance and permanent revocation of mint authority. Until Mainnet, this is an approved design target rather than a completed on-chain fact.

Approved baseline allocation: 40% ecosystem programs, 25% treasury, 15% team with vesting, 5% partners with vesting, 10% liquidity under a separately approved plan, and 5% community and grants. The allocation remains subject to the published release gates and final Mainnet manifest.

Governance

NX1 governance is advisory and does not create corporate rights. Program rules, quorum, voting period, conflicts and execution authority must be published before each binding operational decision. Treasury actions require multisig approval and public reporting.

Security model

• No transfer fee, freeze authority or permanent delegate.
• Three isolated Mainnet signers with a tested 2-of-3 recovery procedure.
• Independent review of release scripts, wallet integration and treasury operations.
• A closed Devnet pilot before Mainnet approval.
• Independent verification of manifest, RPC, addresses, supply and authorities during the release ceremony.

Launch sequence

1. Complete every technical, legal, security and operational gate.
2. Publish the hash of the final release manifest.
3. Create the Mainnet mint with only approved metadata extensions.
4. Issue the exact supply to a multisig-controlled treasury.
5. Verify allocations and vesting accounts.
6. Permanently revoke mint authority after independent reconciliation.
7. Publish mint, transactions, supply methodology and release report.

Liquidity, verification and exchange-listing work may be considered only after the canonical Mainnet state is publicly verifiable.