Token and allocation
One billion SHOOK at construction. Three allocations, one token, and no later minting.
Issuance and units
SHOOK is an ERC-20 token with 18 decimals. One whole SHOOK is 10¹⁸ base units. The constructor mints 1,000,000,000 SHOOK directly to three protocol contracts; there is no token owner and no function to mint more after construction.
| Allocation | Amount | Initial destination |
|---|---|---|
| Formation | 500,000,000 SHOOK · 50% | FormationMarket |
| Permanent liquidity | 250,000,000 SHOOK · 25% | LiquidityVault |
| Staking rewards | 250,000,000 SHOOK · 25% | StakingVault |
Supply can decrease
The token inherits ERC20Burnable. Holders can burn their own tokens, and an approved spender can use burnFrom within its allowance. Therefore one billion is the initial issuance and maximum supply, not a promise that totalSupply will always equal one billion. Burning does not redeem ETH or reserve assets.
Graduation does not burn unused allocation. Remaining formation and liquidity inventory is transferred into the staking launch reward budget.
Transfers and approvals
Transfers use normal ERC-20 accounting; there is no token-level transfer tax in SHOOKToken. Market and game fees are charged by the contracts carrying out those actions. Token allowances authorize a particular spender, so formation, the permanent router, staking, and games use separate approvals.
ERC20Permit supports EIP-2612 signed approvals. A permit changes an allowance; it does not by itself buy, sell, stake, or join a game. The consuming transaction still has to call the relevant contract.
Allocation after graduation
The amount distributed to buyers is the actual circulation at graduation. The permanent liquidity seed is derived from the reserve and marginal curve price. Staking receives its base 250M allocation plus unused formation inventory and any returned liquidity inventory. Read Graduation for the complete handoff.
Source reference
Checked against the source shipped with this documentation. Contract calls and units are detailed in the contract reference.
Imported source files 34
Supporting contracts, interfaces, and libraries imported by the sources above, including their dependencies.