bitcoin/bips
1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2026-02-23 15:38:22 +00:00
Code Issues Releases Wiki Activity

Merge pull request #1766 from jonatack/2025-02-implementors-to-implementers

Browse Source 
spelling: globally change "implementor" to "implementer"
This commit is contained in:
Mark "Murch" Erhardt
2025-02-13 15:15:23 -05:00
committed by GitHub
parent 0203ede3b4 468e9759ba
commit 6651d5c82f
12 changed files with 14 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
bip-0119.mediawiki
View File

@@ -213,7 +213,7 @@ a NOP for consensus (during block validation).
In order to facilitate using CHECKTEMPLATEVERIFY, the common case of a
PayToBareDefaultCheckTemplateVerifyHash
with no scriptSig data may (is recommended to) be made standard to permit relaying. Future template types may be
standardized later as policy changes at the preference of the implementor.
standardized later as policy changes at the preference of the implementer.
==Reference Implementation==
@@ -480,7 +480,7 @@ If the scriptSigs non-nullity is not cached, then the O(T) transaction could be
times as well (although cheaper than hashing, still a DoS). As such, CTV caches hashes and computations
over all variable length fields in a transaction.
For CTV, the Denial-of-Service exposure and validation costs are relatively clear. Implementors must be careful
For CTV, the Denial-of-Service exposure and validation costs are relatively clear. Implementers must be careful
to correctly code CTV to make use of existing caches and cache the (new for CTV) computations over scriptSigs.
Other more flexible covenant proposals may have a more difficult time solving DoS issues as more complex computations may
be less cacheable and expose issues around quadratic hashing, it is a tradeoff CTV makes in favor of cheap and secure