Allocation
Every WEED token is assigned at genesis to one of three explicit vault destinations.
#Allocation table
| Allocation | WEED | Share |
|---|---|---|
| Base farming rewards | 316,848,000 | 75.44% |
| Referral rewards | 69,552,000 | 16.56% |
| Liquidity bootstrap | 33,600,000 | 8% |
| Total | 420,000,000 | 100% |
Base and referral amounts add to 386,400,000 WEED, or 92% of total supply. Adding the 33,600,000 WEED bootstrap reserve conserves the full 420,000,000 WEED supply.
#Atomic genesis distribution
The token constructor requires three nonzero, distinct destinations. It mints each exact amount, checks total supply, and emits one GenesisAllocation event. There is no intermediate team wallet in that constructor flow.
#No hidden allocation
The genesis allocation defines no private or team allocation. The token also defines no later mint, transfer tax, blacklist, transfer pause, maximum-wallet rule, or migrator. These are properties of the current allocation and token code, not a statement about external integration risk.
#Vault controls
Each budget vault blocks recovery only for the token address currently stored in budgetAsset. After correct initialization with WeedToken, that guard rejects WEED recovery and the farming and referral release counters cap their normal protocol payout paths.
Before initialization, budgetAsset is zero, so an administrator can recover the newly minted WEED as an unrelated token. Initialization also accepts any token whose vault balance equals the numeric BUDGET constant; it does not require the WeedToken address.
#Bootstrap custody blocker
The current bootstrap vault releases WEED to any nonzero recipient selected by its operator, subject only to the two WEED sub-caps. It does not create or validate a WEED / USDG or WEED / WETH position and does not send an NFT to LiquidityNFTLocker atomically.