Rusty Russell [ARCHIVE] on Nostr: 📅 Original date posted:2015-09-17 📝 Original message:Tier Nolan via bitcoin-dev ...
📅 Original date posted:2015-09-17
📝 Original message:Tier Nolan via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org> writes:
> On Wed, Sep 16, 2015 at 9:19 PM, Rusty Russell <rusty at rustcorp.com.au>
> wrote:
>> You need a timeout: an ancient (non-mining, thus undetectable) node
>> should never fork itself off the network because someone reused a failed
>> BIP bit.
>>
>
> I meant if the 2nd bit was part of the BIP. One of the 2 bits is "FOR" and
> the other is "AGAINST". If against hits 25%, then it is deemed a failure.
>
> The 2nd bit wouldn't be used normally. This means that proposals can be
> killed quickly if they are obviously going to fail.
This could be added if we approach one failed soft fork every 5 weeks,
I guess (or it could be just for specific soft forks).
Cheers,
Rusty.
📝 Original message:Tier Nolan via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org> writes:
> On Wed, Sep 16, 2015 at 9:19 PM, Rusty Russell <rusty at rustcorp.com.au>
> wrote:
>> You need a timeout: an ancient (non-mining, thus undetectable) node
>> should never fork itself off the network because someone reused a failed
>> BIP bit.
>>
>
> I meant if the 2nd bit was part of the BIP. One of the 2 bits is "FOR" and
> the other is "AGAINST". If against hits 25%, then it is deemed a failure.
>
> The 2nd bit wouldn't be used normally. This means that proposals can be
> killed quickly if they are obviously going to fail.
This could be added if we approach one failed soft fork every 5 weeks,
I guess (or it could be just for specific soft forks).
Cheers,
Rusty.