Disclaimer: This article is general information for token teams. It is not legal, financial or investment advice. Rules on buybacks, disclosure and market conduct differ by jurisdiction and by venue, so review any buyback plan with your legal counsel and your own advisers before you start.
Quick answer
What is a token buyback? A token buyback is when a project uses its own funds to purchase its token on the market, then holds, locks or burns the tokens it acquired. Teams can execute a buyback on the order book over time, through an OTC desk or on-chain, and the right choice depends on size, liquidity and governance. A buyback is a treasury and disclosure decision, not a tool for setting or supporting a price.
What a token buyback is, and what it is not
A token buyback is a planned purchase of a project's own token using funds the project controls, such as protocol revenue or treasury reserves. After the purchase, the tokens are usually held in the treasury, locked for a period or sent to a burn address. Each outcome has different effects on circulating supply and on how holders read the program, so the decision should be made and stated before the first purchase.
Some projects run a one-off buyback after a specific event. Others set up a recurring token buyback program funded by a share of revenue. The mechanics are similar in both cases. What differs is the governance behind the decision and how it is communicated.
It helps to be clear about what a buyback is not. It is not a promise about price, and it should not be presented as one. Markets respond to many factors at once, and a buyback is only one of them. Teams that describe a buyback as a way to lift or defend the price create expectations they cannot control and may run into disclosure and conduct issues. The safer framing is simple: the project is using part of its funds to acquire its own token for stated reasons, under stated rules.
Funding, governance and disclosure
Before any execution question, a team needs answers to three basic questions: where the money comes from, who approves the buyback, and what will be said publicly.
Source of funds
Buybacks are usually funded from protocol or product revenue, or from treasury reserves held in stablecoins or other assets. Funding a buyback from reserves needed for operations can shorten the project's runway, so the amount should fit within the wider treasury policy. Write down the funding source and the maximum budget before you begin.
Approval and governance
For a project with token governance, a buyback may need a vote or at least a published proposal. For a company-led project, it may need board or management approval. Either way, the approval should state the budget, the period, the execution method in general terms and what happens to the acquired tokens. Clear approval protects the team when questions come later.
Disclosure policy
Decide in advance what you will announce before, during and after the buyback. Some teams publish the full program terms up front. Others announce the policy and report results afterwards. The right level depends on your jurisdiction, your venues and your legal advice. Consistency matters more than detail: whatever you commit to, do it every time.
Execution options
There are three broad ways to execute a token buyback. They can be combined, and none of them is right for every project.
On the order book over time
The project places buy orders on the exchanges where the token trades, spread over days or weeks. This is transparent and flexible, and it lets the team adjust pace to conditions. The limit is visible liquidity: a fast program on a thin book will affect the market more than a slow one. Teams usually set a pace based on their own observed volume and depth data, with pause rules for unusual conditions.
Through an OTC desk
For a larger amount, the project can buy a block of tokens from a counterparty through an OTC desk at a negotiated price. This keeps the purchase off the public order book and settles it as one documented trade. For background on how these desks work, see what is a crypto OTC desk.
On-chain
If the token trades in decentralized pools, the project can buy through those pools, often from a dedicated, publicly known wallet. On-chain purchases are visible by default, which can support transparency. The team should still pace purchases with pool depth in mind and take care that the wallet's activity is clearly labeled as the buyback.
How a buyback interacts with your market maker
If your token has a market maker, a buyback changes the conditions it quotes into. Buy orders from the project's accounts add demand on the same venues where the market maker maintains spreads and depth. Without coordination, the two activities can work against each other, and inventory on the market maker's side can drift from what was planned.
Brief the market maker before the buyback starts. Share the budget range, the period, the venues and accounts that will be used, and who makes decisions. Agree how the market maker's mandate applies during the window. In most setups the market maker keeps doing its usual job, maintaining two-sided quotes within agreed targets, and does not run the buyback itself unless that is a separate, written mandate.
Keep accounts and balances separate. Treasury purchases and market making inventory should be tracked so that nobody confuses one with the other. Our guide on multi-venue market making inventory explains how teams keep balances aligned across exchanges. If you want a broader view of how liquidity support works, see our market making page.
Timing also deserves care. If a buyback overlaps with an unlock or other supply event, holders may read the two together. Our article on token unlock price impact explains how teams think about those periods.
Communicating with holders
Holders want to know why the project is buying, how much it can spend, over what period and what will happen to the tokens. A short announcement that answers those questions in plain language is usually enough. Avoid language that hints at price outcomes. Phrases about supporting, defending or boosting the price invite expectations the team cannot meet.
During the program, answer questions consistently and point people to the published terms. If plans change, for example if the budget is reduced or the program pauses, say so promptly and explain why. Silence during a public program tends to create more speculation than a clear update.
What to report after the buyback
A buyback report closes the loop. It typically covers the period, the number of tokens acquired, the funds spent, the methods and venues used in general terms, and what happened to the tokens. Where possible, include verifiable references such as transaction hashes or the burn address, so holders can check the figures themselves.
Your market maker's regular reporting can help here. If the market maker shares data on spread, depth and uptime, the buyback period should be visible in that record. Our guide on what to expect from a market making report describes what those reports usually include.
Conclusion
A token buyback works best when it is treated as a planned treasury action with clear funding, approval, execution and reporting. Choose the execution method based on size and liquidity, brief your market maker before you start, and keep holder communication factual and free of price promises. If you would like to discuss how liquidity support could sit alongside a buyback, the EasyMM team is happy to talk it through from our homepage.
FAQ
What is a token buyback?
It is a planned purchase of a project's own token using funds the project controls, after which the tokens are held, locked or burned according to stated rules.
How do token buybacks work in practice?
The team sets a funding source, budget and period, gets the required approval, chooses an execution method, briefs its market maker, executes within agreed limits and reports the results afterwards.
Should a buyback go through the order book or an OTC desk?
Smaller programs are often executed gradually on the order book. Larger amounts may suit an OTC trade. Many teams combine both, depending on size, liquidity and disclosure needs.
How should a market maker be briefed during a buyback?
Share the budget range, period, venues and accounts, and who makes decisions. Confirm how the market maker's existing mandate applies, and keep treasury and market making balances separate.
What should a project disclose after a buyback?
The period covered, tokens acquired, funds spent, methods and venues in general terms, what happened to the tokens and verifiable references such as transaction hashes or the burn address.




