From 4774e4d1e8d856567ad2de9a39b2b3a29f35422a Mon Sep 17 00:00:00 2001 From: Fabian Jahr Date: Tue, 5 Nov 2019 14:53:16 +0100 Subject: Link design section of BIP Schnorr in Specification --- bip-taproot.mediawiki | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 ''hashtag(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 ''hashtag'' 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 ''hashtag(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 ''hashtag'' with other hashes extremely unlikely. === Script validation rules === -- cgit v1.2.3