What it is
Buy-and-burn is a supply-reduction mechanism where a protocol takes a portion of the fees or revenue it earns — from trading, borrowing, gambling, or any other activity it facilitates — and uses that money to purchase its own token on the open market, then permanently removes the purchased tokens from circulation. It differs slightly from a discretionary "buyback program" in that buy-and-burn is usually built into the protocol's smart contracts as an ongoing, rule-based process rather than a one-off decision by a team or DAO.
How it works
- A protocol contract collects revenue in whatever asset users actually pay with — often a stablecoin, ETH, or the base trading pair — as a byproduct of normal usage (swap fees, funding rates, house edge on bets, etc.).
- A defined split (e.g., "20% of protocol fees") is routed automatically to a buy-and-burn contract or keeper bot, rather than sitting idle in a treasury.
- That contract periodically executes a market swap, converting the collected revenue into the protocol's native token via a DEX pool.
- The purchased tokens are sent to a burn address or passed to a
burn()call that reducestotalSupplyon-chain, so anyone can verify the reduction directly from contract state. - Because the burn amount scales with real usage rather than a fixed schedule, token holders can trace scarcity directly to protocol activity: more volume or revenue means more tokens burned per period.
- Over time, assuming demand for the token doesn't fall faster than supply shrinks, each remaining token represents a growing claim on a shrinking pool — the crypto-native equivalent of a corporate share buyback funded by operating cash flow.
Why designers use it
- Ties token scarcity mechanically to protocol usage, giving holders a legible, hard-to-fake link between "the product is being used" and "the token should be worth more."
- Avoids the regulatory and tax complexity of paying holders a cash dividend by returning value through supply reduction instead.
- Automating the process in a smart contract removes discretion, so holders don't have to trust a team to actually execute buybacks.
- Creates continuous, usage-proportional buy pressure that can help offset sell pressure from emissions, vesting unlocks, or general market selling.
Failure modes
- Revenue too small: if actual protocol revenue is tiny relative to token market cap, the burn has negligible price impact and functions as marketing rather than economics.
- Deflation theater: a protocol can burn tokens it never intended to circulate (unsold allocations, unclaimed emissions) and market this as "buy-and-burn" even though no real revenue-funded purchase occurred.
- MEV and slippage: on-chain periodic buys of a predictable size and timing are easy for bots to front-run, extracting value that should have gone to burn efficiency.
- Revenue-supply mismatch: if usage (and thus burns) is highly cyclical while token supply issuance elsewhere is constant, the mechanism can look strong in bull periods and irrelevant in bear periods.
- Treasury starvation: routing too much revenue to burns instead of runway, security audits, or incentives can leave the protocol under-resourced for development or emergencies.
What to check before using it
- Compare the dollar value of periodic burns to daily trading volume and market cap to judge whether the mechanism can plausibly affect price.
- Confirm the burn is executed on-chain and auditable (burn address balance or
totalSupplyhistory), not just reported in a dashboard. - Check whether burned tokens come from real, ongoing revenue versus a one-time treasury or unallocated-supply source.
- Look at how the buy execution is protected against front-running or sandwich attacks (TWAP execution, private mempools, randomized timing).
- Verify the revenue split is fixed in the contract (or governance-controlled with transparency) rather than an off-chain promise a team can quietly stop honoring.