1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gavinandresen@gmail.com>) id 1WN4K7-0005aF-5O
for bitcoin-development@lists.sourceforge.net;
Mon, 10 Mar 2014 17:49:11 +0000
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;
Received: from mail-yh0-f51.google.com ([209.85.213.51])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WN4K6-0000ae-8l
for bitcoin-development@lists.sourceforge.net;
Mon, 10 Mar 2014 17:49:11 +0000
Received: by mail-yh0-f51.google.com with SMTP id f10so7476862yha.10
for <bitcoin-development@lists.sourceforge.net>;
Mon, 10 Mar 2014 10:49:04 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.236.80.8 with SMTP id j8mr2464453yhe.151.1394473744800; Mon,
10 Mar 2014 10:49:04 -0700 (PDT)
Received: by 10.170.133.195 with HTTP; Mon, 10 Mar 2014 10:49:04 -0700 (PDT)
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
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(gavinandresen[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1WN4K6-0000ae-8l
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Multisign payment protocol?
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 10 Mar 2014 17:49:11 -0000
--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, "Great idea!" 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"><<a href=3D"mailt=
o:drak@zikula.org" target=3D"_blank">drak@zikula.org</a>></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's also terribly complex to generate and keep tra=
ck of. There'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'Reilly Book<br>
"Graph Databases" 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--
|
