What a Token Buyback Program Actually Is
A token buyback program is a standing commitment by a project to use revenue or treasury funds to purchase its own token on the open market. What happens next is the part teams get wrong: the tokens can be burned (sent to an unrecoverable address and removed from supply), held in the treasury, or redistributed to stakers and liquidity providers. Those three choices produce very different outcomes, and "buyback and burn" is announced far more often than it is thought through.
The appeal is obvious. A buyback converts protocol revenue into visible, verifiable demand for your token, and it gives holders a reason to care about the business rather than the narrative. The risk is equally real: a buyback funded from a treasury that has no recurring revenue is just a slow sale of your own runway, and a badly executed buy program tells the whole market exactly when and where you will be buying.
This guide covers the three structures, how to decide which one fits your project, how to fund a program honestly, and the execution mechanics that determine whether you get value for the money you spend.
Buyback and Burn vs Buyback and Hold vs Buyback and Redistribute
All three start the same way — the project buys tokens on the market — and diverge entirely at the point of what happens to those tokens.
| Buyback and burn | Buyback and hold | Buyback and redistribute | |
|---|---|---|---|
| Effect on circulating supply | Permanent reduction | Removed from circulation but recoverable | Returns to circulation with recipients |
| Reversibility | None. This is the point and the risk | Full. Treasury can redeploy | Partial |
| Who benefits | All holders, proportionally and passively | The project first, holders indirectly | Stakers, LPs, or whoever the program targets |
| Signal sent | Confidence, permanence, deflationary intent | Prudence, optionality | Direct reward for a specific behaviour |
| Main failure mode | Destroying capital you later need | Community reads it as a sale waiting to happen | Attracts mercenary capital that leaves when yields drop |
| Best suited to | Mature protocols with durable revenue | Projects with uncertain revenue or future capital needs | Protocols that need to reward a specific behaviour, such as liquidity provision |
A few honest observations on the trade-offs.
Burning is a one-way door. Tokens sent to a burn address cannot fund a future exchange listing, a market making inventory, an ecosystem grant, or an emergency. Teams routinely underestimate how many future obligations a treasury quietly carries. Burn only what you are confident you will never need, and size the program so that a bad year does not force you to sell other assets to cover operations.
Holding is defensible but must be explained. Repurchased tokens sitting in a treasury wallet look, to the market, exactly like a future sell wall. If you choose this route, commit publicly to what the tokens can and cannot be used for, put them behind a timelock or multisig with a published policy, and label the wallet so on-chain trackers do not misread routine transfers as distribution.
Redistribution is a yield program wearing a buyback costume. It can be the right choice — routing bought tokens to liquidity providers deepens your order books and reduces the cost of the very market you trade in — but be clear internally that you are buying a behaviour, not reducing supply. If you stop, the behaviour stops with it.
A fourth option deserves naming: do not run a buyback at all. For most pre-revenue projects, capital spent on buybacks buys a short price effect and nothing durable. The same money spent on engineering, listings, or deeper liquidity usually compounds better. A buyback is a way to return value to holders once you have value to return. It is a poor substitute for having a business.
How to Fund a Buyback Program Without Fooling Yourself
The funding source determines whether a buyback is sustainable or is quietly a liquidation. Three broad sources, in descending order of durability:
- Protocol revenue. Trading fees, subscription income, interest margin, sequencer revenue — money the protocol earns from users. This is the only source that can support an open-ended commitment, because it refills.
- Treasury stablecoins. Fixed and finite. Spending stablecoins on buybacks reduces your operating runway one to one. This can be a legitimate one-off use of surplus reserves, but it should be framed as a discrete program with a defined size, not an ongoing policy.
- Sales of other treasury assets. Selling BTC, ETH or investment positions to buy your own token concentrates treasury risk at exactly the moment you would want it diversified. Very hard to justify.
Before you commit to any recurring program, run the numbers under a downside case. If revenue fell by half and your token price fell by two thirds, would the program still be affordable, and would you still want to be buying? A commitment you have to abandon in a drawdown does more damage to credibility than never making it. This is where buyback policy and treasury management have to be designed as one thing rather than two.
Consider expressing the commitment as a percentage of realised revenue rather than a fixed currency amount. "We allocate 20% of protocol fees to buybacks each quarter" scales down naturally in bad periods without requiring you to break a promise. "We will buy $500,000 of token per quarter" does not.
Execution: The Part Most Teams Get Wrong
A well-designed program can still waste most of its budget in execution. Buying your own token is a trading problem, and it has all the usual hazards plus a few specific to this situation.
You are the most predictable buyer in the market
If you announce a fixed size, a fixed schedule and a single venue, you have told every trader on that venue when to front-run you. The market prices the buy before you make it, you fill higher, and the price gives it all back once you stop. Vary timing within a window, use more than one venue where liquidity allows, and publish results after the fact rather than intentions in advance.
Market impact eats the budget
Executing a large buy as a single market order walks the book and fills you at a much worse average price than the quoted top of book. The cost is real and it is proportional to how thin your order books are. Splitting the order over time — a TWAP-style execution, meaning the buy is spread evenly across a set period — reduces this substantially. If you do not understand how much slippage your own size causes, you cannot know whether your buyback delivered value or simply paid the spread to more sophisticated participants.
Buybacks interact with everything else you are doing
A buyback executed in the same week as a large token unlock is, functionally, the project buying tokens from its own insiders with protocol revenue. That may be defensible, or it may be exactly the optics you cannot afford. Map buybacks against your unlock schedule, ecosystem distributions and any market making inventory movements before you set the calendar.
On-chain and off-chain buys behave differently
Buying through an automated market maker is transparent and easy to verify, which is good for credibility, but the transaction sits in the mempool for anyone to see and act on, and the pool depth caps your realistic size. Buying on centralised order books gives you better depth and execution control at the cost of verifiability — which you can recover by publishing exchange statements or a signed attestation after each program period.
Do not create a false market
There is a bright line between buying your own token as a disclosed capital-allocation policy and trading it to create a misleading impression of demand. Buybacks that are timed to defend a specific price level, coordinated with announcements, or run through undisclosed accounts move toward the second category and can attract regulatory attention in many jurisdictions. Keep the policy public, keep the execution boring, keep the records, and take legal advice in your relevant jurisdictions before you launch.
A Decision Framework
Work through these in order. If you fail an early one, the later ones do not matter.
1. Do you have recurring revenue that is not itself token emissions? No — do not run a recurring buyback. Revisit when you do.
2. Is your treasury runway comfortable for at least 18 to 24 months after the program? No — the program is too large. Cut it or defer it.
3. What problem is the buyback solving?
- Returning value to holders from real earnings — burn or hold both work.
- Offsetting emissions — size it against actual emission rates, and be honest publicly if it only offsets part.
- Supporting the price — this is not a buyback strategy. Reconsider.
4. Will you ever need these tokens again? Yes, or unsure — hold rather than burn. You can always burn later. You can never unburn.
5. Are your order books deep enough to absorb your intended size without visible distortion? No — fix liquidity first. Buying into thin books is expensive and produces a price move that reverses as soon as you stop.
6. Can you commit to publishing what you did, every period, including the periods when you bought nothing? No — do not announce a program at all. An abandoned buyback is worse than no buyback.
Pre-Launch Checklist
Before the first buy:
- Funding source named, with a downside scenario modelled
- Program expressed as a percentage of revenue, or as a clearly bounded one-off
- Destination decided and documented: burn address, timelocked treasury wallet, or distribution contract
- Execution venues and method chosen, with an impact estimate for your intended size
- Calendar checked against unlocks, listings, emissions and other treasury activity
- Wallets labelled and disclosed so on-chain observers do not misread transfers
- Legal review completed for your jurisdictions
- Reporting format and cadence agreed in advance, including what you will report in a quarter with no buying
- A defined circumstance in which the program pauses, published up front
Where Buybacks and Liquidity Meet
The recurring theme above is that a buyback is only as good as the market you execute it into. Thin books make every buy expensive and every price effect temporary. Deep, consistent two-sided liquidity makes a buyback cheaper to run, harder to front-run, and more likely to leave a durable mark on price discovery rather than a spike that fades in a week. It also gives you the data to measure what the program actually cost you in impact and spread.
Fibonacci Capital works with token projects on exactly this intersection — designing liquidity that can absorb treasury activity, and executing buy programs in a way that does not hand the value to faster participants.
If you are planning a buyback program and want to understand what it will cost to execute properly in your current market, get in touch and we will walk through it with you.