Check this yourself
A sceptic's checklist against ourselves. Every line names where to look; nothing here asks you to take our word. The receipt verifier runs in your browser and asks the chain and the original data source directly.
Where money can go · Who can do what · What is locked · What is not done yet · Is the deployed code this code? · Verify a receipt in your browser
Loading
Reading the data. Nothing is shown until it answers.
How a burn is computed
A share of the spendable burn pool buys the coin and every token bought is burned. It is not a fixed share of the token supply. Hypothetical inputs; the first values are the real 2026-10-06 devnet receipt. Holders' balances are never touched: only tokens the program bought are burned.
- Qualifying units: 23 (each full $1B; the remainder carries only while the debt keeps rising).
- Available budget: 0.5056 SOL.
- Planned spend: 0.1043 SOL = budget × (1 − (1 − 1%)^23). Compounding: 23 units × 1% would be 0.1163 SOL; each unit spends its share of what the previous one left.
- Actual purchase: 0.0201 SOL — one crank spends at most 2% of the trading pool's SOL reserve (0.0201 SOL); 0.0842 SOL carries to the next crank.
- Actual burn: every token the purchase received. The number of tokens depends on the trading pool's reserves at the moment of the crank; enter a hypothetical token reserve to estimate it.
The verifier refuses a transaction for a mint the burn_receipts program does not know. To ask about a mint itself — is it a Burnticker coin at all — use Verify a mint; lookalikes are listed on Not Burnticker.
JSON: /api/burnticker/v1/check · /api/burnticker/v1/check/receipts · /api/burnticker/v1/check/receipts/<signature> · doc: docs/burnticker/CHECK-THIS-YOURSELF.md