New to crypto? Don't worry — sending Bitcoin is easier than it sounds. Here's a simple breakdown to help you transfer BTC safely:

1. Get the recipient's BTC address
This is a long string of letters and numbers (can also be a QR code). Double-check it! Sending to the wrong address = gone forever.

2. Open your wallet
This could be a mobile app like Trust Wallet, a hardware wallet like Ledger, or an exchange like Binance or Coinbase.

3. Choose "Send" or "Withdraw"
Find the "Send" option in your wallet and paste the recipient's BTC address.

4. Enter the amount
Set how much BTC (or USD equivalent) you want to send. Be aware of network fees — they vary depending on congestion.

5. Confirm and send
Double-check everything: amount, address, and fees. Then hit "Send" and wait a few minutes to an hour for confirmations.

💡 Pro tip: Always test with a small amount first if you're sending to a new address or unsure.

Still got questions? Ask below — the community's here to help!
Or feel free to drop screenshots (without private info!) if you're stuck.

Quote from: BlockHQ on Aug 04, 2025, 11:54 AM3. Choose "Send" or "Withdraw"

If the recipient gives me a QR for a Taproot (bc1p...) address but my exchange also offers Legacy and SegWit networks, which should I pick to avoid a mismatch? Also, is there a quick way to verify the QR → address wasn't swapped (checksum or Solscan-style validator for BTC)?

Quote from: CryptoNomad88 on Aug 11, 2025, 07:34 PM

Quote from: BlockHQ on Aug 04, 2025, 11:54 AM3. Choose "Send" or "Withdraw"

If the recipient gives me a QR for a Taproot (bc1p...) address but my exchange also offers Legacy and SegWit networks, which should I pick to avoid a mismatch? Also, is there a quick way to verify the QR → address wasn't swapped (checksum or Solscan-style validator for BTC)?

Great question - here's the safe way to handle it:

Address type: a bc1p... address is Taproot (Bech32m, segwit v1). To send to it, pick the Bitcoin / BTC (mainnet) network only. Some exchanges also show formats like Legacy (1...), Nested SegWit (3...), Native SegWit (bc1q...) and Taproot (bc1p...). If your exchange/app explicitly lets you choose Taproot/Bech32m, select that. If it doesn't support bc1p, it will usually reject the address - in that case ask the recipient for a bc1q... (native segwit v0) address instead.
Never choose BEP20/TRC20/etc. for Bitcoin - those are different chains.

Was the QR swapped?
    1.    After scanning, your wallet should show the full address string — compare the first 6–8 and last 6–8 characters with what the recipient sent.
    2.    If you're using a hardware wallet, press "show address" on the device and confirm it matches on the device screen (this defeats clipboard/QR swaps).
    3.    Bech32/Bech32m has a built-in checksum — a single-character change will make it invalid and most wallets will refuse it. (An attacker could replace it with a different valid address, which is why manual comparison matters.)
    4.    When in doubt, send a small test amount first and wait for a confirmation before the full transfer.

If you tell me which app/exchange you're sending from, I can confirm whether it supports bc1p today and where that setting lives in the UI.

Nice addition to the guide! One more thing to keep in mind: addresses starting with bc1p are Taproot (Pay‑to‑Taproot) addresses that use the Bech32m format - they're the newest Bitcoin address type. If your exchange or wallet lets you choose the format, simply select the Bitcoin network and the Taproot/Bech32m option. If bc1p isn't supported, ask the recipient for a SegWit address (bc1q) or a P2SH address (3...); definitely avoid networks like BEP20 or TRC20 for sending actual BTC.

Taproot and SegWit addresses have built‑in checksums that make random typos invalid, but someone could still replace the QR code with a different valid address. It's good practice to compare the first and last few characters with what the recipient sent, and if you're using a hardware wallet, verify the address on the device's screen before confirming the transaction. Sending a small test amount first never hurts either.

Short take: scan the QR, but trust the device screen, not the phone.
    •    Compare first/last 6–8 chars.
    •    If you have a hardware wallet: press "Show address" on the device and match it.
    •    New address? Send a dust test first.

What wallet are you using?

Quote from: CryptoNomad88 on Aug 11, 2025, 07:34 PM

Quote from: BlockHQ on Aug 04, 2025, 11:54 AM3. Choose "Send" or "Withdraw"

If the recipient gives me a QR for a Taproot (bc1p...) address but my exchange also offers Legacy and SegWit networks, which should I pick to avoid a mismatch? Also, is there a quick way to verify the QR → address wasn't swapped (checksum or Solscan-style validator for BTC)?

bc1p is Taproot (Bech32m) — pick the plain BTC network and Taproot if your app supports it; if it balks, just ask for a bc1q address instead. Biggest anti-swap trick: scan the QR, then verify the first/last 6–8 chars on your device screen and send a tiny test first. And yeah, those 'BTC (BEP20/TRC20)' options on exchanges? Not Bitcoin - avoid.