BETA · Fuji Testnet
SNOWFORGE

Buyback & Burn

TL;DR

When a creator picks Buyback & Burn as the fee destination, every single trade triggers an internal buyback using that trade's own creator fee, and the bought tokens are sent to 0xdead. There is no bot, no external swap, no minimum threshold — the fee and the burn happen on the same transaction.

The mechanism

  • Pre-graduation: the pool's own bonding curve math is used to swap the fee AVAX for tokens. Same curve, same block.
  • Post-graduation: the migrated SnowPair uses its own AMM math (the BUYBACK_SELF_MARKER sentinel signals the pair to keep buying back internally). The behaviour carries across graduation seamlessly.
  • Dust carryover: when the fee is too small to mint a whole token, the amount rolls forward and is added to the next trade's buyback. Nothing is lost.
  • Burn address: 0x000000000000000000000000000000000000dEaD.

Why the old threshold model is gone

The previous implementation waited for accumulated fees to cross ~1 AVAX before triggering a buyback via an external bot. Two problems: burns clustered in bursts, and failed bot runs could strand fees. Per-trade buyback removes both.

UX

  • Buybacks terminal tab — shows the running burn total, per-trade burns as they happen, and the cumulative token supply removed.

Contract

BuybackBurnDeployer0x0317…cEB6 is the factory for bonding curves with pool-as-destination semantics.