From 3f050db64e7716a62993e6ff9fae7b0768b217f8 Mon Sep 17 00:00:00 2001
From: Hugo Nguyen <hugh.hn@gmail.com>
Date: Wed, 28 Apr 2021 08:25:43 -0700
Subject: add Compatibility section

---
 bip-hugonguyen-bsms.mediawiki | 3 +++
 1 file changed, 3 insertions(+)

(limited to 'bip-hugonguyen-bsms.mediawiki')

diff --git a/bip-hugonguyen-bsms.mediawiki b/bip-hugonguyen-bsms.mediawiki
index a5225f0..dc04d5e 100644
--- a/bip-hugonguyen-bsms.mediawiki
+++ b/bip-hugonguyen-bsms.mediawiki
@@ -180,6 +180,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==
+To comply with this standard, a Signer must be able to persist the descriptor record in its storage. 
+
 ==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

