View the raw observation JSON (opens the raw observation record)
Not enrolled. the split does not pay the protocol's collection wallet 8SvEu1bvkhgaSkZW4XHLzfw8djd748KAVHMwvkYGfyr8 at all. The config is admin_revoked, so its split is permanent and this coin cannot enroll.
the sharing config names this coin
expected 8FhAXv2tfXUpyMbJsHDHX9zfiEb9PERzFWSY9sgLpump | actual 8FhAXv2tfXUpyMbJsHDHX9zfiEb9PERzFWSY9sgLpump
the split accounts for the whole fee stream
expected 10000 | actual 10000
the split does not pay the protocol's collection wallet 8SvEu1bvkhgaSkZW4XHLzfw8djd748KAVHMwvkYGfyr8 at all
expected >= 2500 | actual 0
every SOL burn destination is a burn address: what reaches it is out of circulation
expected a burn destination | actual a burn destination
no inflows are recorded for burn111111111111111111111111111111111111111 yet, so no total is stated for it
claimed burns do not reconcile against the mint supply
expected 956423419572100 | actual 956338419723399
the mint authority is revoked: burned supply cannot be reissued
expected None | actual None
no protocol-attributed burn exists for this mint (D-10) -- PROTOCOL.md sec.4's atomicity requirement is about the protocol's own BURN leg, not third-party burns, so this check does not apply here. It reads not-applicable for every coin until phase 5, because no protocol burns exist yet (D-14) -- the correct answer, not an awkward one
no BURN destination in this split -- the protocol program is not deployed, so a burn pool PDA cannot be derived yet, and this equation has nothing to check
no OPS destination in this split -- nothing to check
What pump was configured to do with this coin's creator fees, read from the chain.
10 checks ran: 4 pass, 2 fail, 4 unchecked. A failed check is not a footnote here -- it is why a figure above is missing.
Three destinations for creator fees. Two of them burn; what they destroy is different, and the third destroys nothing.
| Leg | Action | Permitted claim | Forbidden claim |
|---|---|---|---|
| SOL burn | SOL to a vault no key can spend | "burned", "deflationary", only where SOL_BURN_UNSPENDABLE passes | "burned" when the destination is spendable |
| BURN | SOL buys the token, then an SPL burn | "burned", "permanently destroyed" | none |
| OPS | SOL to a spendable wallet | "funds operations" | "burned" |
Boost burned 43,575,480.427900 tokens across 29 transactions in a 339-second window, at migration -- not by any keeper of ours, and this protocol's own watcher could not see it happen. No keeper of ours has recorded a burn for this coin.
Separately, 1 recorded burn came from somewhere else: 1,100.000000 tokens destroyed directly, by holders burning their own, with no mechanism running and nobody asking. Boost did not do these and neither did we. They are counted anyway, and that is deliberate (D-09): the figure they back asks how much of this token is gone, not how much of it we destroyed. A protocol that counted only its own burns would be flattering itself -- it would report the burns it caused and quietly drop everyone else's. So the walk records every burn against this mint, by anyone, whether or not it ever touched our crank.
+ 19 more -- see the raw observation JSON
no protocol-attributed burn exists for this mint (D-10) -- PROTOCOL.md sec.4's atomicity requirement is about the protocol's own BURN leg, not third-party burns, so this check does not apply here. It reads not-applicable for every coin until phase 5, because no protocol burns exist yet (D-14) -- the correct answer, not an awkward one
No protocol program is deployed, so no address can be derived as a burn pool: no coin has a recognised BURN destination today. What does run is the payout crank. Every hour it finds every coin whose split pays the protocol wallet and asks pump to distribute that coin's creator vault, and pump pays each row of the split; below pump's minimum it waits for the next hour. Those payouts are pump's own transactions, and this page does not record them yet. The one burn event in this coin's history was pump's boost, a single 339-second window at migration, not a recurring mechanism.
The protocol's crank runs every hour for enrolled coins and not for this one: its split does not pay the protocol wallet, so there is nothing of ours to pay out. Not every burn recorded against this mint was pump's boost -- see The Burn for the full breakdown.
View the raw observation JSON (opens the raw observation record) -- the exact record this page was generated from. Recompute it yourself rather than trust it.
This record proves that the page above faithfully renders it. It does not prove that the record itself matches the chain -- that is a different check, and it is the indexer's job, not the page's. See the generator-unverified risk for the reason this page cannot check itself.
Every build overwrites this page and its record in place -- there is no dated series and no "latest" pointer.
Every version this page has ever had is in this repository's git history. The command below shows the diff at which a figure moved between published and withheld:
git log -p web/8FhAXv2tfXUpyMbJsHDHX9zfiEb9PERzFWSY9sgLpump.htmlVerify the boost transaction list yourself in the committed evidence export: https://github.com/needsmorergb/charlie-protocol-v1/tree/main/state/evidence