diff options
| author | Hugo Nguyen <hugh.hn@gmail.com> | 2021-05-07 19:42:44 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-05-07 19:42:44 -0700 |
| commit | 229a60bf8e180f6d78acce111018d261b8327dec (patch) | |
| tree | 74613f222f93cce098125eb28618514a8970851f | |
| parent | f13cd8dde9e67003fcc952de02d0b63c4db5bbac (diff) | |
| download | bips-229a60bf8e180f6d78acce111018d261b8327dec.tar.xz | |
update Compatibility section
| -rw-r--r-- | bip-hugonguyen-bsms.mediawiki | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/bip-hugonguyen-bsms.mediawiki b/bip-hugonguyen-bsms.mediawiki index 8153ae6..5d9ef85 100644 --- a/bip-hugonguyen-bsms.mediawiki +++ b/bip-hugonguyen-bsms.mediawiki @@ -185,7 +185,9 @@ For signers that use QR codes to transmit data, key and descriptor records can b Also refer to [https://github.com/BlockchainCommons/Research/blob/master/papers/bcr-2020-015-account.md UR Type Definition for BIP44 Accounts] and [https://github.com/BlockchainCommons/Research/blob/master/papers/bcr-2020-010-output-desc.md UR Type Definition for Bitcoin Output Descriptors] for more details. ==Compatibility== -BSMS is opt-in, meaning existing multisig wallets can continue working as-is, with the caveat that current multisig solutions are full of pitfalls. Some of the problems have been described in the [[#Motivation]] section. +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. To comply with this standard, a Signer must be able to persist the descriptor record in its storage. |