blob: 05b9d03f0ff43e2a7e5e42f111d5229e0fd35b70 (
plain)
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-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <tomh@thinlink.com>) id 1Z5NKA-0004HC-4s
for bitcoin-development@lists.sourceforge.net;
Thu, 18 Jun 2015 00:04:54 +0000
X-ACL-Warn:
Received: from mail-pd0-f178.google.com ([209.85.192.178])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Z5NK8-0006sI-0l
for bitcoin-development@lists.sourceforge.net;
Thu, 18 Jun 2015 00:04:54 +0000
Received: by pdbki1 with SMTP id ki1so52237468pdb.1
for <bitcoin-development@lists.sourceforge.net>;
Wed, 17 Jun 2015 17:04:46 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to
:subject:references:in-reply-to:content-type
:content-transfer-encoding;
bh=+qSlanAIdWaEArBCw2nCuDdIiCLPU6oGXdVGbUGHc2E=;
b=UOP3h393KneEyJ1SwfQ+Dpnl4HqmMvADJTzXIUXppSvbFAXe8Tu3vMvMHK+Vw+w/Ry
nlK9vA2AeUmB2i8ZQnWIZY92I67UrQhojoTIA+EJOSAtu7OyyKI8EGeYgeNRXlUaMFKl
gBVITCegZeaG4pqELSDBgVcPlWWZRkx4Jithu2H11CNLJTHpY9mY/OVFa8XN4DZhJt8o
G/LUvha6ggGrGHp8HSohAsQsl4QBec1RjKpzJZLEx5Il8uyf96phZPWnh18YoAwmWNKK
jDBpPT6TWBKt34JxhR/uMh3+b8b5WRyOjCHHh7KbANCIsSV8+T4uJSNtSs4eMMJkGVoo
vJfw==
X-Gm-Message-State: ALoCoQnHG79WhRbLSUVJOg7REX3EVKHuwEoVVjtOsh1oXDX6SQne2Fq2nD8S7QgJZj8IUovRf/DW
X-Received: by 10.70.38.33 with SMTP id d1mr15445638pdk.99.1434585886269;
Wed, 17 Jun 2015 17:04:46 -0700 (PDT)
Received: from [10.100.1.239] ([204.58.254.99])
by mx.google.com with ESMTPSA id f1sm5919441pds.62.2015.06.17.17.04.44
for <bitcoin-development@lists.sourceforge.net>
(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Wed, 17 Jun 2015 17:04:45 -0700 (PDT)
Message-ID: <55820B16.5060806@thinlink.com>
Date: Wed, 17 Jun 2015 17:04:38 -0700
From: Tom Harding <tomh@thinlink.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <COL131-DS3380A8C27DE6CBC0D98A4CDB60@phx.gbl>
<COL131-DS14939FCAB6DB494743B545CDA60@phx.gbl>
In-Reply-To: <COL131-DS14939FCAB6DB494743B545CDA60@phx.gbl>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-Spam-Score: 0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.6 RCVD_IN_SORBS_WEB RBL: SORBS: sender is an abusable web server
[204.58.254.99 listed in dnsbl.sorbs.net]
X-Headers-End: 1Z5NK8-0006sI-0l
Subject: Re: [Bitcoin-development] soft-fork block size
increase(extensionblocks)
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, 18 Jun 2015 00:04:54 -0000
"Increase DEFAULT_BLOCK_MAX_SIZE to 1MB"
https://github.com/bitcoin/bitcoin/pull/6231
On 6/17/2015 8:28 AM, Raystonn . wrote:
> Wow. That email was delayed by the list for quite some time. It was
> sent on 6/1.
>
>> I also need to argue for increasing the default block limit to the
>> full 1MB in the next release. We’re already hitting that limit in
>> bursts of transactions, which puts pressure on the average displayed
>> in the below graphs.
>
>
|
