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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <da2ce7@gmail.com>) id 1UFvsN-0003yR-1V
for bitcoin-development@lists.sourceforge.net;
Thu, 14 Mar 2013 00:18:31 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.210.180 as permitted sender)
client-ip=209.85.210.180; envelope-from=da2ce7@gmail.com;
helo=mail-ia0-f180.google.com;
Received: from mail-ia0-f180.google.com ([209.85.210.180])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1UFvsM-0002Oq-8K
for bitcoin-development@lists.sourceforge.net;
Thu, 14 Mar 2013 00:18:31 +0000
Received: by mail-ia0-f180.google.com with SMTP id f27so1554568iae.11
for <bitcoin-development@lists.sourceforge.net>;
Wed, 13 Mar 2013 17:18:25 -0700 (PDT)
X-Received: by 10.50.106.199 with SMTP id gw7mr18383981igb.27.1363220304939;
Wed, 13 Mar 2013 17:18:24 -0700 (PDT)
Received: from [192.168.178.47] (124-148-133-125.dyn.iinet.net.au.
[124.148.133.125])
by mx.google.com with ESMTPS id dy5sm847343igc.1.2013.03.13.17.18.22
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Wed, 13 Mar 2013 17:18:24 -0700 (PDT)
Message-ID: <51411744.6010908@gmail.com>
Date: Thu, 14 Mar 2013 11:18:12 +1100
From: Cameron Garnham <da2ce7@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
rv:17.0) Gecko/20130307 Thunderbird/17.0.4
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <201303131256.30144.luke@dashjr.org>
<201303132106.45334.andyparkins@gmail.com>
<201303132114.04596.luke@dashjr.org>
<20130313212243.GQ96148@giles.gnomon.org.uk>
<CAAS2fgSLmjhMmmrxjKQ0KOX5EEM4=+Wwebuaw4NHE9LdtLSP6Q@mail.gmail.com>
<20130313213608.GR96148@giles.gnomon.org.uk>
In-Reply-To: <20130313213608.GR96148@giles.gnomon.org.uk>
X-Enigmail-Version: 1.5.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Spam-Score: -1.4 (-)
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
(da2ce7[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in
digit (da2ce7[at]gmail.com)
-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: 1UFvsM-0002Oq-8K
Subject: Re: [Bitcoin-development] 0.8.1 ideas
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: Thu, 14 Mar 2013 00:18:31 -0000
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
I think that the course of action is quite simple:
1. Upgrade all the clients to implement the lock limits. (in code,
not at the DB exception layer). A bit of research is needed to work
out exactly what these limits are so we can maximise the number of
transactions.
2. Fix the DB layer, and test that all the clients can support 1MB blocks.
3. Once we are confident that the network supports 1MB blocks, set a
date where the lock limits are removed.
For me, everyone signed up to bitcoin thinking that there was a 1MB /
block limit. The lock limits were unexpected, and could be considered
extremely uncontroversial to remove.
The discussion of larger blocks (i.e. > 1MB ), that I happen to
disagree with, is not relevant to the discussion of the removal of
the lock limits.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iF4EAREIAAYFAlFBF0QACgkQBJ8cMDO159aWbwEAs8Ldt8hRpzjS4HdrH3U9Jnaq
MWhifXqkJuVC0TVCz3EBAOAfSogdSS7rJvtfV8FqTIox1ek/xJxuHvZdonUnQN1K
=I5Cf
-----END PGP SIGNATURE-----
|
