diff options
| author | Peter Todd <pete@petertodd.org> | 2015-10-23 16:16:07 -0400 |
|---|---|---|
| committer | Peter Todd <pete@petertodd.org> | 2015-10-23 16:19:49 -0400 |
| commit | c939792baaaa5f34ee4079b871d56054e36fb26b (patch) | |
| tree | 1679b42104555e7db0a1e5d2f9e7eb1f37c93894 /doc/release-notes.md | |
| parent | 46f74379b86be982b121bcb8c3cfe07fa80bffd0 (diff) | |
Add BIP65 CHECKLOCKTIMEVERIFY to release notes
Diffstat (limited to 'doc/release-notes.md')
| -rw-r--r-- | doc/release-notes.md | 27 |
1 files changed, 27 insertions, 0 deletions
diff --git a/doc/release-notes.md b/doc/release-notes.md index e9b2d75a76..fd034743e6 100644 --- a/doc/release-notes.md +++ b/doc/release-notes.md @@ -124,6 +124,33 @@ sanity check. Since 0.12, these are no longer stored. When loading a 0.12 wallet into an older version, it will automatically rescan to avoid failed checks. +BIP65 - CHECKLOCKTIMEVERIFY +--------------------------- + +Previously it was impossible to create a transaction output that was guaranteed +to be unspendable until a specific date in the future. CHECKLOCKTIMEVERIFY is a +new opcode that allows a script to check if a specific block height or time has +been reached, failing the script otherwise. This enables a wide variety of new +functionality such as time-locked escrows, secure payment channels, etc. + +BIP65 implements CHECKLOCKTIMEVERIFY by introducing block version 4, which adds +additional restrictions to the NOP2 opcode. The same miner-voting mechanism as +in BIP34 and BIP66 is used: when 751 out of a sequence of 1001 blocks have +version number 4 or higher, the new consensus rule becomes active for those +blocks. When 951 out of a sequence of 1001 blocks have version number 4 or +higher, it becomes mandatory for all blocks and blocks with versions less than +4 are rejected. + +Bitcoin Core's block templates are now for version 4 blocks only, and any +mining software relying on its `getblocktemplate` must be updated in parallel +to use either libblkmaker version FIXME or any version from 0.5.1 onward. If +you are solo mining, this will affect you the moment you upgrade Bitcoin Core, +which must be done prior to BIP65 achieving its 951/1001 status. If you are +mining with the stratum mining protocol: this does not affect you. If you are +mining with the getblocktemplate protocol to a pool: this will affect you at +the pool operator's discretion, which must be no later than BIP65 achieving its +951/1001 status. + 0.12.0 Change log ================= |