Onchain Atlas

Fee Buyback And Burn

A protocol routes the fees it earns from usage into buying its own token off the market and destroying it, tying token scarcity directly to how much the protocol is used.

Also called: revenue buyback and burn · protocol-owned buyback · fee-funded burn

What it is

Fee buyback and burn is a mechanism where a portion (often all) of the trading, borrowing, or other fees a protocol collects from its users is automatically used to purchase the protocol's native token on the open market, and that purchased token is then permanently destroyed (burned). It's a way of converting real protocol revenue into direct, mechanical demand for the token and a shrinking total supply, rather than just accumulating fees in a treasury or paying them out as yield.

How it works

  1. Users generate fees by using the protocol — trading on an exchange, opening leveraged positions, borrowing, or similar activity — and those fees accumulate in the protocol's fee-collection contract, typically denominated in a stablecoin or the base trading asset.
  2. On a schedule (per epoch, daily, or triggered manually/by keeper bots), the accumulated fees are swapped on the open market for the protocol's native token, usually via an AMM or aggregator route.
  3. The purchased tokens are sent to a burn address (or to a contract that calls a token-burn function), permanently removing them from circulating supply.
  4. Because the buy happens on the open market, it creates real, visible buy pressure proportional to protocol usage — more usage means more fees means more buy-side volume for the token.
  5. The burn reduces total supply, so if demand for the token stays constant or grows, each remaining token represents a slightly larger claim on... nothing directly, unless the token also carries other rights — the burn's effect is purely on supply, not a distribution of value to holders.
  6. Some designs make the buyback rate transparent and verifiable on-chain (e.g., a public dashboard tracking cumulative burned supply against cumulative protocol revenue), which lets holders audit whether the claimed link between usage and burns is real.

Why designers use it

  • Creates a mechanical, non-discretionary link between protocol success (fee revenue) and token scarcity, which is easier to reason about than promises of "future value accrual."
  • Avoids direct dividend-like payouts to holders, which can raise securities-law concerns in some jurisdictions, while still returning value to the token indirectly through scarcity.
  • Gives the market a transparent, auditable signal of protocol health: rising burn rates suggest rising usage.
  • Can be combined with staking or fee-sharing so token holders get both a yield stream and a supply-reduction effect from the same revenue.

Failure modes

  • Burning tokens does not guarantee price appreciation — if sell pressure (from unlocks, farming, or panic) exceeds the buyback volume, price can fall even as supply shrinks.
  • If fee revenue is small relative to the token's market cap, the burn is negligible and mostly serves as a marketing narrative rather than a meaningful economic force.
  • Buybacks executed via predictable, on-chain transactions can be front-run by MEV bots, capturing some of the value that was meant to accrue to the protocol's ecosystem.
  • Discretionary or manually triggered buybacks (rather than automatic ones) can be delayed, skipped, or manipulated in timing by whoever controls the trigger, undermining the "mechanical" trust story.
  • Buying back and burning during periods of low liquidity can itself cause outsized price impact, creating misleading price signals disconnected from genuine demand.

What to check before using it

  • Verify whether the buyback-and-burn is automatic and enforced by code, or discretionary and dependent on a team or multisig actually executing it.
  • Compare projected fee revenue to token market cap to assess whether the burn rate will be economically meaningful or just a marketing talking point.
  • Check the execution route (which DEX, what slippage tolerance) for MEV exposure and price-impact risk, especially for smaller-cap tokens.
  • Confirm burns and fee flows are publicly verifiable on-chain, not just claimed in a dashboard that could misreport figures.
  • Consider whether direct fee-sharing to stakers might align incentives more directly than a burn, depending on your regulatory and community goals.

Experiments that used it · 2

Shown oldest first, so you can watch the design evolve.

Deri Protocol
Cross-chain decentralized derivatives protocol that was the first to implement 'everlasting options' on-chain, pricing perps and options against pooled LP capital via an oracle-fed proactive market maker (DPMM).
2021 technically successful commercially unsuccessful
Whales Market
Collateralized peer-to-peer pre-market DEX on Solana that let traders buy and sell pre-TGE token allocations and airdrop points, turning the 2024 'points meta' into an on-chain forward market.
2024 partial success