The new draft of the BIP has been posted to the bitcoindev mailing list:
https://groups.google.com/g/bitcoindev/c/nOZim6FbuF8/m/d4tkNi0DAQAJ
The code has been published here:
I'm looking forward to hearing your feedback.
The new draft of the BIP has been posted to the bitcoindev mailing list:
https://groups.google.com/g/bitcoindev/c/nOZim6FbuF8/m/d4tkNi0DAQAJ
The code has been published here:
I'm looking forward to hearing your feedback.
Thank you !
I believe there is no compelling reason to remove the 'Reactive' softfork deployment method on the pretense of building consensus. Quite the opposite, the existence of the 'Reactive' option acts as an additional lever, actually leading to greater consensus.
I think the same. Stop making compromises with clearly bad actors.
Perhaps he compromise is not as much for the bad actors as it is for more of the middle?
I dunno...
Excellent.
Thanks nostr:nprofile1qqsw3p5pela795rxxff34kgfafsaawhnkqp8ehmgm2my49dgx9fjclcprpmhxue69uhhyetvv9ujuempwd6x2ct6dyhxuet5qyt8wumn8ghj7ct5d3shxtnwdaehgu3wd3skueq9npjah 🫡
I still think the reactive method shouldn’t be removed from the BIP. It’s a fallback if plan A fails, and I get the sense it’s the one that unsettles the bad actors the most.

