From 83aa04776d38e18f03cd766102cfcefb5b244c9f Mon Sep 17 00:00:00 2001
From: Hugo Nguyen <hugh.hn@gmail.com>
Date: Tue, 4 May 2021 21:35:05 -0700
Subject: update Compatibility section

---
 bip-hugonguyen-bsms.mediawiki | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/bip-hugonguyen-bsms.mediawiki b/bip-hugonguyen-bsms.mediawiki
index 11107b4..a41900d 100644
--- a/bip-hugonguyen-bsms.mediawiki
+++ b/bip-hugonguyen-bsms.mediawiki
@@ -2,7 +2,11 @@
   BIP: To be determined
   Layer: Applications
   Title: Bitcoin Secure Multisig Setup (BSMS)
-  Author: Hugo Nguyen <hugo at nunchuk.io>, Peter Gray <peter at coinkite.com>, Marko Bencun <marko at shiftcrypto.ch>, Aaron Chen <aarondongchen at gmail.com>, Rodolfo Novak <rodolfo at coinkite.com>
+  Author: Hugo Nguyen <hugo at nunchuk.io>
+          Peter Gray <peter at coinkite.com>
+          Marko Bencun <marko at shiftcrypto.ch>
+          Aaron Chen <aarondongchen at gmail.com>
+          Rodolfo Novak <rodolfo at coinkite.com>
   Comments-Summary: No comments yet.
   Comments-URI:
   Status: Proposed
@@ -183,6 +187,8 @@ Also refer to [https://github.com/BlockchainCommons/Research/blob/master/papers/
 ==Compatibility==
 To comply with this standard, a Signer must be able to persist the descriptor record in its storage. 
 
+Existing multisig wallets should delay upgrading to the BSMS scheme until all participating Signers in the multisig wallet have added support for BSMS.
+
 ==Security==
 
 This proposal introduces two layers of protection. The first one is a temporary, secret <tt>TOKEN</tt>. The second one is the confirmation of the wallet's first address.
-- 
cgit v1.2.3