Tokenomics — fixed maximum supply: 500,000,000 YUID
No inflation beyond the fixed cap. Three allocations only — every other protocol function is funded from Treasury.
Supply ledger, on chain
What exists, what has been released against each allocation, and what has been retired.
The supply ledger is not initialized
Until initialize_token_config has run there is no ledger to report — a different thing from one reporting zero.
Genesis custody, on chain
The three allocation vaults, read from the accounts themselves. Every one is held by a program-derived address — no key can move them.
No mint to read vaults for
The vault addresses derive from the mint, and the supply ledger has not reported one yet.
Where one activation fee goes
The fee and its four shares, read from the protocol's own settings. Every destination is an address the program itself controls — no person holds a key to any of them.
Reading the parameters
Waiting on the chain.
Community
60%Economic rewards, network contribution, referrals, liquidity and staking incentives. Released through the E-4 emission path, bounded by a per-window ceiling.
Treasury
30%Development, infrastructure, liquidity, audits, ecosystem and operations.
Team
10%Long-term contributor allocation with a cliff and linear vesting.
Supply composition
Share of the 500M maximum supply
- Community300.00M · 60%
- Treasury150.00M · 30%
- Team50.00M · 10%
Emission
Reading the chain…
Team allocation
50M YUID (10%) with 10M at TGE — 2% of maximum supply — and 40M vested over a 12-month cliff followed by 24-month linear vesting. The TGE has been released on Devnet; the vesting schedule dates from the supply ledger’s genesis, not from each grant.
View vesting timeline →Allocations are the canonical V5 model — 300M Community, 150M Treasury, 50M Team — and are protocol constants, not a projection. Supply and emission above are read from the chain.