Fair, mempool.space does show that a tx was replaced and links to the new one. My point was more about support teams. Many of them check the txid in their own node or deposit system, not on a public explorer, and there the old one simply doesn't exist. Sending the new txid from the start saves a round of "we can't find your transaction".

Thanks a lot for the reminder Pooya87... there's been times the habit of double checking my transactions before they are being initiated have saved me loosing some funds. No matter the situation, even if it's an address in your beneficiary list you have to recheck before initiating a transaction. Laziness shouldn't make you lose your money to attackers who could've changed the address if your device was hacked .

A lot of people have been victims to this lackadaisical behaviour of not double checking or even triple checking their crypto transactions and in the process lost some funds. It's even worse when you missed an alphabet or number or getting them mixed up probably due to typo errors. Let's be careful out there a d remember that it doesn't cost you anything to be security conscious.

Not to go off-topic, but would you please recommend one?  As I said on page 1 of the present thread:

https://bt.irlbtc.com/view/5597827.msg67279449#nullius_needs_a_new_wallet

I sometimes used to use a BIP 157/158 wallet many years ago—but they turned evil, or perhaps were evil all along... you know which one.  If you don’t, check my two most recent sent red tags.


This is why.  Especially if the wallet has proper handling of Tor circuit isolation via SOCKS5 username/password, and sends tx via a one-off connection to a P2P network peer on an isolated Tor circuit.  The latter is better than an originating full node’s broadcast privacy, even with the Poisson timer trick that Core uses to make it moderately more difficult to trace the transaction’s origin!


People who watch Youtube videos in HD and 4K will complain about this.  (Compare djb’s remarks about Classic McEliece’s BIG PUBLIC KEYS.)  People who browse the Web of bloated 12 MB webpages loaded with CPU-sucking JS tracker-ads and (other) malware will complain about this.

The bandwidth and CPU loads of compact block filters are not insignificant, but they’re much lower than a full node’s—and the disk requirement is so small.

---

Thank you for the information about what Electrum calls itself.  I stand corrected.

That said, I think that terminology needs to be precise.  What is the unambiguous term for what I’m calling “SPV”?  The unambiguous term for the Electrum Protocol is “Electrum Protocol”.


Thanks.  You also make some good points in your comments, and it’s nice to discuss and debate these technical issues with mutual respect.


Or I could always write my own wallet, LOL.

Having your own node is a plus point but I agree majority don't want to run a node due to many reasons, out of those one reason is the space that's needed to download the whole blockchain. Many people are still happy with 256 GB SSD or 512 GB SSD and such people can't run their own nodes that's why they have to use others nodes for the transactions.

I agree, the better approach is to check transactions and destination addresses multiple times before broadcasting them, as that's something everyone can do. Also to be on safe end one should always update Electrum or any other open source wallet to its latest version.

As with checking the address of the recipient. It's vital to check the change output. Several outputs can be included in a transaction. And users should check the destination of each of their funds prior to signing the transaction. This incident also illustrates the need to have wallet software. Rather than purely relying on users to identify suspicious transactions.

Wasabi Wallet. I have not come across any other as good, and this one comes with the best and most liquid coinjoin implementation, so you can gain on-chain privacy as well.

This is just a reminder that this is real money, and your life is tied to it. This is more important than a mere inconvenience in the browser. Money privacy is not a "nice to have" but a necessity.

Thanks for the clarification.  You’ve got rep.  I will look into it.

I still want a lightweight BIP 157/158 (compact block filter) wallet with TUI, written in C or alternatively, Rust.  (Language makes a real difference, because I like to customize things in private branches; both my Tor daemon (C) and my Zcash wallet (Rust) actually run with some little local patches.)  The only thing I liked about Wasabi was its implementations of receiving (compact block filters) and sending (one-off connection to peer on isolated Tor circuit).  I only used its CoinJoin a few times, to test it; I don’t need any CJ.  I strongly disliked its GUI (which didn’t even use OS widgets as of v1), and it was heavy and slow.  But the privacy of simply receiving and sending bitcoins was excellent for a light wallet!


(Apologies to pooya87.  I do intend to make my own thread about my wallet needs.  The very long rant about wallets will go there!)