Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.160.175 as permitted sender)
	client-ip=209.85.160.175; envelope-from=gavinandresen@gmail.com;
	helo=mail-yk0-f175.google.com; 
MIME-Version: 1.0
In-Reply-To: <CAJHLa0NZkzQQvMxgCJAJGT=Yn6vrVNK8Bg7RAfAjctpnrfg5zA@mail.gmail.com>
References: <CANAnSg3Bt0e7CfUcJXe96xhU6nqif9ey_vurZMZkSa9OHjHStw@mail.gmail.com>
	<CABsx9T0SMi6Gp4JY=CpHxLEu5pVkvDmnug7PsY7m_dvtT7khzg@mail.gmail.com>
	<531DFDF8.80008@gmail.com> <531E52FE.5090107@jerviss.org>
	<531E5454.1030601@gmail.com>
	<CAJHLa0NZkzQQvMxgCJAJGT=Yn6vrVNK8Bg7RAfAjctpnrfg5zA@mail.gmail.com>
Date: Mon, 10 Mar 2014 21:15:28 -0400
Message-ID: <CABsx9T3eViYDsEmLm7ceimJNwci3mCOxWoVnVZHrqp7pDmm0+g@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Jeff Garzik <jgarzik@bitpay.com>
Content-Type: multipart/alternative; boundary=001a1133c7d2a3810704f44a7478
Cc: kjj <bitcoin-devel@jerviss.org>,
	Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Multisign payment protocol?
Precedence: list

--001a1133c7d2a3810704f44a7478
Content-Type: text/plain; charset=ISO-8859-1

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@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

--001a1133c7d2a3810704f44a7478
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Multisig is orthogonal to the payment protocol (but paymen=
t protocol is needed first).<div><br></div><div>There need to be protocols =
for:</div><div><br></div><div>a) Establishing multisig wallets of various s=
orts. See:</div>
<div>=A0=A0<a href=3D"https://moqups.com/gavinandresen/no8mzUDB/">https://m=
oqups.com/gavinandresen/no8mzUDB/</a></div><div>=A0=A0<a href=3D"https://mo=
qups.com/gavinandresen/no8mzUDB/p:ab18547e0">https://moqups.com/gavinandres=
en/no8mzUDB/p:ab18547e0</a></div>
<div>... etc. =A0for a UI mock-up.</div><div>=A0 There needs to be some pro=
tocol so all participants in a multisig wallet contribute keys (actually, w=
e should just assume everybody uses BIP32 HD public keys so we get privacy =
from the start).</div>
<div><br></div><div>Multi-person shared wallets, escrows, and &quot;wallet =
protection service&quot; 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).</div>
<div><br></div><div><br></div><div>b) Gathering signatures for a multisig s=
pend. Here is where the payment protocol is useful; the PaymentRequest mess=
age 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 partic=
ipants creates and submits the Payment and gets the PaymentACK... &quot;to =
be designed&quot;).</div>
<div>=A0 See:</div><div>=A0 =A0 <a href=3D"https://moqups.com/gavinandresen=
/no8mzUDB/p:a7e81be96">https://moqups.com/gavinandresen/no8mzUDB/p:a7e81be9=
6</a></div><div>=A0 =A0=A0<a href=3D"https://moqups.com/gavinandresen/no8mz=
UDB/p:af7339204">https://moqups.com/gavinandresen/no8mzUDB/p:af7339204</a><=
/div>
<div>... for UI mock-up for the multi-person-spend case.</div><div><br></di=
v><div>And maybe a protocol for &quot;I don&#39;t want to be part of this m=
ultisig any more / I lost control of my private key don&#39;t trust me in t=
his multisig any more&quot;.</div>
<div><br></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote=
">On Mon, Mar 10, 2014 at 8:14 PM, Jeff Garzik <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:jgarzik@bitpay.com" target=3D"_blank">jgarzik@bitpay.com</a>&gt=
;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">All of that only melds with the payment protocol under an =
extremely<br>

expansive definition of &quot;payment.&quot; =A0The payment protocol is rea=
lly<br>
geared towards a direct one-to-one relationship....</blockquote><div>=A0</d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bord=
er-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:soli=
d;padding-left:1ex">
=A0<br></blockquote></div>--<br>Gavin Andresen<br>
</div></div>

--001a1133c7d2a3810704f44a7478--