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.
This is not a surprise nor a bug in Knots, much less a serious issue.
Core also won't detect it; nor have most previous softforks guarded against it (eg, Taproot did not).
The simple answer is: don't run software that corrupts your data.
The deficiency in Core that can cause this corruption is only a risk starting in August.
Upgrade to the latest Knots 29.3.knots20260508 before then.
On Sunday, another fake "bug" was claimed by Murch.
It's a complete fabrication. There is nothing to do.
In both cases, there was zero disclosure to the project at all (much less responsible disclosure) - this is clearly a bad faith FUD campaign and will probably continue.
If any real concerns were to surface, @Bitcoin Knots would post an announcement.
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.
This is not a surprise nor a bug in Knots, much less a serious issue.
Core also won't detect it; nor have most previous softforks guarded against it (eg, Taproot did not).
The simple answer is: don't run software that corrupts your data.
The deficiency in Core that can cause this corruption is only a risk starting in August.
Upgrade to the latest Knots 29.3.knots20260508 before then.
On Sunday, another fake "bug" was claimed by Murch.
It's a complete fabrication. There is nothing to do.
In both cases, there was zero disclosure to the project at all (much less responsible disclosure) - this is clearly a bad faith FUD campaign and will probably continue.
If any real concerns were to surface, @Bitcoin Knots would post an announcement.
912❤️38🤙5❤️2🧡2👍1💪1
