bitcoin/bips
1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2025-05-12 12:03:29 +00:00
Code Issues Releases Wiki Activity

Fix typos in BIP-0370 and BIP-0373 (#1718)

Browse Source 
* Update bip-0370.mediawiki

* Update bip-0373.mediawiki
This commit is contained in:
Maks 2024-12-17 14:18:20 +01:00 committed by GitHub
parent f88f1e4392
commit 4c7d1292dd
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
bip-0370.mediawiki
View File

@ -42,7 +42,7 @@ PSBT Version 2 (PSBTv2) only specifies new fields and field inclusion/exclusion
<tt>PSBT_GLOBAL_UNSIGNED_TX</tt> must be excluded in PSBTv2. <tt>PSBT_GLOBAL_UNSIGNED_TX</tt> must be excluded in PSBTv2.
<tt>PSBT_GLOBAL_VERSION</tt> must be included in PSBTv2 and set to version number 2<ref>'''What happened to version number 1?''' <tt>PSBT_GLOBAL_VERSION</tt> must be included in PSBTv2 and set to version number 2<ref>'''What happened to version number 1?'''
Version number 1 is skipped because PSBT Version 0 has been colloquially referred to as version 1. Originally this BIP was to be Version number 1 is skipped because PSBT Version 0 has been colloquially referred to as version 1. Originally this BIP was to be
version 1, but because it has been colloquially referred to as version 2 during its design phrase, it was decided to change the version 1, but because it has been colloquially referred to as version 2 during its design phase, it was decided to change the
version number to 2 so that there would not be any confusion</ref>. version number to 2 so that there would not be any confusion</ref>.
The new global types for PSBT Version 2 are as follows: The new global types for PSBT Version 2 are as follows:

4
bip-0373.mediawiki
View File

@ -130,7 +130,7 @@ required for aggregation. If sorting was done, then the keys must be in the sort
===Updater=== ===Updater===
When an updater observes a Taproot output which involves a MuSig2 aggregate public key that it is When an updater observes a Taproot output which involves a MuSig2 aggregate public key that it is
aware if, it can add a <tt>PSBT_IN_MUSIG2_PARTICIPANT_PUBKEYS</tt> field containing the public keys aware of, it can add a <tt>PSBT_IN_MUSIG2_PARTICIPANT_PUBKEYS</tt> field containing the public keys
of the participants. This aggregate public key may be directly in the script, the Taproot internal of the participants. This aggregate public key may be directly in the script, the Taproot internal
key, the Taproot output key, or a public key from which the key in the script was derived from. key, the Taproot output key, or a public key from which the key in the script was derived from.
@ -171,7 +171,7 @@ partial signature for their key. The result will be added to the PSBT in a
<tt>PSBT_IN_MUSIG2_PARTIAL_SIG</tt> field. <tt>PSBT_IN_MUSIG2_PARTIAL_SIG</tt> field.
Signers must remember to apply any relevant tweaks such as a tweak that is the result of performing Signers must remember to apply any relevant tweaks such as a tweak that is the result of performing
BIP 32 unhardened dervation with the aggregate public key as the parent key. BIP 32 unhardened derivation with the aggregate public key as the parent key.
If all other signers have provided a <tt>PSBT_IN_MUSIG2_PARTIAL_SIG</tt>, then the final signer may If all other signers have provided a <tt>PSBT_IN_MUSIG2_PARTIAL_SIG</tt>, then the final signer may
perform the <tt>PartialSigAgg</tt> algorithm and produce a BIP 340 compatible signature that can be perform the <tt>PartialSigAgg</tt> algorithm and produce a BIP 340 compatible signature that can be