FAQ

Fast Burn wallet connection guide

Version V0.0.1

Fast Burn lets visitors burn SPL tokens without creating an owner-managed project first. The critical rule is simple: the wallet that holds the token account must open and sign the burn transaction.

Recommended flows

Desktop with Phantom or Solflare extension

  1. Open BEX Fast Burn in your desktop browser.
  2. Search or paste the token mint.
  3. Click Connect wallet.
  4. Select or unlock the browser extension.
  5. Click Check balance.
  6. Enter the burn amount, confirm the irreversible burn warning, and prepare the burn.

This is the most stable desktop flow.

Mobile with Phantom or Solflare

  1. Open BEX Fast Burn in your normal mobile browser.
  2. Search or paste the token mint.
  3. Click Connect wallet.
  4. Use Open in Phantom or Open in Solflare.
  5. Continue inside the wallet browser. The selected token should be carried over.
  6. Connect, check balance, enter the burn amount, confirm the warning, and prepare the burn.

This is the recommended mobile flow. Mobile browsers cannot reliably sign Solana transactions unless the page is opened inside a wallet browser.

Desktop without wallet extension

WalletConnect QR can be used as a desktop fallback, but it depends on the wallet app that scans the QR code.

If scanning the QR opens MetaMask, that is usually not useful for Solana Fast Burn. MetaMask is primarily an EVM wallet and cannot sign the Solana SPL burn transaction required here.

In that case use one of these alternatives:

  1. Install the Phantom or Solflare browser extension on desktop.
  2. Open the Fast Burn page directly inside Phantom or Solflare on mobile.
  3. Use another Solana wallet that supports WalletConnect for Solana transaction signing.

Why can I not choose the app after scanning the QR?

The QR code is handled by your phone and by the wallet apps registered for WalletConnect. The browser page cannot reliably force iOS or Android to show a wallet selection dialog. If your phone opens MetaMask automatically, change the default handler on the phone if possible or use the wallet-browser flow instead.

What communicates with what?

Troubleshooting