Re "new bugs", note that I mean newly discovered.
At least one of these dates back to 2013 (v0.8.0).

An update on this thread, for full clarity: There are now a total of 8 new bugs which can cause wallet deletion or corruption.

My initial comment applies only to the initial, severe bug that affects people simply using Core30 normally.

@nprofile1q... _is_, however, impacted by 6 of the others, which are not triggered by normal end users:

3 of these are "power user" functionality (moving wallet files around manually; creating unexpected files in the wallet directory; or using the `bitcoin-wallet` command line tool)

1 of them requires a low-level disk/filesystem/OS problem during shutdown.

The remaining 2 are unrealistic to trigger at all, but hypothetically possible if you start the node software again immediately before it finishes shutting down (within milliseconds), or ... have multiple wallets in the same directory, one of which has recent changes, the node crashes or has a power failure, you start the node again and NOT open the recently-modified wallet, open the other wallet, and shutdown cleanly.

All six of these issues will be fixed in a new version of Knots soon.

@nevent1qqs...

FYI, @nprofile1q... is NOT impacted by the Core30 wallet deletion bug.

https://x.com/LukeDashjr/status/2008326237962277039?s=20

Internet Relay Chat (1980s protocol) for open source development, including Bitcoin from the earliest days (Satoshi's Bitcoin client even used it to find peer IPs!)

You're the one lying

No, you're wrong. You're acting as if miners have a choice. They don't. They must make blocks that the network accepts, or they're not miners anymore. If they make invalid blocks, *they* are splitting the chain - not the softfork.

Furthermore, their invalid blocks don't constitute a real chain: every time the valid chain gets ahead, all the old nodes will drop the invalid blocks and those miners will start over, with huge losses. The only way they can avoid this, is with a counter-fork.

You're the liar. I said nothing of the sort. And no, softforks _don't_ cause chain splits.

No, that's a question for Sparrow

Liar

Even if we survive this attack by Core30, this situation where I personally have to save Bitcoin every few years needs to stop. Bitcoin cannot survive if it's dependent on one man. Others need to step up more.

https://x.com/LukeDashjr/status/1975942110047252776

The exploit works because Core neglected to update the spam filters a few years ago, and refuses to fix the vulnerability.

And no, you're wrong. Satoshi's spam filters were VERY picky about what was inside transactions. Anything that he didn't foresee being used was rejected.

Core30's malicious changes have nothing whatsoever to do with Taproot.

Each user decides for himself. Collectively, our nodes form consensus around what is spam and what maybe isn't.

F2Pool is actively attacking the network RIGHT NOW. All it takes is one attacker to send them a single instance of CSAM, and Bitcoin users will have to knowingly and intentionally receive, store, and distribute it until the end of time. This will permanently impact Bitcoin adoption regardless of whether governments turn a blind eye or prosecute. If miners are going to switch pools when they do bad things, NOW IS THE TIME.

I don't care if you switch to Foundry or even Antpool. Obviously I would prefer you make your own blocks and use OCEAN, but this is too critical and time-sensitive to be picky. We can work on mining decentralization and spam issues over a longer period of time, but CSAM is an insta-kill we MUST avoid.