Burn on Solana
A wallet-signed burn permanently removes the selected supported token from Solana circulation.
Burn supported Solana tokens and receive their corresponding native Bitcoin Runes.

Proof-of-destruction flow
This is not a wrapped-token bridge. The Solana asset is destroyed and the Bitcoin-native Rune is released from reserve inventory.
A wallet-signed burn permanently removes the selected supported token from Solana circulation.
The backend watches the Solana transaction and marks the migration ready only after confirmation.
The matching native Bitcoin Rune is released from a monitored Bitcoin reserve to your bc1p address.
Solana side
Token burn
Supply decreases permanently after wallet confirmation.
Bitcoin side
Native Rune release
Reserve inventory sends the corresponding Rune to a Taproot address.
Supported assets
EMBER
Embr7h...K4mAEMBER•RESERVE•RUNE842119:74SATCAT
SatC4t...U2sVSATELLITE•CAT839550:18ORBIT
Orb1tT...zKbNORBIT•SIGNAL•NINE833214:9FLINT
FLnt3J...TqR6FLINT•GENESIS840002:41JEV tech — under the hood
This isn't a static demo. The app runs on a production-grade full-stack foundation with real server endpoints, real blockchain libraries, and encrypted key storage — Burns run live on Solana mainnet, and reserve releases on Bitcoin and Zcash are handled by the backend reserve operator.
React 19 with a full-stack framework — every page is server-rendered and production-ready, not a throwaway prototype.
Token registry, balances, burns, and history run through live API endpoints on the backend today.
Solana's official web3 SDK is wired in, ready to read real balances and verify burns the moment live RPC connects.
RPC credentials and wallet keys are held in an encrypted secret store on the backend — never in the browser or the codebase.