summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorHugo Nguyen <hugh.hn@gmail.com>2021-04-19 09:48:59 -0700
committerGitHub <noreply@github.com>2021-04-19 09:48:59 -0700
commit3eb481c5519597584fb7a00203d81a6dce41a709 (patch)
tree6e1ccd30c9fc62c5a4266f379ff05314aefd4486
parent9771c5e2a8a04a68499604d8d2c2f8ac7e8594b4 (diff)
downloadbips-3eb481c5519597584fb7a00203d81a6dce41a709.tar.xz
minor edit
-rw-r--r--bip-hugonguyen-bsms.mediawiki34
1 files changed, 17 insertions, 17 deletions
diff --git a/bip-hugonguyen-bsms.mediawiki b/bip-hugonguyen-bsms.mediawiki
index cf2e9c9..afa4f47 100644
--- a/bip-hugonguyen-bsms.mediawiki
+++ b/bip-hugonguyen-bsms.mediawiki
@@ -158,6 +158,23 @@ Whereas:
The <tt>MAC</tt> is to be sent along with the key and descriptor record, as specified above. Because it is a <tt>MAC</tt> over the entire plaintext, this is essentially an [https://en.wikipedia.org/wiki/Authenticated_encryption#Encrypt-and-MAC_(E&M) Encrypt-and-MAC] form of authenticated encryption.
+===Descriptor Template===
+The output descriptor language only supports one-dimensional lists. This proposal introduces a descriptor template to represent multi-dimensional lists:
+
+<tt>XPUB/**</tt>
+
+Whereas <tt>**</tt> can be replaced by any number of derivation paths.
+
+If there is a descriptor template in the descriptor record, Signers should expand the template into concrete descriptors by using the derivations paths provided in the record.
+
+For example, the following template and derivation paths:
+* <tt>wsh(sortedmulti(2,XPUB1/**,XPUB2/**))</tt>
+* <tt>/0/*,/1/*</tt>
+
+Should translate to two concrete descriptors:
+* <tt>wsh(sortedmulti(2,XPUB1/0/*,XPUB2/0/*))</tt>
+* <tt>wsh(sortedmulti(2,XPUB1/1/*,XPUB2/1/*))</tt>
+
==QR Codes==
For signers that use QR codes to transmit data, key and descriptor records can be converted to QR codes, following [https://github.com/BlockchainCommons/Research/blob/master/papers/bcr-2020-005-ur.md the BCR standard].
@@ -176,23 +193,6 @@ Encryption helps improve the privacy of the wallet by avoiding sharing keys and
If the parties wish to have stronger privacy, it is recommended to use a higher number of bits for the <tt>TOKEN</tt>, and to completely erase knowledge of the <tt>TOKEN</tt> after the multisig wallet has been set up.
-==Descriptor Template==
-The output descriptor language only supports one-dimensional lists. This proposal introduces a descriptor template to represent multi-dimensional lists:
-
-<tt>XPUB/**</tt>
-
-Whereas <tt>**</tt> can be replaced by any number of derivation paths.
-
-If there is a descriptor template in the descriptor record, Signers should expand the template into concrete descriptors by using the derivations paths provided in the record.
-
-For example, the following template and derivation paths:
-* <tt>wsh(sortedmulti(2,XPUB1/**,XPUB2/**))</tt>
-* <tt>/0/*,/1/*</tt>
-
-Should translate to two concrete descriptors:
-* <tt>wsh(sortedmulti(2,XPUB1/0/*,XPUB2/0/*))</tt>
-* <tt>wsh(sortedmulti(2,XPUB1/1/*,XPUB2/1/*))</tt>
-
==Test Vectors==
===Mode: <tt>NO_ENCRYPTION</tt>===