For everyone / PKL
The token
A plain ERC-20 with two deliberate omissions. The absence of a mint function fixes the supply more firmly than any governance rule could, and the absence of an owner means there is nobody who can pause, upgrade or confiscate.
The token
| Property | Value |
|---|---|
| Ticker and decimals | PKL, 18 |
| Supply | 10,000,000,000minted once at deployment |
| Minting after deployment | noneno mint function exists |
| Burning | holder-only burnno allowance-gated burn, so no approved spender can destroy a holder's balance |
| Owner, pause, upgrade | noneimmutability by omission |
| Home | the Pickle L2any L1 representation only through the canonical bridge |
PKL is Pickle's coin. There are exactly ten billion of them, made once, and there is no way to make more: the code to do it does not exist. Nobody controls the coin either, so nobody can freeze it, change it or take yours. You do not need PKL to use the chain; you hold it because it gets a share of what the chain and its apps earn, and because it votes on how the chain is run.
PKL is the ecosystem asset that both fee-sharing flows feed: 30 percent of net gas revenue goes to PKL stakers in ETH, and a 40 percent share of net gas plus 60 percent of the application ecosystem share fund a buyback that burns PKL. Its supply is 10,000,000,000, minted once at deployment, with no mint function and a holder-only burn. It has no owner, no pause and no upgrade path. PKL is a fee-share and coordination asset, never equity, and never a claim on any entity's profits.
A plain ERC-20 with 18 decimals and a fixed supply of ten billion minted in the constructor. No mint function, so supply is fixed by the absence of code rather than by a rule. A holder-only burn that decreases total supply; no allowance-gated burn, because one would let any approved spender, including routers holding routine unlimited approvals, destroy a holder's balance, which on a token with no mint is irreversible in a way theft is not. No owner, pause or upgrade. Its home is the Pickle L2, and any L1 representation exists only through the canonical bridge.
Two deliberate omissions
A defect could not be patched in place
The absence of a mint function fixes the supply more firmly than any governance rule could, and the absence of an owner means there is nobody who can pause, upgrade or confiscate. The consequence is stated plainly: a defect in the token contract could not be patched in place; it would require a migration.
What PKL is for
- Fee share. Staked PKL receives 30 percent of net gas revenue, paid in ETH, never in PKL emissions. The fee-sharing page has the vault.
- Buyback. A standing, revenue-funded bid, at the scale the whitepaper publishes and subject to the float caveat: it reduces total supply, not circulating supply during vesting. The buyback page has the mechanism.
- Utility. Names payable in PKL at a published discount, the ETH schedule being 0.05, 0.025 and 0.005 ETH per year for three-, four- and five-or-more-character names; application registry bonds posted in PKL; priority-lane access keyed to staked PKL.
- Governance. Staked PKL votes on rates, tiers, incentives and treasury spend. The governance page has the rules.
- An index over application revenue. Under the settlement-order rule, every registered application's revenue, whatever token that application launches, routes a share into PKL before its own distributions. PKL's position as that index depends on applications actually registering; unregistered activity contributes gas alone.
What PKL is not
- Not gas. Every fee on Pickle is paid in ETH, permanently. PKL is never required in order to transact.
- Not equity. PKL is a fee-share and coordination asset, never a claim on any entity's profits.
- Not a validator bond. Staking is a fee-share vault. It does not produce blocks, does not secure the chain, and has no slashing.
- Not an emissions token. There are no PKL emissions to stakers anywhere in the design. The whole supply exists from day one and only ever goes down.
Who holds that supply, and when it unlocks, is on the allocation page.