Dathon Pwn
@DathonPwn
If the database doesn’t work, bitcoin can’t be money.
1 Following 228 Followers
@start9labs @dathon_ohm @LukeDashjr Your own documentation calls it a "validation gap".
The entire point of running your own node is to not have gaps in consensus validation. To have gaps is a consensus bug. Full stop.
Just because you can fix it by running terminal commands, does not change that definition.
Show more
@murchandamus @dathon_ohm @JimAndrews77 This is correct.
This is not a "consensus bug" in the same way Block Slop is, but this is a failure to honestly document all of the consensus changes that are included in BIP 110.
FYI to @FoundryServices - BIP 110 has not documented all the consensus changes it makes.
Show more
@rodarmor Once a non 110 block gets mined, the 110 client will cause consensus bugs if you switch chains.
This is a confirmed consensus bug I disclosed yesterday.
He would ignore us if he could. He can’t because this matters.
He would engage if he could. He is scared so he blocks.
He is would tell the truth if he could. He can’t so he lies.
He vibe coded a consensus bug in the BIP 110 client
CC @dathon_ohm @cguida6 @LukeDashjr
Show more
@GrassFedBitcoin This issue was already addressed properly in SegWit, as detailed in my report.
Why do you believe the safeguards that were included in SegWit are not necessary for BIP 110?
@saylor Hello @saylor.
I have disclosed a consensus bug in BIP 110 this morning here, this could result in multiple chain splits, and money lost across miners, exchanges, and merchants.
Show more
