Skip to content

The burn and the $SAGITTA market

Part of every trading fee goes to the burn (see Fees). It accrues as SOL in each market, anyone moves it to the burn vault, an account of Sagitta’s core program, and the vault spends it buying $SAGITTA on its PumpSwap pool and burning what it buys. Deposits returned by closed markets and trimmed rent go to the vault too. Nothing else can spend it.

$SAGITTA has its own UP/DOWN market while the burn runs, a relayed memecoin market like any other. Each burn is a buy, so it lifts the price and pays the UP side. Burns run at slots everyone knows in advance, and their size and their move are capped, so both sides can plan for them.

$SAGITTA launches on pump.fun with SOL as its quote, and trades on its launch curve until it graduates into its PumpSwap pool. Until then nothing burns. The burn share keeps collecting in the vault all the while, and the site shows the vault’s balance and the coin’s address.

Once $SAGITTA has graduated, the timelock names the burner program and the coin’s pool, and sets the most one burn may spend. Like every timelock setting, that takes effect 72 hours after it is scheduled. Burns start once the pool’s first four grid readings are posted (below), and from then on each burn spends from everything the vault has collected, at the rate below.

  • Periods. Burns run in periods of 3,000 slots (about 10 minutes). A burn runs only in slots 150 to 199 of a period (about 10 seconds), at most one per period, and never within 300 slots (about 60 seconds) of the last one. Anyone can call burn, and Sagitta’s keeper calls it in every open window.
  • The window opens about 30 seconds into the period. The period’s own grid reading prices the slot just before the period begins, from finished blocks only, so the wait gives it time to post before the window opens.
  • The market page shows the next burn’s slot, the vault’s balance and what the next burn will spend.
  • The schedule is in slots so that each period’s grid reading has a fixed target. If slots run slower than 200 ms, periods lengthen with them.

Each burn spends the smaller of:

  • 5% of the vault’s free balance: what it holds, less the fees it owes for grid readings and calls (below);
  • maxSpend, a timelock setting, never above 10 SOL. It is kept at or below 0.12% of the pool’s quote reserve, so a burn stays well inside the move cap.

The bought tokens are burned through the token’s own program, so $SAGITTA’s supply falls by at least the burn’s floor, and core checks that it did.

A burn must buy at least a floor set from signed grid readings only, never from the pool’s live price. A grid reading’s target is the last slot before a period opens. Sagitta’s price signers value it by the same rule as every relayed pool reading, at the end of that slot’s leader’s run, and post it to the pool’s grid ring, a ring of core’s that takes grid readings and nothing else. Grid readings are on chain in that ring; GET /api/readings lists the $SAGITTA market’s own readings, the ones its tickets fill at.

  • the fresh term uses the period’s own grid reading and the previous period’s, whichever buys fewer tokens, so one push held across a single grid slot can’t block a burn;
  • the anchor is the median of the three grid readings before the period’s own, less 10%;
  • the quote is the larger of the two. Core takes 15% off it as its floor, and the burner’s swap must return at least that.

Core computes the floor itself, from the four grid readings of the burn’s period, so no caller chooses which readings count. A burn needs all four: one missing grid reading blocks the burns of the 4 periods that use it.

  • A burn that would move the price more than about 0.30% is refused. The buy may lower the pool’s square-root price, in tokens per SOL, by at most 15 basis points below the higher of the fresh grid price and the pool’s price at that moment, about 0.30% on the price itself. A spend too large for that cap fails whole.
  • A burn never pays above its price limit. If the pool already stands above the limit when the window opens, that period’s burn is skipped and the next period tries again.
  • What it pays. A burn moves the price by at most about 0.30%. At 100×, that pays up to about 26% of the DOWN pot to UP.

The burn vault pays for its own upkeep:

  • Grid fee. Whoever posts a grid reading that a burn’s floor uses earns 0.00002 SOL, once per reading. The first burn after a pause pays four; while burns run every period, about one per period.
  • Call fee. Whoever calls a burn earns 0.00005 SOL.
  • Both are fixed in core. No setting changes them, and they are set aside before the burn’s spend is sized, so a spend never uses SOL the vault owes. A burn that would spend less than the fees it pays doesn’t run.
  • Earned fees wait in the vault for their owner to claim. The vault keeps 8 such accounts; a fee for an account with no slot stays in the burn. Fees unclaimed for 90 days after an account’s latest credit can be returned to the burn by anyone, and a claim is never refused for age.

A period passes without a burn when one of its grid readings is missing, when the pool’s price stands above the burn’s limit, or when the spend would not cover the fees it owes. The vault keeps the SOL for a later period, and nothing else can spend it.

The burner program, the coin’s pool and maxSpend are 72-hour timelock settings. The burner only routes the swap and holds the move cap; core keeps every other rule, the schedule, the spend, the floor and the check that the vault paid exactly the spend and the supply fell by at least the floor. A burner must be an immutable program, so it can’t change once named. The timelock can’t withdraw the vault’s SOL, change the fees or choose when a burn runs. See What admins can do.