I think it is very naïve to assume that any shift would be temporary. We have a hard enough time getting miners to proactively upgrade to recent versions of the reference bitcoin daemon. If miners interpret the situation as being forced to run non-reference software in order to prevent a chain split because a lack of support from Bitcoin Core, that could be a one-way street.
On Tue, Jun 20, 2017 at 9:49 AM, Hampus Sjöberg via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote: > I don't think it's a huge deal if the miners need to run a non-Core node > once the BIP91 deployment of Segwit2x happens. The shift will most likely be > temporary. > > I agree that the "-bip148"-option should be merged, though. > > 2017-06-20 17:44 GMT+02:00 Erik Aronesty via bitcoin-dev > <bitcoin-dev@lists.linuxfoundation.org>: >> >> Are we going to merge BIP91 or a -BIP148 option to core for inclusion in >> the next release or so? >> >> Because a large percentage of miners are indifferent, right now miners >> have to choose between BIP148 and Segwit2x if they want to activate Segwit. >> >> Should we be forcing miners to choose to run non-core code in order to >> activate a popular feature? >> >> - Erik >> >> _______________________________________________ >> bitcoin-dev mailing list >> bitcoin-dev@lists.linuxfoundation.org >> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev >> > > > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > _______________________________________________ bitcoin-dev mailing list bitcoin-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev