Dev Docs: update v4 blocks text; mention version bits

Closes #1106
This commit is contained in:
David A. Harding 2015-10-26 12:07:23 -04:00
parent 6e03f717c1
commit 666ed01974
No known key found for this signature in database
GPG key ID: 4B29C30FF29EC4B7

View file

@ -72,17 +72,21 @@ fe9f0864 ........................... Nonce
encoding had previously been non-standard since Bitcoin Core 0.8.0 encoding had previously been non-standard since Bitcoin Core 0.8.0
(February 2012). (February 2012).
* **Version 4** blocks will likely be introduced in the near-future as * **Version 4** blocks will likely be introduced in the near future as
specified in draft BIP62. Possible changes include: specified in BIP65. These blocks will support the new
`OP_CHECKLOCKTIMEVERIFY` opcode described in that BIP.
* Reject version 4 blocks that include any version 2 transactions The mechanism used for the version 2, 3, and 4 upgrades is commonly
that don't adhere to any of the version 2 transaction rules. called IsSuperMajority() after the function added to Bitcoin Core to
These rules are not yet described in this documentation; see manage those soft forking changes. See BIP34 for a full description of
BIP62 for details. this method.
* A soft fork rollout of version 4 blocks identical to the rollout As of this writing, a newer method called *version bits* is being designed
used for version 3 blocks (described briefly in BIP62 and in more to manage future soft forking changes, although it's not known whether
detail in BIP34). version 4 will be the last soft fork to use the IsSuperMajority()
function. Draft BIP9 describes the version bits design as of this
writing, although it is still being actively edited and may
substantially change while in the draft state.
{% endautocrossref %} {% endautocrossref %}