Token Buyback vs Token Burn: What Is the Difference?

A token buyback is a purchase: a project spends money to buy its own token from the market. A token burn is a removal: tokens are permanently taken out of supply. The two are often bundled together, but they are separate steps with different effects, and a project can do one without the other.

Two steps, two different effects

Think of a buyback as the cash going out and the burn as the tokens going away. When a project spends $10,000 buying its token, it adds buying pressure for that moment, but the tokens still exist. They are simply in a different wallet. Only when they are destroyed does the total supply fall.

This distinction explains why headlines such as “project buys back and burns 5 million tokens” are really two claims. The first claim can be checked by looking at swap transactions. The second can be checked by comparing total supply before and after, or by confirming the destination address of the tokens.

Action	What happens	Supply effect	What to check
Buyback	Funds are swapped for the token on a DEX or exchange	None by itself; tokens change hands	Swap transactions, amounts, dates
Burn	Tokens are destroyed or sent to an unspendable address	Total supply falls	Total supply, burn address balance
Buyback to rewards	Bought tokens are paid to stakers or users	None; circulating supply may rise again	Recipient contract and payout schedule
Buyback to treasury	Bought tokens are held by the team	None; the team can sell later	Treasury wallet and its policy

Where the tokens go after a buyback

A buyback plan is only as meaningful as the answer to “then what?”. There are four common destinations.

1. Burned. Supply shrinks. This is the cleanest outcome for anyone who cares about scarcity.
2. Distributed as rewards. The tokens go to stakers, cashback programmes or liquidity providers. The buyback absorbs market supply first, but the tokens return to holders’ hands.
3. Held in a treasury. The tokens are off the market for now, though the project could resell them.
4. Locked. A time-lock or vesting contract holds them, which is more credible than a treasury wallet if the lock is public.

A published example of a split design is the BC1 token of the payments app bitcoin.one. Its buybacks page states that of the BC1 bought back, 50% is burned and 50% goes to a rewards pool. That means only half of each buyback shrinks supply, while the other half pays for staking rewards and, according to the whitepaper, cashback from a later date. Whether you like that split is a matter of taste, but you can at least read it and reason about it.

Key takeaway: Ask two questions separately. “Did the project actually buy?” and “What happened to the tokens afterwards?” A strong answer to the first says nothing about the second.

Why projects mix both

Pure burns need tokens to burn. A project that holds a large treasury of its own tokens can burn from that pile without buying anything, which costs no cash but also reflects no demand. A buyback, by contrast, converts real revenue into market demand. Doing both means revenue funds purchases, and part of the purchases are destroyed.

For a revenue-funded design, the order matters. Money first has to exist, which is why the question of where the buyback money comes from deserves more attention than the burn percentage. A big burn percentage applied to a trickle of fees is still a trickle.

How to read a supply claim

Burns can be confusing because tokens live on several chains and in several states. A few habits help.

• Look at total supply on the home chain. If the contract has no mint function, as bitcoin.one says of BC1, supply can only go down. Our note on deflationary tokens without a mint function goes through what that really guarantees.
• Separate burned from locked. Locked tokens return when the lock ends. Burned tokens do not.
• Compare against unlocks. Supply that is burned slowly while a treasury unlocks quickly may still be net inflationary. See vesting versus buybacks.

Common misunderstandings

“A burn raises the price.” A burn reduces the number of tokens. Price depends on demand as well, and demand does not rise just because supply fell. Fewer tokens can be worth less in total if interest disappears.

“A buyback is the same as a dividend.” Not usually. A stock dividend pays owners cash. Most token buybacks do not give holders a legal claim on anything. We compare the two in token buybacks versus stock buybacks.

“If it says 100% it is all buyback.” The percentage normally applies to a specific fee base. For BC1, the page says all app fees go to buybacks, but its whitepaper explains the only app revenue stream is a 2% margin on shop checkouts, and that sending BTC or BC1 is free. So “100% of fees” can still be a small number in dollars.

A quick way to compare two programmes

Put the following facts side by side before judging either.

• Source of funds, and its size per month
• Who triggers the purchase: a contract, a keeper bot or a person
• Percentage burned, percentage distributed, percentage held
• Whether the contract owner can withdraw the funds
• Whether a block explorer shows every step

For bitcoin.one, the whitepaper states that the vault owner cannot withdraw USDC or BC1 and that this is enforced in code. That is a claim from the project itself and the contracts had not been externally audited at the time of writing, according to its risk disclosure. Verify before relying on it.

Bottom line

Buyback and burn are partners, not synonyms. The buyback is the demand-side action and the burn is the supply-side action. Read each claim separately, find the contract, and treat the split between burn and rewards as design information, not as a promise about price. If you want to see how one project lays this out, the BC1 buybacks page is a readable reference, with the caveat that its figures refer to a test network until mainnet launch.

A final suggestion is to keep a one-line summary for every token you read about: what is bought, with what money, and what is then done with it. If you cannot write that sentence from the project’s documentation, the programme is not yet explained properly. Over time you will notice that the clearest projects write this sentence for you.