@Arthur_van_Pelt maybe they’re trying to fix BSV by turning it off and back on again
@Tak_Horigoshi @Arthur_van_Pelt Known issues in Bitcoin’s white paper: https://t.co/JoqeF0bQMU
@LukeDashjr @peterktodd This is why I argue that “hard fork” and “soft fork” are insufficiently descriptive. By you… https://t.co/1ajcMFdkVu
@johndoeisback @peterktodd You’re probably thinking about the BDB lock limit issue. I cover that here: https://t.co/DLnvBYtfqy
@peterktodd Interestingly enough it looks like the first practical hard fork may have been triggered by @LukeDashjr… https://t.co/2ZtNIBlsCH
@peterktodd Published! I actually changed my mind regarding OP_CLTV because blockchain analysis shows OP_NOPs being… https://t.co/yvhM6SR7iq
@peterktodd TL;DR the first use of an OP_NOP triggered a hard fork for pre-v0.3.6 clients that had no concept of OP… https://t.co/0LPtLROmzY
RT @TyCardon: Domestic wealth migration data from the IRS for 2020.
Top gainers: FL ($23.7B), TX ($6.3B), AZ ($4.8B), NC ($3.8B), SC ($3.6…
@ercwl Don’t forget “Dr” Roy Murphy who is now a full-on BSV proponent.
@ssfaserr @peterktodd The condition was triggered on December 8, 2015
After extensive research I have come to believe that @peterktodd triggered a hard fork of the Bitcoin protocol by i… https://t.co/so3lw2t5cW