Skip to content
Crypto.world

The Ledger

Draft Multisig Session Protocol would let remote Bitcoin cosigners set up wallets without a coordinator

A draft protocol published for review specifies how remote Bitcoin multisig participants could exchange keys, confirm a wallet and pass partially signed transactions without a central coordinator distributing the wallet descriptor. Its current version is limited to two online participants and has not received cryptographic review.

Draft Multisig Session Protocol would let remote Bitcoin cosigners set up wallets without a coordinator

A draft for remote signers

A draft protocol published for review on Delving Bitcoin on Nov. 21 sets out how remote multisig cosigners could exchange keys, confirm a wallet and approve transactions without a coordinator distributing the wallet descriptor. The author, posting as onedigitmoney, says the current version, v0.1, handles two clients at a time, needs everyone online and has no external cryptographic review.

The post says BIP-129 defines the multisig setup file but no protocol defines how remote cosigners exchange it or partially signed Bitcoin transactions (PSBTs). That exchange usually happens by email, chat or a vendor’s server, it says, which makes the coordinator the only source of the other cosigners’ keys, the substitution problem BitBox described in 2020.

How the draft works

Cosigners share a short code out of band and use it to authenticate ephemeral X25519 keys over a relay the protocol treats as hostile. Each side reveals a nonce it committed to in its hello message, and the two people compare a 12-character string derived from both keys and both nonces, by voice or over a verified messenger; a mismatch aborts with nothing disclosed.

For setup, each participant sends its key to the other, assembles the descriptor itself using a byte-exact function and sends the hash; any mismatch aborts. Before funding, each reads the first address off its signing device and the two compare it. Because no one distributes a descriptor, the post says, there is no coordinator to compromise.

For signing, signers refuse PSBTs that do not spend from a wallet both parties hold, sign SIGHASH_ALL only, and approve destinations, amounts and the fee on the device.

Limits and open questions

Because v0.1 handles two clients at a time, setup makes two-key wallets; signing works for any wallet both parties hold, so two cosigners of a 2-of-3 wallet made elsewhere can sign together. The author lists no external cryptographic review and no post-quantum protection. An external design review of the previous draft was received and closed on Nov. 18, and this revision came out of it. The author’s own browser app, Keylay, does not yet conform to the draft.

The author asks for review of two constructions. The first is the short authentication string: the October draft hashed the session keys with nothing committed, so an attacker on the path who held the code could search for a collision at about 2^30 work per side. The current draft commits to a fresh nonce in the hello message and reveals it afterwards; the author believes the bound is about 2^-59 per session with no offline work, and asks whether the two-party argument is sound and what a group profile must add for n parties.

The second is the join, which is not a password-authenticated key exchange. It authenticates with an HMAC under a PBKDF2-stretched code, so the channel identifier and every hello message authentication code are offline oracles on the code. For a generated 10-character code, about 49.5 bits, the margin is large, the post says, but for typed codes it is not. The proposed fix hashes only a short public rendezvous segment into the channel identifier and uses a separate secret segment as the CPace password; the author asks whether that removes offline guessing and what the public segment might reveal. The author also invites pushback on the n(n−1) key messages that symmetric assembly requires, saying they have not seen it done for BSMS-style setup.

Sources

  1. Original source Delving Bitcoin delvingbitcoin.org

Related stories

Explore

More articles