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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gavinandresen@gmail.com>) id 1R9gmK-00019l-P4
for bitcoin-development@lists.sourceforge.net;
Fri, 30 Sep 2011 17:21:40 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.161.47 as permitted sender)
client-ip=209.85.161.47; envelope-from=gavinandresen@gmail.com;
helo=mail-fx0-f47.google.com;
Received: from mail-fx0-f47.google.com ([209.85.161.47])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1R9gmK-0002fJ-3P
for bitcoin-development@lists.sourceforge.net;
Fri, 30 Sep 2011 17:21:40 +0000
Received: by fxi1 with SMTP id 1so4520942fxi.34
for <bitcoin-development@lists.sourceforge.net>;
Fri, 30 Sep 2011 10:21:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.94.134 with SMTP id z6mr430533fam.8.1317403293845; Fri, 30
Sep 2011 10:21:33 -0700 (PDT)
Received: by 10.152.25.105 with HTTP; Fri, 30 Sep 2011 10:21:33 -0700 (PDT)
In-Reply-To: <CAAS2fgRCyppz27-_UhjLnK3a8=DBOVMixk1COv5-uYXGa6WuxA@mail.gmail.com>
References: <CABsx9T2QzafV-uzn7yL01gs2mrzLaP0FCgjt_O--Ldw+s-Xm9w@mail.gmail.com>
<CANEZrP2fqvivhnjSDsLiYdYJ09E7y+=EmsVH3BvLmA4tGri7bQ@mail.gmail.com>
<CAAS2fgRCyppz27-_UhjLnK3a8=DBOVMixk1COv5-uYXGa6WuxA@mail.gmail.com>
Date: Fri, 30 Sep 2011 13:21:33 -0400
Message-ID: <CABsx9T1uxcyqk+Gxrkhb48moszNtCPVpKzuQdnFznr2ZtP_eiw@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Gregory Maxwell <gmaxwell@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.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
-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
0.0 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1R9gmK-0002fJ-3P
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Multisignature transations
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: Fri, 30 Sep 2011 17:21:40 -0000
>> Does this mean dispute mediation (2-of-3) will not be supported?
Not with this PULL-- I think wallet security and backup is a critical
feature, so that is what this is for.
> I thought the plan was also to allow CHECKMULTISIG for smallish numbers of keys.
groffer pointed out that might cause problems when transaction volume
ramps up, because each CHECKMULTISIG counts as 20 sigops, and there is
a limit to the number of sigops you can put into a block. And since it
isn't needed for wallet security and backup I dropped it.
Accepting this does not preclude adding more 'standard' transaction
types in the future.
--
--
Gavin Andresen
|
