summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorHugo Nguyen <hugh.hn@gmail.com>2021-04-28 08:25:43 -0700
committerGitHub <noreply@github.com>2021-04-28 08:25:43 -0700
commit3f050db64e7716a62993e6ff9fae7b0768b217f8 (patch)
treea6ed77515bcc7035f2e75d45f9c200c724a6c017
parentcf00b456798eedb829f2d247eaf974b9668f5376 (diff)
downloadbips-3f050db64e7716a62993e6ff9fae7b0768b217f8.tar.xz
add Compatibility section
-rw-r--r--bip-hugonguyen-bsms.mediawiki3
1 files changed, 3 insertions, 0 deletions
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.