summaryrefslogtreecommitdiff
path: root/bip-0119.mediawiki
diff options
context:
space:
mode:
authorJose Storopoli <jose@storopoli.io>2024-07-25 16:24:55 -0300
committerJose Storopoli <jose@storopoli.io>2024-08-07 19:02:47 -0300
commitda1e3ad5456b800120a7f98a9816024465dc50d3 (patch)
treeed45175a62b45fe50acf959e0834f7f7254444dc /bip-0119.mediawiki
parentc25032a3ff2bd0140c56ea6dbfaa885c7ee75bfb (diff)
bip-119: fix typo
Diffstat (limited to 'bip-0119.mediawiki')
-rw-r--r--bip-0119.mediawiki4
1 files changed, 2 insertions, 2 deletions
diff --git a/bip-0119.mediawiki b/bip-0119.mediawiki
index be1f70c..6ca0adb 100644
--- a/bip-0119.mediawiki
+++ b/bip-0119.mediawiki
@@ -392,7 +392,7 @@ transaction preimages.
=====Using Non-Tagged Hashes=====
The Taproot/Schnorr BIPs use Tagged Hashes
-(`SHA256(SHA256(tag)||SHA256(tag)||msg)`) to prevent taproot leafs, branches,
+(`SHA256(SHA256(tag)||SHA256(tag)||msg)`) to prevent taproot leaves, branches,
tweaks, and signatures from overlapping in a way that might introduce a security
[vulnerability https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2018-June/016091.html].
@@ -494,7 +494,7 @@ The preimage argument passed to CHECKTEMPLATEVERIFY may be unknown or otherwise
However, requiring knowledge that an address is spendable from is incompatible with sender's ability
to spend to any address (especially, OP_RETURN). If a sender needs to know the template can be spent
from before sending, they may request a signature of an provably non-transaction challenge string
-from the leafs of the CHECKTEMPLATEVERIFY tree.
+from the leaves of the CHECKTEMPLATEVERIFY tree.
====Forwarding Addresses====