NOVA21 Whitepaper
21 million. One clear limit. A documented token model and a practical plan for transparent project tools.
The token and presale are deployed. Launch Tools, dedicated vesting execution and future liquidity are distinct development and execution items. No return or listing is guaranteed.
1. Project overview
NOVA21 is a BNB Smart Chain project with a fixed-supply token, N21, and a planned product called NOVA21 Launch Tools. Its proposed focus is making project contracts, treasury information and execution milestones easier to inspect. Token ownership does not represent equity, revenue sharing or a guaranteed return.
2. Implemented and planned
Implemented: the N21 token, a four-stage presale contract, a public website, wallet connection and purchase interfaces, and project disclosure pages. Token and presale source code have been verified on BscScan. Source verification is not an independent security audit. Planned: a commercial Launch Tools platform, paid token utility, treasury reporting exports, dedicated reserve separation, team vesting execution and liquidity deployment. This paper does not assert that these planned items are completed.
3. NOVA21 Launch Tools
The proposed product includes public contract registries, treasury dashboards, downloadable reporting and hosted transparency pages for Web3 teams. Development should prioritize useful tools and verifiable releases. Specific paid N21 functionality, commercial adoption and delivery dates are not guaranteed.
4. Token specification
N21 uses 18 decimals and has a total supply of 21,000,000 tokens. The deployed token has no public mint path. Network: BNB Smart Chain, chain ID 56. The token address is listed in the contract registry below. Holding N21 does not provide an automatic right to treasury assets or project income.
5. Allocation policy
The published policy allocates 25% (5,250,000 N21) to the presale; 25% (5,250,000) to future liquidity reserves; 20% (4,200,000) to community and contributors; 20% (4,200,000) to the development treasury; and 10% (2,100,000) to the team. These are policy allocations, not proof of separate on-chain custody or locked balances. The proposed team schedule is a 365-day wait after the fixed sale end followed by 730 days of linear vesting. A deployed, funded vesting contract is required before describing that schedule as enforced.
6. Presale mechanics
The sale allocation is 5,250,000 N21. Four stages each allocate 1,312,500 N21, at USD-denominated prices of $0.02, $0.03, $0.04 and $0.05. Stages advance by quantity allocated, not by separate dates. Purchases crossing a boundary use each applicable stage price. Full allocation at these nominal prices corresponds to $183,750; this is not a fundraising forecast. Payments are accepted in BNB or BSC USDT. BNB conversion uses the configured price feed and freshness checks; USDT pricing follows the contract's denomination assumptions and carries depeg risk. The minimum purchase is 100 N21, except the exact final remainder; the cumulative maximum is 250,000 N21 per wallet.
7. Schedule and claims
The fixed sale window starts on 27 October 2026 at 03:40:46 UTC and ends on 26 November 2026 at 03:40:46 UTC. Purchased N21 becomes claimable after the fixed end, including an early sell-out. Claim activation is permissionless after the end. This is not a refundable crowdfunding contract: it has no cancellation or refund mechanism. Direct BNB or token transfers do not create a purchase allocation. Use the purchase interface and review wallet transactions.
8. Treasury and proceeds
The designated treasury is a 2-of-3 Safe multisignature wallet. Sale proceeds remain in the presale contract until permitted withdrawal after the fixed end. Unsold-token withdrawal must preserve purchaser claims. The published operating budget for proceeds is 50% liquidity, 25% development, 15% security, infrastructure and professional services, and 10% marketing and support. This budget is a policy, not automatic contract routing. Actual spending, reserve movements and liquidity transactions require separate execution and disclosure. Multisignature custody reduces reliance on a single signer but does not eliminate signer collusion or compromise.
9. Security and operating controls
The purchase interface checks the intended network and reviewed contract configuration, presents quotes, uses protected purchase methods and amount-specific USDT approvals, and reports transaction status. Interface checks complement but do not replace contract protections or wallet review. Public contract source allows inspection; neither tests nor explorer verification constitute an independent audit. Users should confirm the official domain and contract addresses and retain sufficient BNB for applicable fees.
10. Execution priorities
First: maintain the sale interface, documentation and support. Next: publish verifiable allocation execution records, implement and fund the proposed team vesting arrangement, and document liquidity planning and deployment. Product work should proceed through publicly demonstrable Launch Tools releases and user feedback. These priorities are a development plan, not a promise of timing, adoption or exchange access.
11. Material risks
N21 can lose some or all of its value. Risks include smart-contract defects, wallet compromise, treasury decisions, network outages, BNB price-feed disruption, USDT depegging, limited or absent liquidity, execution delays and changes in applicable requirements. There is no guaranteed market price, exchange listing, return or liquidity exit. Presale stage prices are not predictions of secondary-market value. Participants must consider restrictions applicable to them; website access alone is not confirmation of eligibility.
12. Document scope and updates
Version 1.0 — published 28 October 2026. This document describes the reviewed design and disclosed project policy; it is not a live balance statement. Consult the transparency page and blockchain records for current execution. Contract rules govern on-chain behavior; a documentation update cannot change immutable deployed terms. Material changes should be published with an updated version and date.
Contract registry
N21 token0xc5a8eaaa6fc731cdd2168a30ae312608158e62df
Presale0xa9a4276f0e7e0ff0f9abd521dfa11903864cf421
Treasury Safe0xBA4189cDAE8BF2042b36A7879995393dCa22655b
NOVA21