diff options
| author | John Bampton <jbampton@users.noreply.github.com> | 2024-05-01 06:54:05 +1000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-04-30 16:54:05 -0400 |
| commit | f61885edcf5e63ac205b1ca5f08173f1336bff74 (patch) | |
| tree | 2d577255ee2fd3c3c5743edf1c0184a67abcb7d2 /bip-0067.mediawiki | |
| parent | 2d9e431fbe654640b55bca3bf8c4b17462890109 (diff) | |
| download | bips-f61885edcf5e63ac205b1ca5f08173f1336bff74.tar.xz | |
docs: fix spelling (#1117)
Co-authored-by: Mark "Murch" Erhardt <murch@murch.one>
Diffstat (limited to 'bip-0067.mediawiki')
| -rw-r--r-- | bip-0067.mediawiki | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/bip-0067.mediawiki b/bip-0067.mediawiki index 793039d..a31cc3d 100644 --- a/bip-0067.mediawiki +++ b/bip-0067.mediawiki @@ -53,10 +53,10 @@ Hash the redeem script according to BIP-0016 to get the P2SH address. 3Q4sF6tv9wsdqu2NtARzNCpQgwifm2rAba ==Compatibility== -* Uncompressed keys are incompatible with this specificiation. A compatible implementation should not automatically compress keys. Receiving an uncompressed key from a multisig participant should be interpreted as a sign that the user has an incompatible implementation. -* P2SH addressses do not reveal information about the script that is receiving the funds. For this reason it is not technically possible to enforce this BIP as a rule on the network. Also, it would cause a hard fork. +* Uncompressed keys are incompatible with this specification. A compatible implementation should not automatically compress keys. Receiving an uncompressed key from a multisig participant should be interpreted as a sign that the user has an incompatible implementation. +* P2SH addresses do not reveal information about the script that is receiving the funds. For this reason it is not technically possible to enforce this BIP as a rule on the network. Also, it would cause a hard fork. * Implementations that do not conform with this BIP will have compatibility issues with strictly-compliant wallets. -* Implementations which do adopt this standard will be cross-compatible when choosing multisig addressses. +* Implementations which do adopt this standard will be cross-compatible when choosing multisig addresses. * If a group of users were not entirely compliant, there is the possibility that a participant will derive an address that the others will not recognize as part of the common multisig account. ==Test vectors== |