📅 Original date posted:2014-03-10 📝 Original message:Multisig is orthogonal to ...

Gavin Andresen [ARCHIVE] /

npub1s4l…44kw

2023-06-07 15:15:04

in reply to nevent1q…fdam

📅 Original date posted:2014-03-10
📝 Original message:Multisig is orthogonal to the payment protocol (but payment protocol is
needed first).

There need to be protocols for:

a) Establishing multisig wallets of various sorts. See:
https://moqups.com/gavinandresen/no8mzUDB/
https://moqups.com/gavinandresen/no8mzUDB/p:ab18547e0
... etc. for a UI mock-up.
There needs to be some protocol so all participants in a multisig wallet
contribute keys (actually, we should just assume everybody uses BIP32 HD
public keys so we get privacy from the start).

Multi-person shared wallets, escrows, and "wallet protection service"
wallets (which might be protected with two-factor authentication) are
different use cases and probably use slightly different protocols (and will
probably need different BIPs eventually).

b) Gathering signatures for a multisig spend. Here is where the payment
protocol is useful; the PaymentRequest message should be passed around so
all participants know what is being paid for, and maybe a partially-signed
Payment message is where the signatures are gathered (or maybe the
signatures are sent separately and one of the participants creates and
submits the Payment and gets the PaymentACK... "to be designed").
See:
https://moqups.com/gavinandresen/no8mzUDB/p:a7e81be96
https://moqups.com/gavinandresen/no8mzUDB/p:af7339204
... for UI mock-up for the multi-person-spend case.

And maybe a protocol for "I don't want to be part of this multisig any more
/ I lost control of my private key don't trust me in this multisig any
more".

On Mon, Mar 10, 2014 at 8:14 PM, Jeff Garzik <jgarzik at bitpay.com> wrote:

> All of that only melds with the payment protocol under an extremely
> expansive definition of "payment." The payment protocol is really
> geared towards a direct one-to-one relationship....

>
>
--
Gavin Andresen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140310/1ce818ae/attachment.html>;

Author Public Key

npub1s4lj77xuzcu7wy04afcr487f0r3za0f8n2775xrpkld2sv639mjqsd44kw

Show more details

Published at

2023-06-07 15:15:04

Kind type

1 Short Text Note

Event JSON

{ "id": "2eae9e8182cd28426f23f08c2f31afb9775e44cb54c1049260712de90e777a9b", "pubkey": "857f2f78dc1639e711f5ea703a9fc978e22ebd279abdea1861b7daa833512ee4", "created_at": 1686150904, "kind": 1, "tags": [ [ "e", "07851d213f227977a351770e7dfc2e7354779fae77670cd215beec4023ffb144", "", "root" ], [ "e", "ec5b5699d6fc2bab766cd752223ea29bef297d7ae0369f8886f6404fa5bc1798", "", "reply" ], [ "p", "b25e10e25d470d9b215521b50da0dfe7a209bec7fedeb53860c3e180ffdc8c11" ] ], "content": "📅 Original date posted:2014-03-10\n📝 Original message:Multisig is orthogonal to the payment protocol (but payment protocol is\nneeded first).\n\nThere need to be protocols for:\n\na) Establishing multisig wallets of various sorts. See:\n https://moqups.com/gavinandresen/no8mzUDB/\n https://moqups.com/gavinandresen/no8mzUDB/p:ab18547e0\n... etc. for a UI mock-up.\n There needs to be some protocol so all participants in a multisig wallet\ncontribute keys (actually, we should just assume everybody uses BIP32 HD\npublic keys so we get privacy from the start).\n\nMulti-person shared wallets, escrows, and \"wallet protection service\"\nwallets (which might be protected with two-factor authentication) are\ndifferent use cases and probably use slightly different protocols (and will\nprobably need different BIPs eventually).\n\n\nb) Gathering signatures for a multisig spend. Here is where the payment\nprotocol is useful; the PaymentRequest message should be passed around so\nall participants know what is being paid for, and maybe a partially-signed\nPayment message is where the signatures are gathered (or maybe the\nsignatures are sent separately and one of the participants creates and\nsubmits the Payment and gets the PaymentACK... \"to be designed\").\n See:\n https://moqups.com/gavinandresen/no8mzUDB/p:a7e81be96\n https://moqups.com/gavinandresen/no8mzUDB/p:af7339204\n... for UI mock-up for the multi-person-spend case.\n\nAnd maybe a protocol for \"I don't want to be part of this multisig any more\n/ I lost control of my private key don't trust me in this multisig any\nmore\".\n\n\n\nOn Mon, Mar 10, 2014 at 8:14 PM, Jeff Garzik \u003cjgarzik at bitpay.com\u003e wrote:\n\n\u003e All of that only melds with the payment protocol under an extremely\n\u003e expansive definition of \"payment.\" The payment protocol is really\n\u003e geared towards a direct one-to-one relationship....\n\n\n\n\u003e\n\u003e\n--\nGavin Andresen\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140310/1ce818ae/attachment.html\u003e", "sig": "b81a39fcbf6be17000575da609a0ef89cacb65ab3b4b948dc3bdb5e0726457dc8a59f70616878c5b9fddf4cb5e1b525665b2927912ef3e7678f109b22f169722" }