mirror of
https://github.com/bitcoin/bips.git
synced 2025-05-19 12:08:05 +00:00
bip-119: fix typo
This commit is contained in:
parent
c25032a3ff
commit
da1e3ad545
@ -392,7 +392,7 @@ transaction preimages.
|
|||||||
=====Using Non-Tagged Hashes=====
|
=====Using Non-Tagged Hashes=====
|
||||||
|
|
||||||
The Taproot/Schnorr BIPs use 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
|
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].
|
[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
|
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
|
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 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====
|
====Forwarding Addresses====
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user