highperfocused/bips
1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2025-03-17 05:12:58 +01:00
Code Issues Packages Projects Releases Wiki Activity

fix: grammatical typos

Browse Source
This commit is contained in:
Ethan Tuttle 2025-03-09 21:01:44 -04:00 committed by GitHub
parent 33231097c2
commit 9573e060e3
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
bip-0119.mediawiki
View File

@ -471,7 +471,7 @@ As such, evaluating a CTV hash during consensus is always O(1) computation when
These caches usually must be available due to similar issues in CHECKSIG behavior. Computing the caches
is O(T) (the size of the transaction).
An example of a script that could experience an DoS issue without caching is:
An example of a script that could experience a DoS issue without caching is:
<H> CTV CTV CTV... CTV
@ -492,7 +492,7 @@ caching of all combinations of outputs would not be possible and would cause a q
The preimage argument passed to CHECKTEMPLATEVERIFY may be unknown or otherwise unsatisfiable.
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 before sending, they may request a signature of a provably non-transaction challenge string
from the leaves of the CHECKTEMPLATEVERIFY tree.
====Forwarding Addresses====
@ -532,7 +532,7 @@ the restrictions for standardness while tightening them for consensus with the u
The standardness rules may lead an unscrupulous script developer to accidentally rely on the
stricter standardness rules to be enforced during consensus. Should that developer submit a
transaction directly to the network relying on standardness rejection, an standardness-invalid but
transaction directly to the network relying on standardness rejection, a standardness-invalid but
consensus-valid transaction may be caused, leading to a potential loss of funds.
====Feature Redundancy====