diff options
| author | BtcDrak <btcdrak@gmail.com> | 2015-10-03 23:26:22 +0100 |
|---|---|---|
| committer | BtcDrak <btcdrak@gmail.com> | 2015-10-03 23:26:22 +0100 |
| commit | 315bd227d717cb57aa42abb14816671bd07bee8f (patch) | |
| tree | 0bae89c1aa1fcdef41d0c210b3756409729b543f /bip-0112.mediawiki | |
| parent | 4b0c6dc4ad23fce54b75182b43ec314fc8889ef3 (diff) | |
| download | bips-315bd227d717cb57aa42abb14816671bd07bee8f.tar.xz | |
Change deployment to simple ISM
Diffstat (limited to 'bip-0112.mediawiki')
| -rw-r--r-- | bip-0112.mediawiki | 16 |
1 files changed, 4 insertions, 12 deletions
diff --git a/bip-0112.mediawiki b/bip-0112.mediawiki index 4773b17..097a136 100644 --- a/bip-0112.mediawiki +++ b/bip-0112.mediawiki @@ -207,21 +207,13 @@ https://github.com/maaku/bitcoin/tree/checksequenceverify ==Deployment== We reuse the double-threshold switchover mechanism from BIPs 34 and -66, with the same thresholds, but for nVersion = 8. The new rules are -in effect for every block (at height H) with nVersion = 8 and at least +66, with the same thresholds, but for nVersion = 4. The new rules are +in effect for every block (at height H) with nVersion = 4 and at least 750 out of 1000 blocks preceding it (with heights H-1000..H-1) also -have nVersion = 8. Furthermore, when 950 out of the 1000 blocks -preceding a block do have nVersion = 8, nVersion = 3 blocks become +have nVersion = 4. Furthermore, when 950 out of the 1000 blocks +preceding a block do have nVersion = 4, nVersion = 3 blocks become invalid, and all further blocks enforce the new rules. -When assessing the block version as mask of ~0x20000007 must be applied -to work around the complications caused by -[http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-August/010396.html BIP101's premature use] -of the [https://gist.github.com/sipa/bf69659f43e763540550 undecided version bits proposal]. - -By applying ~0x20000007 with nVersion = 8, the thresholds should be tested -comparing block nVersion >= 4 as this will save a bit for future use. - It is recommended that this soft-fork deployment trigger include other related proposals for improving Bitcoin's lock-time capabilities, including: |