An approved allocation policy for all 21,000,000 N21. The sale allocation is funded; the remaining categories are a policy for existing treasury holdings, not deployed lock contracts.
Full token distribution
Public presale25% · 5,250,000 N21
Future liquidity reserve25% · 5,250,000 N21
Community & contributors20% · 4,200,000 N21
Project development treasury20% · 4,200,000 N21
Founders & developer team10% · 2,100,000 N21
On narrow screens, swipe the table horizontally to see execution status.
Allocation
Share
N21
Execution status
Public presale
25%
5,250,000
Funded in the sale contract
Future liquidity reserve
25%
5,250,000
Allocation policy; pool not created
Community & contributors
20%
4,200,000
Allocation policy; programs not launched
Project development treasury
20%
4,200,000
Allocation policy; spending reports pending
Founders & developer team
10%
2,100,000
Allocation policy; vesting not deployed
Total
100%
21,000,000
Fixed existing supply
Team allocation: 10%, earned over time
The approved team allocation is 2,100,000 N21. The implementation plan uses the fixed sale end as the reference: no release for 365 days, then linear release over 730 days. There is no accumulated lump-sum release at the end of the waiting period.
Execution pending: beneficiaries and individual shares must be named before a vesting contract is deployed and funded. Until verified funding is published, these tokens remain treasury-held and are not time-locked.
The planned implementation uses OpenZeppelin VestingWallet. Its ownership can be transferred; we will not describe the beneficiary control as non-transferable.
Treasury, community and liquidity
Planned
Community rewards
Reward accepted contributions: documented bug reports, reviewed translations, technical documentation and original educational work. Each program needs a public budget, eligibility rules and evidence of completion. No passive holding yield is promised.
Planned
Development treasury
Fund development, operations and disclosed partnerships through the Safe. Publish monthly spending summaries. Salaries and contractor payments are separate from the team token allocation and must be disclosed.
Planned
Future liquidity
5,250,000 N21 are reserved by policy for future liquidity. A token reserve alone is not a trading pool: paired USDT or BNB, pool parameters and custody terms must be published before launch. No listing price or liquidity lock is currently committed on-chain.
Use of sale proceeds
Approved initial budgeting policy for actual collected BNB and USDT, not assumed future proceeds. Show gross receipts, separately itemized costs and actual spending in treasury reports. The sale contract permits treasury withdrawals only after the fixed sale end.
Purpose
Budget share
Initial liquidity
50%
Product development
25%
Security review, infrastructure and professional costs
15%
Marketing and support
10%
These budgets are operating policies, not smart-contract spending restrictions. Any future policy revision should be published with its date and rationale. Token allocations do not grant a claim on project revenue.
Review before you connect.
Read the token distribution, verify the contract addresses and understand the claim schedule.