Token Sink
Pronunciation: TOH-kun SINGK
Definition
A token sink is a mechanism that removes tokens from active circulation or creates recurring demand by requiring users to spend, burn, lock, redeem, or commit them. Examples include fees, subscriptions, game crafting, upgrades, collateral, governance locks, repayments, and asset creation. A sink does not necessarily reduce total supply: tokens sent to a treasury can reenter circulation, locks can expire, and ongoing issuance can exceed the amount permanently removed.
Overview
A token sink is an economic or protocol mechanism that takes tokens out of freely available use or requires them for a recurring action. A permanent burn reduces recognized supply, while a lock only reduces active liquidity for a period. Payments to a treasury create demand but are not permanent removal because the treasury may spend the tokens later.
Sinks appear in many designs. A network can burn transaction fees, an application can charge tokens for access, a game can consume items during crafting, a lending protocol can require repayment, and governance can require long-term locking for voting power. The useful classification records what happens to the units after use rather than labeling every fee or payment as deflationary.
Analysis should measure gross sink volume, permanence, destination, lock duration, treasury recycling, user benefit, and replacement issuance. The net effect on token supply and market liquidity depends on all of those flows. A growing sink can coexist with rising circulation when minting, rewards, or unlocks add tokens faster.
A sink can support demand when users receive durable utility, but an excessive or artificial charge can reduce adoption. Governance may also redirect or disable the mechanism. Teams should distinguish protocol-enforced rules from discretionary issuer policy and monitor upgrades that change rates, exemptions, destinations, or burn behavior.
For example, a fee that sends half to an inaccessible burn mechanism and half to a treasury contains two different flows. Supply reporting should record the burn separately, while treasury analysis tracks the spendable portion. Combining both as “burned” would overstate scarcity and hide administrator-controlled inventory.
Operational records should connect each sink event to the asset, contract, amount, destination, permanence, and business action. Comparing sinks with token emission and unlock schedules gives treasury and product teams a more useful view of net circulating pressure than promotional burn totals alone.
Key Takeaway
A token sink affects demand or circulation only according to its permanence, destination, user value, treasury recycling, and offsetting issuance.
Sources
- EIP-1559: Fee Market Change — Ethereum Improvement Proposals (2026-08-02)
- Ethereum Monetary Policy — Ethereum Foundation (2026-08-02)