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
|
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 <mh.in.england@gmail.com>) id 1WN4LC-0005eW-PR
for bitcoin-development@lists.sourceforge.net;
Mon, 10 Mar 2014 17:50:18 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.214.181 as permitted sender)
client-ip=209.85.214.181; envelope-from=mh.in.england@gmail.com;
helo=mail-ob0-f181.google.com;
Received: from mail-ob0-f181.google.com ([209.85.214.181])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WN4LC-0000e4-2C
for bitcoin-development@lists.sourceforge.net;
Mon, 10 Mar 2014 17:50:18 +0000
Received: by mail-ob0-f181.google.com with SMTP id wp4so7079088obc.26
for <bitcoin-development@lists.sourceforge.net>;
Mon, 10 Mar 2014 10:50:12 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.60.15.38 with SMTP id u6mr21189093oec.26.1394473812772; Mon,
10 Mar 2014 10:50:12 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.71.231 with HTTP; Mon, 10 Mar 2014 10:50:12 -0700 (PDT)
In-Reply-To: <CANAnSg3Bt0e7CfUcJXe96xhU6nqif9ey_vurZMZkSa9OHjHStw@mail.gmail.com>
References: <CANAnSg3Bt0e7CfUcJXe96xhU6nqif9ey_vurZMZkSa9OHjHStw@mail.gmail.com>
Date: Mon, 10 Mar 2014 18:50:12 +0100
X-Google-Sender-Auth: BIDBEWmd28EqWrdqh0_R3KuRdgY
Message-ID: <CANEZrP3Tg=WAnpfV4FSznk_x9JR0wT_z5dT6XZzpQY+yMaKpBw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Drak <drak@zikula.org>
Content-Type: multipart/alternative; boundary=089e013cc024424e3b04f4443cb8
X-Spam-Score: -0.5 (/)
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
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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: 1WN4LC-0000e4-2C
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:50:19 -0000
--089e013cc024424e3b04f4443cb8
Content-Type: text/plain; charset=UTF-8
No, this doesn't make any sense. Multisig outputs are a tool you use to
build helpful features, not a feature in and of themselves.
By all means create a nice protocol, implementation and BIP for something
like:
- Creation of multi-user money pools for managing an organisations funds
- Dispute mediated transactions
- Watchdog services that provide a third party risk analysis of transactions
- Micropayment channels (actually me and Matt already did this, sans BIP)
but trying to do just "multisig" won't work well.
--089e013cc024424e3b04f4443cb8
Content-Type: text/html; charset=UTF-8
<div dir="ltr">No, this doesn't make any sense. Multisig outputs are a tool you use to build helpful features, not a feature in and of themselves.<div><br></div><div>By all means create a nice protocol, implementation and BIP for something like:</div>
<div><br></div><div>- Creation of multi-user money pools for managing an organisations funds</div><div>- Dispute mediated transactions</div><div>- Watchdog services that provide a third party risk analysis of transactions</div>
<div>- Micropayment channels (actually me and Matt already did this, sans BIP)</div><div><br></div><div>but trying to do just "multisig" won't work well.</div><div class="gmail_extra"><br></div></div>
--089e013cc024424e3b04f4443cb8--
|
