The Bitcoin network is under attack, and block production has slowed significantly. The community is preparing mitigations to resolve the situation. In the meantime, attackers are spreading misinformation and advising users to downgrade or switch to insecure node software.

On Saturday, a troll made a false "consensus failure" report about Bitcoin Knots. To put it simply: if Core corrupts your data, Knots sometimes can't detect the corruption. Since Core is late updating to BIP110, it can in some case corrupt the database after activation.

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. @BitcoinKnots _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.