Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of zikula.org
	designates 74.125.82.42 as permitted sender)
	client-ip=74.125.82.42; envelope-from=drak@zikula.org;
	helo=mail-wg0-f42.google.com; 
MIME-Version: 1.0
From: Drak <drak@zikula.org>
Date: Mon, 10 Mar 2014 17:39:03 +0000
Message-ID: <CANAnSg3Bt0e7CfUcJXe96xhU6nqif9ey_vurZMZkSa9OHjHStw@mail.gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: multipart/alternative; boundary=047d7bf0c1068b967704f4441513
Subject: [Bitcoin-development] Multisign payment protocol?
Precedence: list

--047d7bf0c1068b967704f4441513
Content-Type: text/plain; charset=UTF-8

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

--047d7bf0c1068b967704f4441513
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<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">coinb.in/multisig</a> but it still lac=
ks the kind of ease with created by the payment protocol. If there was a BI=
P 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><div><br></div><div>Drak</=
div></div></div>

--047d7bf0c1068b967704f4441513--