I explained my reasons to you on multiple occasions - https://bitcointalk.org/index.php?topic=5271997.msg55093424#msg55093424

Still, not that it matters now - I'll drop off the DT selection algorithm soon enough.

I completely understand that position. But after many years here and several users I would consider friends, I felt I owed the community a basic explanation at least. And not to mention that this account would be highly valuable if sold, could be used to scam, could take out large no-collateral loans, and so on. Better to remove all doubt.

---

Thanks to the users who reported the trash and the mods who cleaned this thread up. I think it's probably run its course now. I've got a few more PMs to send over the coming days, but this will be my last post. Farewell everyone.

I sincerely appreciate the gesture - truly I do - but I've always been quite uncomfortable with some of the (for lack of a better term) "hero worship" that myself and some other established/knowledgeable users receive on this forum. I'm just a normal person. Quiet remembrance will be just fine.

I have been dipping in and out over the last couple of days reading all the messages and PMs. Even if I don't reply directly, I have read your message and I thank you for it. Although to the multiple people who have tried to convert me to their religion, I'll paraphrase some random Irishman (and not Voltaire) when I say "Now is not the time to be making enemies".

I've known this day would probably come for the best part of 10 years. Obviously I hoped it wouldn't come for another 10 years, but I came to terms with it a long time ago. It's probably why I've been so vocal in telling people to make sure their loved ones know about their back ups, and to not rely on their memory alone for anything important.

I couldn't ask to leave behind a better legacy.

Have a cookie for me sometime.

For everyone defending me above - it is only natural that after years on the forum that I would have pissed off at least a few people. I have both those users on ignore though, and as I said somewhere before, I'm not going to lose a second of sleep over what either of them think of me. For what it's worth, I stand by everything I've said about BSV and Wasabi over the years, and if part of my legacy is continuing to piss off a couple of scammers from beyond the grave, then that's even better.

And you can all stop sending me merit - Loyce and fillippone are going to have to cycle even harder to catch up now!

Thank you everyone for all the kind comments. It is pleasing to know that so many people learned things from my ramblings.

You flatter me. Although as I've said before, my coding skills are very average and nowhere near the level needed to be a dev.

Heh. My wife might have a comment or two to make about that...

If I was disappearing for privacy reasons, I hope I'd come up with a much more glamorous story. Or you know, just actually disappear without a trace like Satoshi did.

Look on the bright side: Less competition for the top merit spot!

Without giving away too much personal info, I have a chronic disease. I've had this disease for a decade and have had a lot of treatment for it, but it is winning. I likely only have a few months left. And so, I bid you all farewell. I'll be spending as much of my remaining time as possible with my family. In a week or so, once this thread has run its course, I'll ask theymos to lock this account.

I have learnt a lot from many of you, and I hope many of you have learnt something from me. Although we will never meet, I would have loved to share a beer with many of you, and I hope you'll remember me fondly.

Leo

Been patched in the most recent version of Electrum:

Sparrow uses Java's SecureRandom function to generate its entropy, which sources entropy from /dev/urandom: https://github.com/sparrowwallet/sparrow/blob/02a0a3277bdc4469d7369cb1915a1f47c05e05d1/src/main/java/com/sparrowwallet/sparrow/control/MnemonicKeystoreEntryPane.java#L57-L71

This is the right answer. You want to Sparrow to create a keystore at m/49'/0'/0', using the default account. It will then generate addresses starting at m/49'/0'/0'/0/0, meaning the address you see in Ledger Live at the derivation path you gave will be the 12th address in the wallet.

Have you checked that your Tor daemon is running properly? You can use the -debug=tor argument to log additional info regarding your Tor set up.

Any new antivirus or firewall software or updates which could be blocking ports, etc?

Does it actually make any noticeable difference to the overall percentage though? I suspect what is happening is that when you restart you are simply interrupting the sampling process, and so when you restart Core thinks it is running faster than it is.

That is the standard page Blockchair shows if you navigate directly to the URL of an invalid/non-existent transaction (as opposed to searching for it via their search bar first). For example: https://blockchair.com/bitcoin/transaction/0123456789abcdef

As we develop more and more script types, each with their own default derivation path, then not having a versioning system is becoming more and more problematic. It's why wallets such as Electrum have implemented a feature to scan all the commonly used script/path pairs for BIP39 seed phrases, because many users do not know where exactly their coins are stored and many wallets do their own thing such as derive P2WPKH addresses at m/44'/0'/0', use m/0' instead, and so on.

I don't think so. OP's proposal as it stands is 100% backwards compatible. If I generate a new 15 word seed phrase with the 32 bit versioning system, old software will still see the entire seed phrase as a valid BIP39 seed phrase and will recover the exact same wallets (provided of course I know my script type/derivation path, since old wallets won't be able to interpret the 32 extra bits). Any legacy seed phrases will still be recoverable by new software, provided there is a simple check box to indicate it is a legacy seed phrase so the software does not try to interpret the first 32 bits of entropy as versioning data.

Perhaps you could even stipulate that the new seed phrases must be either 15, 21, or 27 words long, and so any seed phrase which is 12, 18, or 24 words is immediately known to be a legacy seed phrase.

I agree it is confusing, but in my post above the word "consensus" is referring to the consensus rules as hosseinimr93 has explained, and not to a "general agreement" between all node runners. RBF rules are a local policy, and even if 100% of nodes enforce the same RBF policy, a block containing a valid transaction which breaks that policy (such as a replacement transaction which evicts >100 other transactions) will still be valid and will still be accepted by all these nodes because it does not break the consensus rules.

You might be interested in reading this page: https://en.bitcoin.it/wiki/Consensus

This was actually the original use of the nSequence field in transactions. Any unconfirmed transaction which had an input with an nSequence of less than 0xFFFFFFFF was not yet considered finalized and could be replaced by a conflicting transaction with a higher nSequence value. And so the upper limit was effectively 4,294,967,295 (0xFFFFFFFF in decimal).

Interesting proposal! A few questions:

How would you propose assigning your 8 bit field version field? Something like this?

00000000 - P2PKH at m/44'/0'/0'
00000001 - P2SH-P2WPKH at m/49'/0'/0'
00000010 - P2WPKH at m/84'/0'/0'
00000011 - P2TR at m/86'/0'/0'

What if I want to use a script type/derivation path combo which isn't assigned a version number? What happens then? And what if I want to use the same seed phrase to generate both a P2PKH wallet and a P2WPKH wallet, for example?

Taking 128 bits of entropy generating a 15 word seed phrase using your new system, I assume you are feeding the full 15 words in to PBKDF2? Or are you stripping out the 128 bits of entropy and converting to a "legacy" 12 word seed phrase before generating your wallet?

I disagree with your suggestion above to indicate whether a passphrase has been used in the general purpose field. One of the main uses of a passphrase is to add plausible deniability, which is eliminated if you indicate in your seed phrase that you have used a passphrase.

I don't use Windows, but it sounds like you've deleted some or all of the Electrum files without actually uninstalling it. The other possibility is an antivirus program has quarantined some of the files. Try navigating to C:\Program Files (x86)\Electrum and see what is there.

Coinomi is critically insecure and users have previously lost all their coins because Coinomi sends seed phrases in plain text via the internet to Google servers. And as pointed out by others above, Coinomi is closed source trash and slowly dying.

Use this as a wake up call to stop using Coinomi and move to a better wallet. Choose a good monero wallet from the sidebar here: https://www.reddit.com/r/Monero/. Create a new wallet and then send your funds from your defunct Coinomi wallet to your fresh wallet.

Chrome is an awful browser for many reasons, and resource usage is one of them.

In Bitcoin Core, go to Settings -> Options and check the size of the database cache you have set. Increase this if you want Core to use more RAM (you'll need to restart Core after you change this setting).

I've had Kruw on ignore for a long time so I've not been keeping up with his latest copy and paste nonsense.

In terms of whatever Peter Todd thinks of Wasabi, I tend not to care what one person's opinion is, regardless of who that person is. Gavin Andresen was a reputable contributor to bitcoin, and people blindly listening to his opinion has caused untold damage in this space. The opinion of one person is irrelevant, especially when that opinion can be bought. I care about the facts. And the facts of the matter are that Wasabi directly funds the enemies of privacy, and that Wasabi coinjoins are deeply flawed: https://bitcointalk.org/index.php?topic=5476210.msg63334000#msg63334000.

The receiver sees the transaction, which will clearly contain all three addresses listed as inputs. How his particular wallet software displays that transaction may vary, but all three addresses will be part of the transaction.

Either import all three address types (and their relevant private keys) in to the same wallet, or move a partially signed transaction between three different wallets, each containing one address.

You could if you wanted, but there is no need to do this.

Here's a recent transaction from a couple of blocks ago which contains P2PKH, P2SH, and P2WPKH inputs altogether in the same transaction: https://mempool.space/tx/d556106e99a030496a7c959c29f45f5f514407e6fa2dd58ccff8548d07309f0f

And it's a great acquisition for a blockchain analysis company. Simultaneously remove a large cost of running Wasabi since they can obviously supply their mass surveillance tools to themselves for free, while also gaining more information about every output which is even attempted to be coinjoined through Wasabi (even if they ultimately censor it), giving them more information to further their blockchain analysis capabilities. Plus it further opens up the possibility of self Sybil attacks (as OP has linked to) to further deanonymize Wasabi users. (On another note, some of the Twitter links OP has provided are now dead, but can be found on The Wayback Machine.)

The writing has been on the wall for Wasabi since the day they announced they will start cooperating with and directly funding blockchain analysis. Anyone who has chosen to support them from that day onward has no excuse.

I've been poking around the Dread forum after seeing the links shared by OP; the distrust of Wasabi there is pretty widespread (for good reason), and I would think people regularly using Tor and Darknet Markets know a thing or two about privacy. The most privacy orientated people on this forum do not recommend Wasabi. The most privacy orientated people on Twitter do not recommend Wasabi. It would seem the people who do recommend Wasabi largely either work for Wasabi or are being paid by Wasabi. It's pretty telling.