How burns are settled
A burn follows a result in four steps: the source is read, the result becomes final, the burn runs, and the receipt appears. These are the times the code uses for each step.
How often each source is read
A coin settled by a market is read every 5 minutes.
A coin settled by a published data feed is read on that feed's own schedule. A feed with no schedule of its own is read every 60 minutes.
$DEFICIT reads the Treasury's debt figure at 4:30 p.m. and 8:00 p.m. New York time on business days.
When a result counts
A result counts only when it is final.
A game counts when its feed marks it final.
A Polymarket market counts only after its on-chain payout is recorded. That follows UMA's dispute window of about 2 hours, and longer if a proposal is disputed.
A scheduled publisher's number counts when it is posted.
From a final result to the burn
The cycle that sees a final result submits the reading and runs the burn in the same pass.
Before it swaps, the program checks the pool's current rate against its average over the last 10 to 20 minutes. A pool that is already trading has that history.
One burn spends at most 2% of the pool's SOL reserve. The rest carries to the next burn, so a large burn arrives in slices.
Typical times after the event
Sports results and scheduled data: about 5 to 25 minutes.
Polymarket markets: about 2 hours, plus a few minutes.
$DEFICIT: within about an hour of the read that first sees each new Treasury figure, which is posted on the business day after the day it describes.
The receipt
When the burn's transaction confirms, its receipt appears on the coin's page: the memo, the swap's signature and the amount burned.