Check what you’re approving.

SolanaBurner’s transaction rules are narrow and inspectable. Here is the source, the evidence, and a way to decode the exact bytes before signing.

Audit status: not independently audited. Automated checks and devnet transactions provide evidence of tested behavior. They do not guarantee that software, hosting, dependencies, RPC providers, or wallets cannot fail or be compromised.

Only three instruction types

Instruction	What it may do
BurnChecked	Destroy the selected amount, for one token mint, from your token accounts.
CloseAccount · optional	Close eligible empty accounts after a full burn and return their entire rent deposit to your wallet.
System transfer	Pay exactly 20,000 lamports (0.00002 SOL) to the fee address below, once.

The prepared transaction contains no delegate approval, authority change, token transfer, wallet-account closure, or custom on-chain program call. Your wallet remains the sole signer and network-fee payer.

Fee recipient: Htj8rb2dH75AsBawvhQPCDtXBwL3FpAX5bS7SYWkaLEr
SPL Token program: TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA
Token-2022 program: TokenzQdBNbLqP5VEhdkAS6EPFLC1PHnBqCXEpPxuEb
System program: 11111111111111111111111111111111

Checks before you sign

The server refreshes balances, validates account eligibility and closure authority, estimates fees, and simulates. The browser independently reconstructs the transaction from your selection and compares the complete message bytes. This checks the chosen mint, amount, decimals, accounts, closure option and fixed fee before the wallet request. After signing, the message bytes must still match.

You can expand Verify this transaction in the review screen to copy the unsigned bytes. Always compare the wallet’s displayed actions and network with your intended burn. Decline any unexpected approval or transfer.

A timeout never automatically triggers another submission. SolanaBurner tracks the known signature so you can check whether the transaction landed.

Inspect a transaction without connecting a wallet

Copy the unsigned transaction from SolanaBurner’s review screen and paste it here. Decoding runs locally in your browser. This tool cannot submit or sign anything.

Base64 transaction

An allowlist match does not prove your intended amount, valid signature, ownership, network, account state, or future execution. Compare the decoded details, use your wallet’s simulation, and independently inspect the source. A compromised website could also change this checker.

Inspect the source and repeat the checks

Release manifest and SHA-256 hashes · Transaction-related source snapshot · Standalone receipt verifier · Devnet evidence JSON

The source snapshot includes the transaction builder, browser burn flow, guards, receipt verification, wallet integration, tests, and dependency lockfile. The manifest identifies their exact bytes. Download the immutable hash-named snapshot linked in the manifest for comparisons between releases.

Hashes show whether two artifacts are identical. Because these files are published by the same operator as the website, they are not an independent attestation that the served application matches the source. Review and run the checks locally, obtain transaction data from an RPC provider you trust, and inspect the actual wallet request.

Independent verification instructions for humans and agents

Executed devnet evidence

These seven burns used test tokens in a faucet-funded temporary wallet. They cover partial burns, full burns with and without closure, both token programs, multiple accounts, exact decimals, and a transfer-fee token. They are developer-run tests, not an external audit or evidence of a mainnet burn.

What you still rely on

You rely on the browser and downloaded code, wallet, Solana network, token programs, and the RPC data used for simulation and receipts. Solana programs and website releases can change. A successful simulation cannot promise future execution. Burns are irreversible, and failed transactions can still charge a network fee.

SolanaBurner never needs a seed phrase or private key. Wallet addresses and transaction signatures are public blockchain data. Read the data handling details.