Jul 18, 2026

This supposed consensus bug in BIP110 is a case where someone activates the fork after the fork is active, after validating blocks under the previous rules. So the user is changing the rules out from under the store. That's not a consensus bug. The node will sync just fine from genesis and all who do so will end always up on the same chain. Changing rules that affect already-validated blocks is user error and affects only that user, it a way unique to that user's situation. While segwit added a guard for this, other soft forks and hard forks have not done so. x.com/DathonPwn/status/2078514978773192779