Jan 24 - Jan 24, 2017
The proposal supports 8 opt-out bits compatible with many earlier descriptions. If the existing network wants to support its own hard-fork opt-out bit, it should execute a soft fork as soon as possible. It is inadequate for a new network to rely on non-standardness in the existing network to prevent replay there. A responsible new network would allow something that is invalid in the existing network if replay to the existing network is undesirable. Johnson's BIP suggesting specific changes to be included in the new network is an overreach as it is a matter for the new network itself. The proposal suggests implementing a specific O(n^2) fix, which is not necessary.
TLDR
We’ll email you summaries of the latest discussions from authoritative bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.
We'd love to hear your feedback on this project?
Give Feedback