aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Todd <pete@petertodd.org>2014-12-23 19:31:02 +0100
committerWladimir J. van der Laan <laanwj@gmail.com>2014-12-23 19:31:02 +0100
commit2bb0ca9b5549e6612a71e9a046b3a973bc346195 (patch)
tree79c0fdfa699f8c2e084d469d70bddf6b4d30874b
parenta2300499b76e1a3654241f871ab53d5f6b95308e (diff)
downloadbitcoin-2bb0ca9b5549e6612a71e9a046b3a973bc346195.tar.xz
doc: mention P2SH IsStandard relaxation in release notes
-rw-r--r--doc/release-notes.md11
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/release-notes.md b/doc/release-notes.md
index 803bb33e6b..e1998c6bdf 100644
--- a/doc/release-notes.md
+++ b/doc/release-notes.md
@@ -195,6 +195,17 @@ correctly spends the passed scriptPubKey under additional constraints indicated
The functionality is planned to be extended to e.g. UTXO management in upcoming releases, but the interface
for existing methods should remain stable.
+Standard script rules relaxed for P2SH addresses
+================================================
+
+The IsStandard() rules have been almost completely removed for P2SH
+redemption scripts, allowing applications to make use of any valid
+script type, such as "n-of-m OR y", hash-locked oracle addresses, etc.
+While the Bitcoin protocol has always supported these types of script,
+actually using them on mainnet has been previously inconvenient as
+standard Bitcoin Core nodes wouldn't relay them to miners, nor would
+most miners include them in blocks they mined.
+
0.10.0 Release notes
=======================