On Sun, Jun 11, 2017 at 3:44 PM, Martijn Meijering via bitcoin-dev <[email protected]> wrote: > Jorge Timón wrote: > Why not just make sure BIP 149 will never activate unless BIP 141 has > expired unsuccessfully?
Right, that would be part of it, as well as not removing the BIP141 deployment with bip9. See https://github.com/jtimon/bitcoin/commit/62efd741740f5c75c43d78358d6318941e6d3c04 > If BIP 141 should unexpectly activate, then > BIP 149 nodes would notice and act as pre-SegWit nodes indefinitely, > but remain in consensus with BIP 141 nodes. > > It might be slightly less convenient for BIP 149 users to upgrade > again, but then at least we could start deploying BIP 149 sooner. No, if segwit activates pre nov15, bip149 nodse can detect and interpret that just fine. The problem if it activates post nov15, then you need a separate service bit in the p2p network, for pre-BIP149 will think sw hasn't activated while post-BIP149 would know it has activated. If you release it only after nov15, you don't need to test compatibility between the two for neither of this two cases. Or do you? Actually you only save testing the easier case of pre-nov15 activation. > _______________________________________________ > bitcoin-dev mailing list > [email protected] > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev _______________________________________________ bitcoin-dev mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
