Return-Path: Received: from whitealder.osuosl.org (smtp1.osuosl.org [140.211.166.138]) by lists.linuxfoundation.org (Postfix) with ESMTP id 17679C013A for ; Mon, 15 Feb 2021 09:11:25 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by whitealder.osuosl.org (Postfix) with ESMTP id 03D5386847 for ; Mon, 15 Feb 2021 09:11:25 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from whitealder.osuosl.org ([127.0.0.1]) by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QoeTXeYiEAcr for ; Mon, 15 Feb 2021 09:11:22 +0000 (UTC) X-Greylist: delayed 00:20:57 by SQLgrey-1.7.6 Received: from mail-pj1-f42.google.com (mail-pj1-f42.google.com [209.85.216.42]) by whitealder.osuosl.org (Postfix) with ESMTPS id A2EBA867B7 for ; Mon, 15 Feb 2021 09:11:22 +0000 (UTC) Received: by mail-pj1-f42.google.com with SMTP id nm1so3351549pjb.3 for ; Mon, 15 Feb 2021 01:11:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nunchuk-io.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=VyLdnWo/PiD7GgqWMF1n1w+WSP7x9T/ce8X75PJPsPA=; b=NWLPSlFHjY5LNqHabnVIupRooNujkWHH20i8gtNSNOaP4cY7B/Gbc51dISILlmbv8f 6q7vyL/tzD5z+lCxolS0vf4N7wa+yQpHDJYD3T70lv5VX430Lo3hTTbg9r338SfkyW7h vX6WcYrnZh+y0/+fRQDMT4RmnEYMXM5fswq7N5L6L1LnbiuDtbsp/h43j0rMhJG8NRQU Y+3uUj2hU2h2I7A9QwdFnv8Sc0GPOSoAE1sN+hrEYuIsUo/Tvyq0e4dmoZghmEy7RY0/ smRoqKfqbMUB87rgh2waf84IA1rwUlHblBDq7Yu5PFiBr6pxnBvnZwbKetWa8YpWKEgZ 0JGA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=VyLdnWo/PiD7GgqWMF1n1w+WSP7x9T/ce8X75PJPsPA=; b=mqEUm6IClRsjlMHTLPV/dbpwqO3gF1xcIGJJuOgDhxxveooMGBY1Tcp4CguJYV2GQR HvLj6PLKKBOEPWuytZo3ZkrqOzY6lLGdiaMydBovwk9OFC4niWiK+UzjU8dZGJklAyfb fi31IBMBdkPA2UXXVtBu4aBzA60J1vm7+78B+8Jz+n3u8X9R0kXoxqyslc9ThwNtOLPo aW+NuMSBG6Ray+0o52W0Uuc+ulY+98qDqYK/MXyHVMOT4ZYszmrPRbrNegVExWDCrEfa D+EaTmUC0BqmLkXv3ThDd2nL3fjm4uO/BgW3aQNfutLHdwsnm3EGa5+HNHmFmsoxGFrB di7w== X-Gm-Message-State: AOAM530H6SyCSrlpXNVWJ3VzJWc2TxBLRLLRU6sV2Tr7oF8ptmA1T1CH omrKalChx6/b5EAiOfSztu5tBlCFMNeOpF8Kr6KueOtMuKPCr6ZiLNiP7A== X-Google-Smtp-Source: ABdhPJxg1a6ceatUGwtrqYFYbd6EJ42CNsR7/7HnkTtr+JdALw0ql0yUEFIgjOWUgQmjOisTuIJeAz3i247Sg3hU7PU= X-Received: by 2002:a1f:b60c:: with SMTP id g12mr7583624vkf.15.1613378670873; Mon, 15 Feb 2021 00:44:30 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Hugo Nguyen Date: Mon, 15 Feb 2021 00:44:19 -0800 Message-ID: To: Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="00000000000090de7105bb5bfebe" X-Mailman-Approved-At: Mon, 15 Feb 2021 09:13:31 +0000 Subject: Re: [bitcoin-dev] Proposal: Bitcoin Secure Multisig Setup X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Feb 2021 09:11:25 -0000 --00000000000090de7105bb5bfebe Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi all, I have updated the proposal based on further feedback. The new spec is included at the bottom. I have also created a public Github PR to make it easier to comment on the text of the spec itself: https://github.com/nunchuk-io/bips/pull/1 . Could someone please let me know what else needs to be done before a BIP number can be assigned? =3D=3D=3D Quick summary of changes from last update =3D=3D=3D 1. Define encryption modes # NO_ENCRYPTION: Encryption is disabled. # STANDARD : the TOKEN is a 64-bit nonce. # EXTENDED : the TOKEN is a 128-bit nonce. 2. Define signature algorithm Follow BIP-0322, legacy format allowed. 3. Multiple TOKENs (optional) Also add an option where the Coordinator can choose to use one common TOKEN for all Signers, or use one per Signer. =3D=3D=3D End of summary =3D=3D=3D Cheers, Hugo 
  BIP: To be determined
  Layer: Applications
  Title: Bitcoin Secure Multisig Setup (BSMS)
  Author: Hugo Nguyen , Peter Gray , Marko Bencun , Pavol Rusnak <
stick@satoshilabs.com>, Aaron Chen , Rodolfo
Novak 
  Comments-Summary: No comments yet.
  Comments-URI:
  Status: Proposed
  Type: Standards Track
  Created: 2020-11-10
  License: BSD-2-Clause
=3D=3DIntroduction=3D=3D =3D=3D=3DAbstract=3D=3D=3D This document proposes a mechanism to set up multisig wallets securely. =3D=3D=3DCopyright=3D=3D=3D This BIP is licensed under the 2-clause BSD license. =3D=3D=3DMotivation=3D=3D=3D The Bitcoin multisig experience has been greatly streamlined under [ https://github.com/bitcoin/bips/blob/master/bip-0174.mediawiki BIP-0174 (Partially Signed Bitcoin Transaction)]. However, what is still missing is a standardized process for setting up multisig wallets securely across different vendors. There are a number of concerns when it comes to setting up a multisig wallet: # Whether the multisig configuration, such as Signer membership, script type, derivation paths and number of signatures required, is correct and not tampered with. # Whether Signer persists the multisig configuration in their respective storage, and under what format. # Whether Signer's storage is tamper-proof. # Whether Signer subsequently uses the multisig configuration to generate and verify receive and change addresses. An attacker who can modify the multisig configuration can steal or hold funds to ransom by duping the user into sending funds to the wrong address. This proposal seeks to address concerns #1 and #2: to mitigate the risk of tampering during the initial setup phase, and to define an interoperable multisig configuration format. Concerns #3 and #4 should be handled by Signers and is out of scope of this proposal. =3D=3DSpecification=3D=3D =3D=3D=3DPrerequisites=3D=3D=3D This proposal assumes the parties in the multisig support [ https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki BIP-0032], [ https://github.com/bitcoin/bitcoin/blob/master/doc/descriptors.md the descriptor language] and encryption. =3D=3D=3DRoles=3D=3D=3D =3D=3D=3D=3DCoordinator=3D=3D=3D=3D The Coordinator initiates the multisig setup. The Coordinator determines what type of multisig is used and the exact policy script. If encryption is enabled, the Coordinator also distributes a shared secret or shared secrets to the parties involved for secure communication. The Coordinator gathers information from the Signers to generate a descriptor record. The Coordinator distributes the descriptor record back to the Signers. =3D=3D=3D=3DSigner=3D=3D=3D=3D The Signer is a participating member in the multisig. Its responsibilities include providing its key record -- which contains an Extended Public Key (XPUB) -- to the Coordinator, verifying that its XPUB is included in the descriptor record and persisting the descriptor record in its storage. =3D=3D=3DSetup Process=3D=3D=3D =3D=3D=3D=3DRound 1=3D=3D=3D=3D =3D=3D=3D=3D=3DCoordinator=3D=3D=3D=3D=3D * The Coordinator creates a multisig wallet creation session. The Coordinator constructs the multisig script and its policy parameters, such as the total number of signers and the required number of signatures (M and N). * The session should expire after some time period determined by the Coordinator, e.g., 24 hours. * If encryption is enabled, the Coordinator distributes a secret TOKEN to each Signer over a secure channel. The Signer can use the TOKEN to derive an ENCRYPTION_KEY. Refer to the Encryption section below for details on the TOKEN, the key derivation function and the encryption scheme. Depending on the use case, the Coordinator can decide whether to share one common TOKEN for all Signers, or to have one per Signer. * If encryption is disabled, TOKEN is set to 0, and all the encryption/decryption steps below can be skipped. =3D=3D=3D=3D=3DSigner=3D=3D=3D=3D=3D * The Signer initiates a new secure multisig setup session by setting the TOKEN. The Signer derives an ENCRYPTION_KEY from the TOKEN. The Signer can keep the session open until a different value for the TOKEN is set. * The Signer generates a key record by prompting the user for a multisig derivation path and retrieves the XPUB at that derivation path. Optionally, the Signer can choose a path on behalf of the user. If the Signer chooses the path, it should try to avoid reusing XPUBs for different wallets. * The first line in the record must be the TOKEN. The second line must be the KEY. The KEY is an XPUB plus its key origin information, written in the descriptor-defined format, i.e.: [{master key fingerprint}/{derivation path}]{XPUB}. The third line must be a SIG, whereas SIG is the signature generated by using the private key associated with the XPUB to sign the first two lines. The signature should follow [ https://github.com/bitcoin/bips/blob/master/bip-0322.mediawiki BIP-0322], legacy format accepted. Finally, the Signer encrypts the entire record with ENCRYPTION_KEY. =3D=3D=3D=3DRound 2=3D=3D=3D=3D =3D=3D=3D=3D=3DCoordinator=3D=3D=3D=3D=3D * The Coordinator gathers key records from all participating Signers. Abort the setup if the wallet setup session has expired. * For each key record, the Coordinator decrypts it using ENCRYPTION_KEY. The Coordinator verifies that the included SIG is valid given the KEY. * If all key records look good, the Coordinator fills in all necessary information to generate a descriptor record, which is simply the descriptor string plus a CHECKSUM, all in one line. The CHECKSUM has [https://github.com/bitcoin/bitcoin/blob/master/doc/descriptors.md#checksum= s BECH32 encoding]. * The Coordinator encrypts this descriptor record with ENCRYPTION_KEY. * The Coordinator sends the encrypted descriptor record to all participating Signers. =3D=3D=3D=3D=3DSigner=3D=3D=3D=3D=3D * The Signer imports the descriptor record, decrypts it using the ENCRYPTION_KEY derived from the open session. * The Signer calculates and verifies the descriptor=E2=80=99s CHECKSUM<= /tt>. Abort the setup if the CHECKSUM is incorrect. * The Signer checks whether one of the KEYs in the descriptor belongs to it, using path and fingerprint information included in the descriptor. The check must perform an exact match on the KEYs, and not using shortcuts such as matching fingerprints (which is trivial to spoof). Abort the setup if it doesn=E2=80=99t detect its own KEY. * For confirmation, the Signer must display to the user the CHECKSUM, plus other configurations, such as M and N. The total number of Signers, N, is important to prevent a KEY insertion attack. All participating Signers should be able to display the same confirmation. * If all checks pass, the Signer persists the descriptor record in its storage. * The Signer can choose to further restrict post-XPUB derivation paths, such as to those defined in [ https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki BIP-0044]. * The Signer should subsequently use the descriptor to generate and verify receive and change addresses. This completes the setup. =3D=3D=3DEncryption=3D=3D=3D =3D=3D=3D=3DThe Token=3D=3D=3D=3D We define three modes of encryption. # NO_ENCRYPTION : the TOKEN is set to 0. Encryption is disabled. # STANDARD : the TOKEN is a 64-bit nonce. # EXTENDED : the TOKEN is a 128-bit nonce. The TOKEN can be converted to one of these formats: * A mnemonic phrase using [ https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki BIP-0039] word list (6 words in STANDARD mode, 12 words in EXTENDED mode) * A decimal number (20 digits in STANDARD mode, 40 digits in EXTENDED mode) * A QR code * Other formats The flexibility in the data format allows each Signer to customize the User Experience based on its respective capabilities. =3D=3D=3D=3DKey Derivation=3D=3D=3D=3D The key derivation function is [https://tools.ietf.org/html/rfc2898 PBKDF2], with PRF =3D SHA512. Specifically: DK =3D PBKDF2(PRF, Password, Salt, c, dkLen) Whereas: * PRF =3D SHA512 * Password =3D "No SPOF" * Salt =3D TOKEN * c =3D 2048 * dkLen =3D 256 * DK =3D Derived ENCRYPTION_KEY =3D=3D=3D=3DEncryption Scheme=3D=3D=3D=3D The encryption scheme is [https://tools.ietf.org/html/rfc3686 AES, CTR mode]. =3D=3DQR Codes=3D=3D 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-0= 05-ur.md the BCR standard]. Also refer to [ https://github.com/BlockchainCommons/Research/blob/master/papers/bcr-2020-0= 15-account.md UR Type Definition for BIP44 Accounts] and [ https://github.com/BlockchainCommons/Research/blob/master/papers/bcr-2020-0= 10-output-desc.md UR Type Definition for Bitcoin Output Descriptors] for more details. =3D=3DSecurity=3D=3D This proposal introduces two layers of protection. The first one is a temporary, secret token, used to encrypt the two rounds of communication between the Signer and the Coordinator. The second one is through the descriptor checksum and visual inspection of the descriptor itself. The token is only needed during the setup phase, and can be safely thrown away afterwards. The token does not guarantee that the Signer membership set is not modified, since that depends on the overall security of all parties in the setup, but it can make it significantly harder for an attacker to do so. There are three ways an attacker can modify the membership set: by changing an existing member, by removing an existing member, or by adding a new member. For the first two methods, one of the Signers will be able to detect that its membership has been changed or removed, and reject the final descriptor. Thus, it is vital that all participating Signers check that their membership is intact in the descriptor. Even one Signer failing to check for its membership means that the setup could be compromised. For the third type of attack, the descriptor checksum and visual inspection of the descriptor itself are the only way to guard against malicious members from being inserted into the set. =3D=3DAcknowledgement=3D=3D Special thanks to Dmitry Petukhov, Christopher Allen, Craig Raw and others for their feedback on the specification. =3D=3DReferences=3D=3D Original mailing list thread: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-February/01838= 5.html --00000000000090de7105bb5bfebe Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all,
I have updated the proposal based on furth= er feedback. The new spec is included at the bottom.

I have also created a public Github PR to make it easier to comment on t= he text of the spec itself:=C2=A0https://github.com/nunchuk-io/bips/pull/1 .

Could so= meone please let me know what else needs to be done before a BIP number can= be assigned?


=3D=3D=3D Quick summary of changes from last updat= e =3D=3D=3D

1. Define encryption modes

# NO_ENCRYPTION: Encry= ption is disabled.
# STANDARD : the TOKEN is a 64-bit nonce.
# EXTEND= ED : the TOKEN is a 128-bit nonce.

2. Define signature algorithm
=
Follow BIP-0322, legacy format allowed.

3. Multiple TOKENs (opti= onal)

Also add an option where the Coordinator can choose to use one= common TOKEN for all Signers, or use one per Signer.

=3D=3D=3D End = of summary =3D=3D=3D


Cheers,
Hugo


<pre>
=C2=A0 BIP: To be determ= ined
=C2=A0 Layer: Applications
=C2=A0 Title: Bitcoin Secure Multisig= Setup (BSMS)
=C2=A0 Author: Hugo Nguyen <hugo at nunchuk.io>, Peter Gray <peter at coinkite.com>, Marko Bencun <marko at shiftcrypto.ch>, Pavol Rusnak <stick@satoshilabs.com>, Aaron Chen <aar= ondongchen at gmail.com>, Rodolfo Novak= <rodolfo at coinkite.com>
=C2= =A0 Comments-Summary: No comments yet.
=C2=A0 Comments-URI:
=C2=A0 St= atus: Proposed
=C2=A0 Type: Standards Track
=C2=A0 Created: 2020-11-1= 0
=C2=A0 License: BSD-2-Clause
</pre>

=3D=3DIntroduction= =3D=3D

=3D=3D=3DAbstract=3D=3D=3D

This document proposes a me= chanism to set up multisig wallets securely.

=3D=3D=3DCopyright=3D= =3D=3D

This BIP is licensed under the 2-clause BSD license.

= =3D=3D=3DMotivation=3D=3D=3D

The Bitcoin multisig experience has bee= n greatly streamlined under [https://github.com/bitcoin/bips/blob/master/bi= p-0174.mediawiki BIP-0174
(Partially Signed Bitcoin Transaction)]. H= owever, what is still missing is a standardized process for setting up mult= isig wallets securely across different vendors.

There are a number o= f concerns when it comes to setting up a multisig wallet:

# Whether = the multisig configuration, such as Signer membership, script type, derivat= ion paths and number of signatures required, is correct and not tampered wi= th.
# Whether Signer persists the multisig configuration in their respec= tive storage, and under what format.
# Whether Signer's storage is t= amper-proof.
# Whether Signer subsequently uses the multisig configurati= on to generate and verify receive and change addresses.

An attacker = who can modify the multisig configuration can steal or hold funds to ransom= by duping the user into sending funds to the wrong address.

This pr= oposal seeks to address concerns #1 and #2: to mitigate the risk of tamperi= ng during the initial setup phase, and to define an interoperable multisig = configuration format.

Concerns #3 and #4 should be handled by Signer= s and is out of scope of this proposal.

=3D=3DSpecification=3D=3D
=3D=3D=3DPrerequisites=3D=3D=3D
This proposal assumes the parties i= n the multisig support [https://github.com/bitcoin/bips/blob/master/bip-003= 2.mediawiki BIP-0032], [https://github.com/bitcoin/bitcoin/blob/mast= er/doc/descriptors.md the descriptor language] and encryption.

= =3D=3D=3DRoles=3D=3D=3D
=3D=3D=3D=3DCoordinator=3D=3D=3D=3D

The C= oordinator initiates the multisig setup. The Coordinator determines what ty= pe of multisig is used and the exact policy script. If encryption is enable= d, the Coordinator also distributes a shared secret or shared secrets to th= e parties involved for secure communication. The Coordinator gathers inform= ation from the Signers to generate a descriptor record. The Coordinator dis= tributes the descriptor record back to the Signers.

=3D=3D=3D=3DSign= er=3D=3D=3D=3D

The Signer is a participating member in the multisig.= Its responsibilities include providing its key record -- which contains an= Extended Public Key (XPUB) -- to the Coordinator, verifying that its XPUB = is included in the descriptor record and persisting the descriptor record i= n its storage.

=3D=3D=3DSetup Process=3D=3D=3D

=3D=3D=3D=3DRo= und 1=3D=3D=3D=3D

=3D=3D=3D=3D=3DCoordinator=3D=3D=3D=3D=3D

*= The Coordinator creates a multisig wallet creation session. The Coordinato= r constructs the multisig script and its policy parameters, such as the tot= al number of signers and the required number of signatures (<tt>M<= /tt> and <tt>N</tt>).
* The session should expire after s= ome time period determined by the Coordinator, e.g., 24 hours.
* If encr= yption is enabled, the Coordinator distributes a secret <tt>TOKEN<= /tt> to each Signer over a secure channel. The Signer can use the <tt= >TOKEN</tt> to derive an <tt>ENCRYPTION_KEY</tt>. Refe= r to the Encryption section below for details on the <tt>TOKEN</tt= >, the key derivation function and the encryption scheme. Depending on t= he use case, the Coordinator can decide whether to share one common <tt&= gt;TOKEN</tt> for all Signers, or to have one per Signer.
* If enc= ryption is disabled, <tt>TOKEN</tt> is set to <tt>0</t= t>, and all the encryption/decryption steps below can be skipped.
=3D=3D=3D=3D=3DSigner=3D=3D=3D=3D=3D

* The Signer initiates a new s= ecure multisig setup session by setting the <tt>TOKEN</tt>. The= Signer derives an <tt>ENCRYPTION_KEY</tt> from the <tt>T= OKEN</tt>. The Signer can keep the session open until a different val= ue for the <tt>TOKEN</tt> is set.
* The Signer generates a k= ey record by prompting the user for a multisig derivation path and retrieve= s the XPUB at that derivation path. Optionally, the Signer can choose a pat= h on behalf of the user. If the Signer chooses the path, it should try to a= void reusing XPUBs for different wallets.
* The first line in the record= must be the <tt>TOKEN</tt>. The second line must be the <tt= >KEY</tt>. The <tt>KEY</tt> is an XPUB plus its key or= igin information, written in the descriptor-defined format, i.e.: <tt>= ;[{master key fingerprint}/{derivation path}]{XPUB}</tt>. The third l= ine must be a <tt>SIG</tt>, whereas <tt>SIG</tt> is= the signature generated by using the private key associated with the XPUB = to sign the first two lines.=C2=A0 The signature should follow [https://git= hub.com/bitcoin/bips/blob/master/bip-0322.mediawiki BIP-0322], legacy f= ormat accepted. Finally, the Signer encrypts the entire record with <tt&= gt;ENCRYPTION_KEY</tt>.

=3D=3D=3D=3DRound 2=3D=3D=3D=3D
=3D=3D=3D=3D=3DCoordinator=3D=3D=3D=3D=3D

* The Coordinator gathers= key records from all participating Signers. Abort the setup if the wallet = setup session has expired.
* For each key record, the Coordinator decryp= ts it using <tt>ENCRYPTION_KEY</tt>. The Coordinator verifies t= hat the included <tt>SIG</tt> is valid given the <tt>KEY&= lt;/tt>.
* If all key records look good, the Coordinator fills in all= necessary information to generate a descriptor record, which is simply the= descriptor string plus a <tt>CHECKSUM</tt>, all in one line. T= he <tt>CHECKSUM</tt> has [https://github.com/bitco= in/bitcoin/blob/master/doc/descriptors.md#checksums BECH32 encoding].* The Coordinator encrypts this descriptor record with <tt>ENCRYPTI= ON_KEY</tt>.
* The Coordinator sends the encrypted descriptor reco= rd to all participating Signers.

=3D=3D=3D=3D=3DSigner=3D=3D=3D=3D= =3D

* The Signer imports the descriptor record, decrypts it using th= e <tt>ENCRYPTION_KEY</tt> derived from the open session.
* T= he Signer calculates and verifies the descriptor=E2=80=99s <tt>CHECKS= UM</tt>. Abort the setup if the <tt>CHECKSUM</tt> is inco= rrect.
* The Signer checks whether one of the <tt>KEY</tt>s = in the descriptor belongs to it, using path and fingerprint information inc= luded in the descriptor. The check must perform an exact match on the <t= t>KEY</tt>s, and not using shortcuts such as matching fingerprints= (which is trivial to spoof). Abort the setup if it doesn=E2=80=99t detect = its own <tt>KEY</tt>.
* For confirmation, the Signer must di= splay to the user the <tt>CHECKSUM</tt>, plus other configurati= ons, such as <tt>M</tt> and <tt>N</tt>. The total n= umber of Signers, <tt>N</tt>, is important to prevent a <tt&= gt;KEY</tt> insertion attack. All participating Signers should be abl= e to display the same confirmation.
* If all checks pass, the Signer per= sists the descriptor record in its storage.
* The Signer can choose to f= urther restrict post-XPUB derivation paths, such as to those defined in [ht= tps://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki BIP-0044].=
* The Signer should subsequently use the descriptor to generate and ver= ify receive and change addresses.

This completes the setup.

= =3D=3D=3DEncryption=3D=3D=3D

=3D=3D=3D=3DThe Token=3D=3D=3D=3D
We= define three modes of encryption.

# <tt>NO_ENCRYPTION</tt&= gt; : the <tt>TOKEN</tt> is set to <tt>0</tt>. Encr= yption is disabled.
# <tt>STANDARD</tt> : the <tt>TOKE= N</tt> is a 64-bit nonce.
# <tt>EXTENDED</tt> : the &l= t;tt>TOKEN</tt> is a 128-bit nonce.

The <tt>TOKEN<= /tt> can be converted to one of these formats:
* A mnemonic phrase us= ing [https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki BIP= -0039] word list (6 words in <tt>STANDARD</tt> mode, 12 words i= n <tt>EXTENDED</tt> mode)
* A decimal number (20 digits in &= lt;tt>STANDARD</tt> mode, 40 digits in <tt>EXTENDED</tt&g= t; mode)
* A QR code
* Other formats

The flexibility in the da= ta format allows each Signer to customize the User Experience based on its = respective capabilities.

=3D=3D=3D=3DKey Derivation=3D=3D=3D=3D
T= he key derivation function is [https://tools.ietf.org/html/rfc2898 PBKDF2], with PRF =3D SHA512. S= pecifically:

<tt>DK =3D PBKDF2(PRF, Password, Salt, c, dkLen)&= lt;/tt>

Whereas:

* PRF =3D <tt>SHA512</tt>
= * Password =3D <tt>"No SPOF"</tt>
* Salt =3D <t= t>TOKEN</tt>
* c =3D <tt>2048</tt>
* dkLen =3D &= lt;tt>256</tt>
* DK =3D Derived <tt>ENCRYPTION_KEY</tt= >

=3D=3D=3D=3DEncryption Scheme=3D=3D=3D=3D
The encryption sch= eme is [https://tools.ietf.= org/html/rfc3686 AES, CTR mode].

=3D=3DQR Codes=3D=3D
For sig= ners that use QR codes to transmit data, key and descriptor records can be = converted to QR codes, following [https://github.com/B= lockchainCommons/Research/blob/master/papers/bcr-2020-005-ur.md the BCR= standard].

Also refer to [https://github.= com/BlockchainCommons/Research/blob/master/papers/bcr-2020-015-account.md UR Type Definition for BIP44 Accounts] and [https://lists.linuxfoundation.org/pipermail/= bitcoin-dev/2021-February/018385.html

=C2=A0
--00000000000090de7105bb5bfebe--