Treasury · buyback & burn
Every fee. Every burn.
On-chain.
snapshot — · refreshed …
numbers below come from program accounts and confirmed transactions
00The burn engineLOADING
Reading the blockchain…
$OFB burned so far · on-chain
0
0 BUYBACKS
NO BURNS YET
The furnace only lights up for a confirmed buyback (BuybackExecuted event) whose transaction really contains an SPL Token burn of the reported amount. It never animates for simulated or pending activity.
01Burn statistics
$OFB bought back
0
received in verified runs
$OFB burned
0
SPL burn by the program
% of current supply
—
mint not configured
% of initial supply
—
unknown for this mint
Lifetime buyback spending—
Burn vaultnot created (prelaunch)
$OFB mintnot launched
Trust model of the buyback
Run by a permissioned keeper key, limited by the program: max — per run, at most every — min, and every run must burn at least — (no floor set: buybacks refused) (on-chain price floor). Reserve SOL can only leave inside a transaction that burns at least that much; otherwise the whole transaction reverts. Raising these limits or replacing the keeper is announced on-chain and takes effect only after the timelock. Above the floor the keeper still chooses route and price, so this is not trustless.02Fee statistics
Per-asset ledgers are kept separately. SOL and token fees are never added together.
03Daily fee inflows · SOL · 30 days
Buyback reserve (50%)Treasury (50%)30d total 0 SOL
04Buyback reserve
Last executed buyback: none yet
05Verifiable burn history
No buybacks executed yet. Nothing here is simulated.
06Operating treasury
Outflows (withdrawals)
No withdrawals.
Inflows are the treasury half of every fee (chart above). Withdrawals require the treasury authority's signature and can only touch the treasury vaults — never the buyback reserve or the funds locked in offers.
07Public addresses & authorities
Config not indexed yet.
The admin and authorities are single keys on this test deployment. For mainnet they should be multisigs (see docs/MAINNET-READINESS.md).