minor edit

This commit is contained in:
Hugo Nguyen 2021-05-11 03:36:32 -07:00 committed by GitHub
parent 229a60bf8e
commit 47847fe874
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -187,13 +187,11 @@ Also refer to [https://github.com/BlockchainCommons/Research/blob/master/papers/
==Compatibility==
This specification is not backwards compatible with existing multisig implementations.
BSMS is opt-in, meaning existing multisig implementations can continue working as-is, with the caveat that they are full of pitfalls. Some of the problems have been described in the [[#Motivation]] section.
BSMS is opt-in, meaning existing multisig implementations can continue working as-is, with the caveat that they are likely to have various pitfalls. Some of the problems with existing solutions have been described in the [[#Motivation]] section.
To comply with this standard, a Signer must be able to persist the descriptor record in its storage.
Once a Signer has implemented BSMS, the user can create new multisig wallets using BSMS or migrate existing ones to BSMS.
Existing multisig wallets should delay upgrading to BSMS until all participating Signers have implemented BSMS.
To use BSMS for a multisig wallet, the user should wait until all participating Signers in the multisig have implemented BSMS.
==Security==