summaryrefslogtreecommitdiff
path: root/e6/f498d7d0513648121f7a84be708767d49e16d7
blob: 8b53a0dbb107b0bb775f716510df309eed356990 (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
Return-Path: <martin.schwarz@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id A904393E
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 22 Jun 2015 19:10:44 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wi0-f177.google.com (mail-wi0-f177.google.com
	[209.85.212.177])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 2ABCFAA
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 22 Jun 2015 19:10:44 +0000 (UTC)
Received: by wicnd19 with SMTP id nd19so85752582wic.1
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 22 Jun 2015 12:10:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=message-id:date:from:user-agent:mime-version:to:cc:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	bh=S+QeKV0tKoBnInRiT4QCh0TE3u8UAzZBQJMBQy1iAyk=;
	b=qNZI9wpKayAtRQc+fT8cpX5yuiN0znmnJ/a51+N3oD4HSRx9RBPPbqDTTZcZnVR6U5
	fUk/qS13bz+vRlj8APyxIE88m4y72UjoVRbL26h2TR+zD5j6/UzwkWgNdrcYldacbk3M
	A9tNJPHiqoVj+ZWnudPaUUNzDMt28wL6s22NitOV0UrlyE0D18+gj8ef4Q5VbLxyQrrl
	9Oc/cOZe1E6cAqbjdIAbBbqU7ONB0lOnynNzJwaRSjKSRlZSBXxRhFuGsftQt7eC7Xoy
	w2V+C+4tyywWTcVbkuHzKv63B8LeCrbwO+fL9cbsACzJTOoe1ZHZbMO6tlpNMaKs30d7
	Bo6A==
X-Received: by 10.180.106.195 with SMTP id gw3mr34790416wib.25.1435000242456; 
	Mon, 22 Jun 2015 12:10:42 -0700 (PDT)
Received: from [10.0.0.5] (188-23-78-116.adsl.highway.telekom.at.
	[188.23.78.116])
	by mx.google.com with ESMTPSA id e2sm6606418wjw.12.2015.06.22.12.10.41
	(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
	Mon, 22 Jun 2015 12:10:41 -0700 (PDT)
Message-ID: <55885DB0.9040709@gmail.com>
Date: Mon, 22 Jun 2015 21:10:40 +0200
From: Martin Schwarz <martin.schwarz@gmail.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: Gavin Andresen <gavinandresen@gmail.com>
References: <CABsx9T2HegqOBqd1jijk1bZBE6N+NH8x6nfwbaoLBACVf8-WBQ@mail.gmail.com>
In-Reply-To: <CABsx9T2HegqOBqd1jijk1bZBE6N+NH8x6nfwbaoLBACVf8-WBQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM,
	RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Draft BIP : fixed-schedule block size increase
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Jun 2015 19:10:44 -0000

Gavin,

in 2022 your proposal (BIP as well as code) crosses the 32MB maximum
message size limit. In order to avoid deployment of code that deterministically
fails fatally in 2022, I'd propose to stop the doublings at 32MB for now and fix
the message size limit in the mean time. Since the message size fix requires
a 2nd hard fork anyway, your current 8GB limit could be re-instateted in that
2nd fork as well. Even if you disagree, I'd suggest to address the topic in the BIP.

best regards,
Martin