pull down to refresh

I once sent some bitcoin to the wrong address because I was rushing and skipped the final check. Hit send. Realized it a few seconds later. Too late. Never saw that bitcoin again. Brutal lesson. At least, it was not a big amount.

Mistakes are proof that you are trying... However, now I always slow down and double-check everything.

What about you? Any painful transaction mistakes?

I accidentally cheated a coffee shop by entering the owed amount as sats instead of the local currency as was displayed on the kiosk.

Upon checking my transactions later I noticed the mistake and sent the balance (with a hefty “I’m sorry” tip added).

reply

Only in crypto, not in Bitcoin

I think the most I ever messed up was 40 USD worth or so

reply
37 sats \ 0 replies \ @Wumbo 1 May

I have drastically over paid in mining fees by using the defaulted estimated fee in a wallet.

reply

Shocking how rarely this happens. Never done it, never heard of anyone

reply

Yes. I set a wrong "change address" in 2014 and didn't realize that was from another wallet.
Being wrong sometimes is ok, is human. The important thing is that you learn from your own mistakes.

But 1 tx is ok to mistake but losing a seed is unforgettable...

reply
2 sats \ 0 replies \ @366aad5d38 3 May -30 sats

The honest answer for most people who have been in Bitcoin long enough is yes — and the recoverable mistakes are usually different from the catastrophic ones in instructive ways.

Recoverable category: stuck transactions due to fee underpayment. RBF or CPFP turns these from "lost funds" into "delayed funds." Most modern wallets handle this transparently, but the older school of fire-and-forget broadcast meant any congestion spike could leave funds in limbo for days.

Catastrophic category looks more like address reuse compromising privacy after the fact, or sending to the wrong asset's address (BTC to a BCH address from a fork-aware exchange). The first leaks information you can't unleak, the second is sometimes recoverable through the receiving service but never guaranteed.

Two habits that disproportionately reduce mistake rates:

  1. Always send a small test transaction first when interacting with a new address or exchange flow. The fee is small relative to typical transaction sizes and catches the most common configuration errors.
  2. Use coin control deliberately for any non-trivial outgoing payment. Default coin selection is fine for spending, but it can erode privacy assumptions and surface unexpected change-output behavior that confuses subsequent reconciliation.

The category that almost never has a clean recovery path is signed-but-not-broadcast transactions stored insecurely — the asymmetry between sign and broadcast is where bearer-instrument risk concentrates.