BIP: 8 Title: Version bits with guaranteed lock-in Author: Shaolin Fry <[email protected]> Comments-Summary: No comments yet. Comments-URI: https://github.com/bitcoin/bips/wiki/Comments:BIP-0008 Status: Draft Type: Informational Created: 2017-02-01 License: BSD-3-Clause CC0-1.0
This document specifies an extension to BIP9 that introduces an additional activation parameter to guarantee activation of backward-compatible changes (further called "soft forks").
BIP9 introduced a mechanism for doing parallel soft forking deployments based on repurposing the block nVersion field. Activation is dependent on near unanimous hashrate signalling which may be impractical and is also subject to veto by a small minority of non-signalling hashrate.
This specification provides a way to optionally guarantee lock-in at the end of the BIP9 timeout, and therefore activation, while still allowing a hashrate super majority to trigger activation earlier.
This specification is the same as BIP9 except from the STARTED state, there is no FAILED condition. The state transition from STARTED to LOCKED_IN will occur under two condition:
The first is when the threshold of blocks signalling is reached as per BIP9. The second is if the timeout is still STARTED.
During the STARTED state if the lockinontimeout is set to true, the state will transition to LOCKED_IN when timeout is reached.
case STARTED:
// BIP8/9 specification follows
if (GetMedianTimePast(block.parent) >= timeout) {
// implementation detail: if flag set, BIP8 workflow, else BIP9 workflow.
return (fLockInOnTimeout == true) ? THRESHOLD_LOCKED_IN : THRESHOLD_FAILED
}
int count = 0;
walk = block;
for (i = 0; i < 2016; i++) {
walk = walk.parent;
if (walk.nVersion & 0xE0000000 == 0x20000000 && (walk.nVersion >> bit) & 1 == 1) {
count++;
}
}
if (count >= threshold) {
return LOCKED_IN;
}
return STARTED;
https://github.com/bitcoin/bitcoin/compare/master...shaolinfry:bip-uaversionbits
BIP8 and BIP9 deployments should not share concurrent active deployment bits. Nodes that only implement BIP9 will not activate a BIP8 soft fork if hashpower threshold is not reached by timeout, however, those nodes will still accept the blocks generated by activated nodes.
A living list of deployment proposals can be found here.
This document is dual licensed as BSD 3-clause, and Creative Commons CC0 1.0 Universal.