solanaburner*

Your wallet, and the data around it.

Wallet access

Connecting a wallet shares its public address with SolanaBurner. Signing takes place in your wallet. SolanaBurner does not request a seed phrase or private key and does not hold your tokens.

RPC requests and hosting

Your wallet address, token accounts, transaction bytes and transaction signatures are sent through SolanaBurner’s server to Helius to read balances, estimate fees, simulate, submit and verify transactions. The provider and Vercel hosting infrastructure can process request metadata, including IP addresses and operational logs. This site does not make a retention promise on their behalf.

SolanaBurner currently uses no advertising analytics or application user database. Rate limiting uses IP-related request metadata. The RPC API key stays on the server.

Browser storage

Your browser stores pending transaction signatures, the selected network and the associated public wallet address so SolanaBurner can check an uncertain submission after reconnecting. This record is removed when you start another burn, or you can clear this website’s local storage.

Public receipts

A finalized transaction is public blockchain data. A receipt exposes the wallet, token mint, amount, network, timestamp and transaction link. Sharing opens X’s compose page; SolanaBurner does not post automatically. Downloading an image does not publish it.