From 6823404c6870d48c5c634f52a1056e0083c0b5c2 Mon Sep 17 00:00:00 2001 From: "David A. Harding" Date: Fri, 23 Oct 2015 09:55:28 -0400 Subject: [PATCH] Dev Docs: update text about v3 blocks/BIP66 Closes #1084 --- _includes/devdoc/ref_block_chain.md | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/_includes/devdoc/ref_block_chain.md b/_includes/devdoc/ref_block_chain.md index c1d41f37..23f6b555 100644 --- a/_includes/devdoc/ref_block_chain.md +++ b/_includes/devdoc/ref_block_chain.md @@ -65,13 +65,12 @@ fe9f0864 ........................... Nonce -* **Version 3** blocks will be introduced when sufficient numbers of - miners switch to using Bitcoin Core 0.10.0 and other versions that - create version 3 blocks. As described in draft BIP66, this soft fork - change requires strict DER encoding for all ECDSA signatures used in - transactions appearing in version 3 or later blocks. Transactions that - do not use strict DER encoding have been non-standard since Bitcoin - Core 0.8.0. +* **Version 3** blocks were introduced in Bitcoin Core 0.10.0 (February + 2015) as a soft fork. When the fork reach full enforcement (July + 2015), it required strict DER encoding of all ECDSA signatures in new + blocks as described in BIP66. Transactions that do not use strict DER + encoding had previously been non-standard since Bitcoin Core 0.8.0 + (February 2012). * **Version 4** blocks will likely be introduced in the near-future as specified in draft BIP62. Possible changes include: