Step-by-step
- Unlock and open Receive. Pick Bitcoin. Copy the address. Optionally show the QR to someone in the same room — not to a screenshot group chat full of strangers.
- Tell the sender “Bitcoin mainnet, bc1”. If their exchange only sends to 1…, they must use a SegWit-capable withdrawal or another sender. Do not type a fake 1… from this seed on a website.
- Wait for confirmations in History. Explorer: mempool.space. Keep some BTC for the next Send fee. No BTC swap/bridge in Exchange.
Why this wallet uses bech32
Native SegWit is what modern invoices expect and what our HD path produces. Legacy vs SegWit is compared in Bitcoin SegWit vs legacy. The sample address in the detector is the BIP-173 example — not a donation address.
| Sender asks for | You should |
|---|---|
| bc1 Bitcoin | Share GaurdWallet Receive |
| Lightning invoice | Not supported here |
| USDT TRC-20 | Wrong asset — use TRON Receive |
| BTC on BNB Chain (wrapped) | Different token; not this Bitcoin adapter |
Receive copy: send only that symbol on that network. Other assets to a Bitcoin address are lost. We cannot recover them.
After the payment
Dashboard fiat values need the price feed; if it is down, balances still exist on-chain. RPC for Bitcoin is Esplora-compatible (mempool.space). Sending later uses sat/vB tiers.
Receive → Bitcoin → bc1q… (BIP-84)
History → mempool.space
Exchange → no BTCTest with a small amount first when the sender is an exchange. Their “BTC” picker has been wrong before.
FAQ
Is the BIP-173 example my deposit address? No. It is a public test vector for the detector. Always copy Receive from your unlocked wallet.
Can I receive wrapped BTC on Ethereum at this bc1? No. Wrapped BTC is an ERC-20. Use an EVM Receive address and the correct contract.
How many confirmations? Exchanges set their own. We show pending vs confirmed from the adapter. We do not credit unconfirmed BTC as spendable beyond what the chain adapter reports.