Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.213.51 as permitted sender)
	client-ip=209.85.213.51; envelope-from=gavinandresen@gmail.com;
	helo=mail-yh0-f51.google.com; 
MIME-Version: 1.0
In-Reply-To: <CANAnSg3Bt0e7CfUcJXe96xhU6nqif9ey_vurZMZkSa9OHjHStw@mail.gmail.com>
References: <CANAnSg3Bt0e7CfUcJXe96xhU6nqif9ey_vurZMZkSa9OHjHStw@mail.gmail.com>
Date: Mon, 10 Mar 2014 13:49:04 -0400
Message-ID: <CABsx9T0SMi6Gp4JY=CpHxLEu5pVkvDmnug7PsY7m_dvtT7khzg@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Drak <drak@zikula.org>
Content-Type: multipart/alternative; boundary=20cf300fb33d35243004f444382c
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Multisign payment protocol?
Precedence: list

--20cf300fb33d35243004f444382c
Content-Type: text/plain; charset=ISO-8859-1

In my experience, best process for standardizing something is:

1) Somebody has a great idea
2) They implement it
3) Everybody agrees, "Great idea!" and they copy it.
4) Idea gets refined by the people copying it.
5) It gets standardized.

Mutisig wallets are at step 2 right now. BIP is step 5, in my humble
opinion...


On Mon, Mar 10, 2014 at 1:39 PM, Drak <drak@zikula.org> wrote:

> I was wondering if there would be merit in a kind of BIP for a payment
> protocol using multisig?
>
> Currently, setting up a multisig is quite a feat. Users have to exchange
> public keys, work out how to get the public keys from their addresses. If
> one of the parties are not savvy enough, an malicious party could easily be
> setup that was 2 of 3 instead of 2 of 2 where the malicious party generates
> the multisig address+script and thus be able to run off with funds anyway.
>
> It's also terribly complex to generate and keep track of. There's been a
> nice attempt at creating an browser interface at coinb.in/multisig but it
> still lacks the kind of ease with created by the payment protocol. If there
> was a BIP then it would go a long way to aiding future usability of
> multisig wallet implementations.
>
> What are your thoughts?
>
> Drak
>
>
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/13534_NeoTech
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>


-- 
--
Gavin Andresen

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

<div dir=3D"ltr">In my experience, best process for standardizing something=
 is:<div><br></div><div>1) Somebody has a great idea</div><div>2) They impl=
ement it</div><div>3) Everybody agrees, &quot;Great idea!&quot; and they co=
py it.</div>
<div>4) Idea gets refined by the people copying it.</div><div>5) It gets st=
andardized.</div><div><br></div><div>Mutisig wallets are at step 2 right no=
w. BIP is step 5, in my humble opinion...</div><div><br></div><div><br>
</div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">O=
n Mon, Mar 10, 2014 at 1:39 PM, Drak <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:drak@zikula.org" target=3D"_blank">drak@zikula.org</a>&gt;</span> wrote:<=
br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr">I was wondering if there would be merit in a kind of BIP f=
or a payment protocol using multisig?<div><br><div>Currently, setting up a =
multisig is quite a feat. Users have to exchange public keys, work out how =
to get the public keys from their addresses. If one of the parties are not =
savvy enough, an malicious party could easily be setup that was 2 of 3 inst=
ead of 2 of 2 where the malicious party generates the multisig address+scri=
pt and thus be able to run off with funds anyway.</div>


<div><br></div><div>It&#39;s also terribly complex to generate and keep tra=
ck of. There&#39;s been a nice attempt at creating an browser interface at =
<a href=3D"http://coinb.in/multisig" target=3D"_blank">coinb.in/multisig</a=
> but it still lacks the kind of ease with created by the payment protocol.=
 If there was a BIP then it would go a long way to aiding future usability =
of multisig wallet implementations.</div>


<div><br></div><div>What are your thoughts?</div><span class=3D"HOEnZb"><fo=
nt color=3D"#888888"><div><br></div><div>Drak</div></font></span></div></di=
v>
<br>-----------------------------------------------------------------------=
-------<br>
Learn Graph Databases - Download FREE O&#39;Reilly Book<br>
&quot;Graph Databases&quot; is the definitive new guide to graph databases =
and their<br>
applications. Written by three acclaimed leaders in the field,<br>
this first edition is now available. Download your free book today!<br>
<a href=3D"http://p.sf.net/sfu/13534_NeoTech" target=3D"_blank">http://p.sf=
.net/sfu/13534_NeoTech</a><br>_____________________________________________=
__<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
<br></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>--<br>Ga=
vin Andresen<br>
</div>

--20cf300fb33d35243004f444382c--