diff options
| author | Wladimir J. van der Laan <laanwj@gmail.com> | 2016-01-13 18:20:06 +0100 |
|---|---|---|
| committer | Wladimir J. van der Laan <laanwj@gmail.com> | 2016-01-13 18:20:06 +0100 |
| commit | 5771b71ca533d712893c7895204a47c9ad70c9c7 (patch) | |
| tree | 55dcb078619d3b5e890fd2cdf048f7975ef29abf | |
| parent | 3d5cf698d60eaa22ede6937207a205aede4212ff (diff) | |
doc: Remove BIP65 mention from release notes
This is already done, not new in 0.12.
| -rw-r--r-- | doc/release-notes.md | 27 |
1 files changed, 0 insertions, 27 deletions
diff --git a/doc/release-notes.md b/doc/release-notes.md index 3d4816ae9a..473f29d10e 100644 --- a/doc/release-notes.md +++ b/doc/release-notes.md @@ -160,33 +160,6 @@ Priority code is planned to get moved out of from Bitcoin Core 0.13 and the default block priority size has been set to `0` in Bitcoin Core 0.12. -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 0.4.3 or any version from 0.5.2 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. - Automatically use Tor hidden services ------------------------------------- |