Draft release notes for 0.11.2 to include BIP 66.

doc/release-notes.md

@@ -1,95 +1,5 @@
-Bitcoin Core version 0.9.4 is now available from:
+Darkcoin Core tree 0.11.x release notes can be found here:
 
-  https://bitcoin.org/bin/0.9.4/
+- [v0.11.0](release-notes/release-notes-0.11.0.md) released Jan/15/2015
-
+- [v0.11.1](release-notes/release-notes-0.11.1.md) released Feb/10/2015.
-This is a new minor version release, bringing only bug fixes and updated
+- [v0.11.2](release-notes/release-notes-0.11.2.md) not released yet.
-translations. Upgrading to this release is recommended.
-
-Please report bugs using the issue tracker at github:
-
-  https://github.com/bitcoin/bitcoin/issues
-
-How to Upgrade
-===============
-
-If you are running an older version, shut it down. Wait until it has completely
-shut down (which might take a few minutes for older versions), then run the
-installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac) or
-bitcoind/bitcoin-qt (on Linux).
-
-OpenSSL Warning
-================
-
-OpenSSL 1.0.0p / 1.0.1k was recently released and is being pushed out by
-various operating system maintainers. Review by Gregory Maxwell determined that
-this update is incompatible with the Bitcoin system and could lead to consensus
-forks.
-
-Bitcoin Core released binaries from https://bitcoin.org are unaffected,
-as are any built with the gitian deterministic build system.
-
-However, if you are running either
-
-- The Ubuntu PPA from https://launchpad.net/~bitcoin/+archive/ubuntu/bitcoin
-- A third-party or self-compiled Bitcoin Core
-
-upgrade to Bitcoin Core 0.9.4, which includes a workaround, **before** updating
-OpenSSL.
-
-The incompatibility is due to the OpenSSL update changing the
-behavior of ECDSA validation to reject any signature which is
-not encoded in a very rigid manner. This was a result of
-OpenSSL's change for CVE-2014-8275 "Certificate fingerprints
-can be modified".
-
-We are specifically aware of potential hard-forks due to signature
-encoding handling and had been hoping to close them via BIP62 in 0.10.
-BIP62's purpose is to improve transaction malleability handling and
-as a side effect rigidly defines the encoding for signatures, but the
-overall scope of BIP62 has made it take longer than we'd like to
-deploy.
-
-0.9.4 changelog
-================
-
-Validation:
-- `b8e81b7` consensus: guard against openssl's new strict DER checks
-- `60c51f1` fail immediately on an empty signature
-- `037bfef` Improve robustness of DER recoding code
-
-Command-line options:
-- `cd5164a` Make -proxy set all network types, avoiding a connect leak.
-
-P2P:
-- `bb424e4` Limit the number of new addressses to accumulate
-
-RPC:
-- `0a94661` Disable SSLv3 (in favor of TLS) for the RPC client and server.
-
-Build system:
-- `f047dfa` gitian: openssl-1.0.1i.tar.gz -> openssl-1.0.1k.tar.gz
-- `5b9f78d` build: Fix OSX build when using Homebrew and qt5
-- `ffab1dd` Keep symlinks when copying into .app bundle
-- `613247f` osx: fix signing to make Gatekeeper happy (again)
-
-Miscellaneous:
-- `25b49b5` Refactor -alertnotify code
-- `2743529` doc: Add instructions for consistent Mac OS X build names
-
-Credits
---------
-
-Thanks to who contributed to this release, at least:
-
-- Cory Fields
-- Gavin Andresen
-- Gregory Maxwell
-- Jeff Garzik
-- Luke Dashjr
-- Matt Corallo
-- Pieter Wuille
-- Saivann
-- Sergio Demian Lerner
-- Wladimir J. van der Laan
-
-As well as everyone that helped translating on [Transifex](https://www.transifex.com/projects/p/bitcoin/).

doc/release-notes/release-notes-0.11.2.md

@@ -0,0 +1,21 @@
+*This is a draft!*
+
+0.11.2 Release notes
+====================
+
+Mining and relay policy enhancements
+------------------------------------
+
+Darkcoin Core's block templates are now for version 3 blocks only, and any mining software relying on its `getblocktemplate` must be updated in parallel to use libblkmaker either version 0.4.2 or any version from 0.5.1 onward. If you are solo mining, this will affect you the moment you upgrade Darkcoin Core, which must be done prior to BIP66 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 BIP66 achieving its 951/1001 status.
+
+
+BIP 66: strict DER encoding for signatures
+------------------------------------------
+
+Darkcoin Core 0.11.2 implements BIP 66, which introduces block version 3, and a new consensus rule, which prohibits non-DER signatures. Such transactions have been non-standard since Darkcoin 0.8, but were technically still permitted inside blocks.
+This change breaks the dependency on OpenSSL's signature parsing, and is required if implementations would want to remove all of OpenSSL from the consensus code.
+The same miner-voting mechanism as in BIP 34 is used: when 751 out of a sequence of 1001 blocks have version number 3 or higher, the new consensus rule becomes active for those blocks. When 951 out of a sequence of 1001 blocks have version number 3 or higher, it becomes mandatory for all blocks.
+Backward compatibility with current mining software is NOT provided, thus miners should read the first paragraph of "Mining and relay policy enhancements" above.
+
+Also compare with [upstream release notes](https://github.com/bitcoin/bitcoin/blob/0.10/doc/release-notes.md#mining-and-relay-policy-enhancements).
+More info on [BIP 66](https://github.com/bitcoin/bips/blob/master/bip-0066.mediawiki).