Revenue-Funded Token Buybacks: Where the Money Comes From

A revenue-funded buyback is paid for with money the product earns from users, not with money raised by selling the token. That makes it more durable than a treasury buyback, but its size is capped by real usage. The first thing to check in any programme is therefore the revenue base, not the burn percentage.

Three ways to fund a buyback

Funding source	How it works	Strength	Weakness
Product revenue	Fees or margins from users flow to a vault	Tied to real activity	Small if usage is small
Treasury reserves	The project spends money it already holds	Can be large at once	Finite; may come from earlier token sales
Token sales	Proceeds of selling the token fund buying it	Easy to announce	Circular: sells with one hand, buys with the other

Many programmes mix the three without saying so. Tracing the source is how you tell a business from a pattern.

Why circular buybacks are a problem

If a project sells $1 million of its token and spends $200,000 buying some back, the net result is $800,000 of new selling pressure and a nice announcement. That is not necessarily dishonest, but it is not value returned to holders. It is a partial reversal of a sale.

Revenue-funded designs avoid that circularity at the buyback step. The money comes from outside the token market. But look again at what else the product does with the token. The bitcoin.one whitepaper notes that each shop purchase sells BC1 for the full order value, while the buyback is only the 2% margin, so buybacks offset only part of that selling. It is rare and useful that a project writes this down.

Key takeaway: Revenue-funded does not mean net-buying. Compare the fee that funds the buyback with the other flows the same product creates.

A concrete funding model

According to the project’s own pages, bitcoin.one’s flow is as follows.

• Sending BTC or BC1 through the app costs no app fee.
• Gift-card purchases in the shop carry a 2% service margin, paid in USDC.
• 100% of app fees go to the BuybackVault, which buys BC1 on the market.
• Of the BC1 bought, 50% is burned and 50% goes to the rewards pool.

So “100% of app fees” really means “100% of a 2% margin on shop purchases”. The whitepaper confirms the shop margin is the only app revenue stream. In dollars, then, the buyback scales with how much people spend in the shop. If that is little, so is the buyback. Our calculator example works through this using the whitepaper’s own illustrations.

This is not criticism. A small, transparent, usage-linked buyback is a legitimate design. It just must not be confused with a large one. The project says so itself: its risk disclosure notes that the amount depends on app usage.

Questions that expose the funding model

1. What exactly is the fee? A percentage of what, charged to whom?
2. Is the fee optional? If users can avoid it, revenue may fall.
3. Is revenue in a stablecoin or in the token? Fees collected in the token itself are not a buyback at all.
4. How much has it collected? Look at the vault inflows in the explorer.
5. Is the product live? On a test network, activity has no real value. The bitcoin.one app is on a testnet today, and its buybacks page was showing no totals when we looked.

Revenue-funded versus value-accruing

A revenue buyback is not the same as giving holders a share of revenue. The money buys tokens on the market. It may support the price and shrink supply, but it does not pay holders directly. That is also why the comparison with stock buybacks is only partial: owners of shares have claims on cash flow, and token holders usually do not.

What a healthy revenue link looks like

• A named, simple revenue source
• A fixed, published percentage going to the vault
• An on-chain record of inflows
• A statement of what the revenue is not (for example, not a promise of price)
• Honest disclosure of other flows that work the other way

If the project cannot show real revenue yet, as is common before launch, the sensible stance is to treat the buyback as a plan, not a track record.

Summary

Funding is the foundation of any buyback. Product revenue is the strongest source because it comes from outside the token market, but it is limited by usage and may be dwarfed by other flows. Before judging a burn percentage, find the revenue it applies to. For a transparent example of this chain, read the BC1 buybacks page and its whitepaper, remembering that this is a testnet-stage project and that nothing here is advice to buy any token.

As a further reference, the project’s whitepaper states the fee mechanics and the contract ceilings in one place, which makes it easy to compare with the explorer later. A closing thought on incentives: when buybacks come from revenue, the team has a reason to grow the product, since more usage means a bigger buyback. When they come from the treasury or from token sales, the incentive points the other way, towards announcing purchases rather than building anything. That does not prove intent in either direction, but it explains why careful readers weight the funding source above nearly every other detail of a programme.

A related caution concerns timing. Revenue arrives continuously, but a vault may hold it for a while before buying, so inflows and purchases can differ on any given day. That is normal. What is not normal is a vault balance that grows for months without being spent, or one that is drained in a single day. Neither pattern proves wrongdoing, but both are worth asking about. Examples of fee-linked designs vary, and our walk-through of how payments app fees link to buybacks shows one case in which a single margin on shop purchases is the entire funding source.