Simplify UASF Activation Logic, and update specification. #514

pull da2ce7 wants to merge 1 commits into bitcoin:master from da2ce7:bip148 changing 1 files +1 −2

da2ce7 commented at 9:10 AM on April 10, 2017: contributor

Updated BIP 148 Activation Logic, as the timeout of this BIP is completely redundant.
Simplify UASF Activation Logic, and update specification. 3626a3b9d4
da2ce7 commented at 9:10 AM on April 10, 2017: contributor

@shaolinfry please review.
da2ce7 cross-referenced this on Apr 10, 2017 from issue BIP148: UASF-Segwit by sneurlax
da2ce7 commented at 9:29 AM on April 10, 2017: contributor

I'm going to withdraw this pull request, as dealing with the logic for a very slow hash-rate after the enforced period starts.
da2ce7 closed this on Apr 10, 2017
shaolinfry commented at 10:16 AM on April 10, 2017: contributor

In case you arent aware of the discussions, the reason the date was moved to Aug 1 was exactly to handle a ridiculous drop in hashrate, regardless of how unlikely.

dooglus commented at 6:19 PM on April 10, 2017: contributor

There's no point in having this UASF active after the SegWit activation period has timed out.

From Bitcoin's src/chainparams.cpp:

    // Deployment of SegWit (BIP141, BIP143, and BIP147)
    consensus.vDeployments[Consensus::DEPLOYMENT_SEGWIT].bit = 1;
    consensus.vDeployments[Consensus::DEPLOYMENT_SEGWIT].nStartTime = 1479168000; // November 15th, 2016.
    consensus.vDeployments[Consensus::DEPLOYMENT_SEGWIT].nTimeout = 1510704000; // November 15th, 2017.

Contributors

da2ce7

shaolinfry

dooglus