Author: Salvatore Ingala 2021-04-12 15:03:12
Published on: 2021-04-12T15:03:12+00:00
The discussion revolves around the distinction between a "Signer" and a "Signing device" in a multisig setup. While a "Signer" is defined as a participating member, who is likely using both a hardware wallet and some BSMS-friendly software wallet, the "Signing device" is the hardware wallet. The flow for wallet registration includes the desktop wallet requesting the HWW to register a new multisig wallet, the HWW validating and verifying it with the user, and returning a wallet ID and signature. The desktop wallet stores the full wallet description, ID, and signature, which could be backed up elsewhere. The only caveat is that the script registration is never revocable if a signing key derived from the seed is used. There is a disagreement on going stateless in a multisig setup, with one side arguing that any Signer in the contract must know who the other co-Signers are at all times, while the other side argues that external software only cares about storing certain data and sending it back later. Storing xpubs/descriptors in the desktop software that interacts with the HWW is already common practice and necessary for using any watch-only wallet. The stateful/stateless characteristic of a hardware wallet does not really affect the ability to participate in the BSMS ceremony, whose Signers should indeed be stateful.
Updated on: 2023-06-14T17:34:50.112503+00:00