Skip to content
Solana

Docs · ReelBook · Existing token

Revenue buyback engine

For an app or protocol with real revenue: a buyback pool only its vault may buy, fed by 1% of buys on a second pool.

Buybacks run from trading volume on rules anyone can read, not from a team’s discretion.

Set up now · partial: Zap Relay target, Arb recapture, Zap Relay source2 pools · 2 launches
Sample settings, not live data. Each pool’s board uses the catalog’s defaults plus the recipe’s choices, and passes the builder’s checks. Keys such as payees, mints and feeds are named when you launch.

The pools

The buyback pool (launches first)

Existing token · 1 pool

The feeder

Existing token · 1 pool · the same pair, a second launch · names the vault

How the pools work together

The feeder’s buys pay 1% into a zap vault; when it has gathered enough, anyone can zap it into the buyback pool, which nobody else may buy. Anyone may sell into the buyback pool at any time. The feeder’s recapture reads the buyback pool, its sibling on the same pair (reference 2).

What is coming or partial

  • Zap Relay target (Partial). Partial: the gate is in reel, but the feeder vaults that buy are reel-vaults' zap module (coming), so until it runs nothing can buy the pool.
  • Arb recapture (Partial). Partial: Solana has no in-swap executor callback like Uniswap v4's, so reel charges the swap that closes a gap against a reference price instead of running a partner's arbitrage (PROGRAM.md §12). A stale or missing reference skips it.
  • Zap Relay source (Partial). Partial: the cut accrues on reel and is paid to the zap vault named at launch; the vault that buys the target pool is reel-vaults' zap module (coming).

Steps

  1. Launch the buyback pool first, with no dev buy and no recapture.
  2. Open the feeder as a second launch of the same token on USDC, naming the buyback pool’s zap vault.
  3. The zap vault that buys and burns is reel-vaults' zap module; until it ships, the buyback pool has no buyer.