Re: [bitcoin-dev] Draft BIP: Version bits extension with guaranteed lock-in

> After some thought I managed to simplify the original uaversionbits proposal > introducing a simple boolean flag to guarantee lock-in of a BIP9 deployment > by the timeout. This seems to be the simplest form combining optional flag > day activation with BIP9. This brings the best of both

Re: [bitcoin-dev] Draft BIP: Version bits extension with guaranteed lock-in

Praxeology Guy, On Fri, Apr 7, 2017 at 12:56 PM, praxeology_guy wrote: > TLDR Unless I'm missing something, your claim that a > misconfiguration would result in a stop chain is wrong because BIP9 > only works on soft forks. If our rule change timing is different

Re: [bitcoin-dev] Draft BIP: Version bits extension with guaranteed lock-in

al Message Subject: Re: [bitcoin-dev] Draft BIP: Version bits extension with guaranteed lock-in Local Time: April 7, 2017 8:55 AM UTC Time: April 7, 2017 1:55 PM From: bitcoin-dev@lists.linuxfoundation.org To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org> The prim

Re: [bitcoin-dev] Draft BIP: Version bits extension with guaranteed lock-in

The primary failure mode of a user's misconfiguration of nTimeout will be a stopped chain. If less-sophisticated users are offered these configuration settings then chaintip progress failures that result from them should be prominently displayed. ___

[bitcoin-dev] Draft BIP: Version bits extension with guaranteed lock-in

After some thought I managed to simplify the original uaversionbits proposal introducing a simple boolean flag to guarantee lock-in of a BIP9 deployment by the timeout. This seems to be the simplest form combining optional flag day activation with BIP9. This brings the best of both worlds