summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFabian Jahr <fabjahr@gmail.com>2019-11-05 14:53:16 +0100
committerPieter Wuille <pieter.wuille@gmail.com>2020-01-19 14:47:33 -0800
commit4774e4d1e8d856567ad2de9a39b2b3a29f35422a (patch)
treea66eb147dbf8eb55467f2cb05227155aaa88605e
parent3d97967b97831dc268b39bc8b667d6aace0dc56a (diff)
downloadbips-4774e4d1e8d856567ad2de9a39b2b3a29f35422a.tar.xz
Link design section of BIP Schnorr in Specification
-rw-r--r--bip-taproot.mediawiki2
1 files changed, 1 insertions, 1 deletions
diff --git a/bip-taproot.mediawiki b/bip-taproot.mediawiki
index d408357..d8f51ca 100644
--- a/bip-taproot.mediawiki
+++ b/bip-taproot.mediawiki
@@ -50,7 +50,7 @@ Not included in this proposal are additional features like new sighash modes or
This section specifies the Taproot consensus rules. Validity is defined by exclusion: a block or transaction is valid if no condition exists that marks it failed.
-The notation below follows that of bip-schnorr. This includes the ''hash<sub>tag</sub>(x)'' notation to refer to ''SHA256(SHA256(tag) || SHA256(tag) || x)''. To the best of the authors' knowledge, no existing use of SHA256 in Bitcoin feeds it a message that starts with two single SHA256 outputs, making collisions between ''hash<sub>tag</sub>'' with other hashes extremely unlikely.
+The notation below follows that of [https://github.com/sipa/bips/blob/bip-schnorr/bip-schnorr.mediawiki#design bip-schnorr]. This includes the ''hash<sub>tag</sub>(x)'' notation to refer to ''SHA256(SHA256(tag) || SHA256(tag) || x)''. To the best of the authors' knowledge, no existing use of SHA256 in Bitcoin feeds it a message that starts with two single SHA256 outputs, making collisions between ''hash<sub>tag</sub>'' with other hashes extremely unlikely.
=== Script validation rules ===