mirror of
https://github.com/bitcoin/bips.git
synced 2026-02-23 15:38:22 +00:00
docs: fix spelling (#1117)
Co-authored-by: Mark "Murch" Erhardt <murch@murch.one>
This commit is contained in:
@@ -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==
|
||||
|
||||
Reference in New Issue
Block a user