summaryrefslogtreecommitdiff
path: root/a1/d9ee394d124b889ad0a5ba52b7908ce368da89
blob: 490a156f75e729f653f4900f4d4c438ed3ddb87a (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
86
Return-Path: <tomh@thinlink.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 10AD91BB
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 31 Jul 2015 02:02:17 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-pa0-f43.google.com (mail-pa0-f43.google.com
	[209.85.220.43])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id BCDBAB0
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 31 Jul 2015 02:02:16 +0000 (UTC)
Received: by pacan13 with SMTP id an13so32828014pac.1
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Thu, 30 Jul 2015 19:02:16 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:subject:to:references:from:message-id:date
	:user-agent:mime-version:in-reply-to:content-type
	:content-transfer-encoding;
	bh=e1/TR/+uS8BfIQOIlfKTRscy4JJ6d/rumHVJ7QF+BwI=;
	b=jGmdaSMXSAcvw+xaEPCCpdN+MjvsPZKnH6RhDFNMAZ4Gx7c5PSKKYR+W5NKMn+13Tn
	4Mx61uez2dnbtPt70OK51y0JsweXDm5Hyzc0uFBcu+ztG+uAzP2nXN5mE/y7GgZ0ReIe
	7O0YO7ZCNtYGPTRKOZJI1bFaF+RSpCi4a4jJRR8tS9qiiYuGTeSB/wrtQiv0As8YILT7
	rmJ+/AVg2VxWgB7XPvZxBuiCarqJ6AN6xBe7AaMi7vIv/ZjVZX1h2Z5Hb3lm7LELlGI0
	9v/WVJ9H3XdkKS/pnrOQrkzCuxIymILO6a8HrdaFZ7lNpE4ZPgW7sMoywFoYAfnBge5m
	cLGg==
X-Gm-Message-State: ALoCoQnME/oT/P+6zBJFdXhxJovsSUQCveyS+SiIkRRl1HblUUEZXj1lexJlPht/gNRSSEav5MEM
X-Received: by 10.66.145.195 with SMTP id sw3mr1001434pab.72.1438308136454;
	Thu, 30 Jul 2015 19:02:16 -0700 (PDT)
Received: from [192.168.1.89] (99-8-65-117.lightspeed.davlca.sbcglobal.net.
	[99.8.65.117]) by smtp.googlemail.com with ESMTPSA id
	ex13sm4421537pac.17.2015.07.30.19.02.14
	for <bitcoin-dev@lists.linuxfoundation.org>
	(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
	Thu, 30 Jul 2015 19:02:15 -0700 (PDT)
To: bitcoin-dev@lists.linuxfoundation.org
References: <CABK8tmUd+RqTP=vteoX0UEwbzG-X=N3GWvUkD2g5q2suQNpx2w@mail.gmail.com>
From: Tom Harding <tomh@thinlink.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <55BAD726.8070200@thinlink.com>
Date: Thu, 30 Jul 2015 19:02:14 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101
	Thunderbird/38.1.0
MIME-Version: 1.0
In-Reply-To: <CABK8tmUd+RqTP=vteoX0UEwbzG-X=N3GWvUkD2g5q2suQNpx2w@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,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
Subject: Re: [bitcoin-dev] Another block size limit solution - dynamic block
 size limit.
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: Fri, 31 Jul 2015 02:02:17 -0000

On 7/30/2015 8:03 AM, Максим Божко via bitcoin-dev wrote:
> I propose to implement dynamic block size limit. Its short summary is
> here in doc:
>
> https://docs.google.com/document/d/1ixt0loN7LOF6M_2HXvV0D-3ZCayvcfj0rzVm-h-6ONg/edit
>
>

A dynamic limit based on recent block sizes has been discussed, but with
all the traffic on the list, finding the discussions is bound to be
difficult.

I think the main reason this kind of thing hasn't gotten traction is
that it would allow miners alone to chart the course of block sizes. 
Miners are likely to have more powerful equipment than everybody else,
and with the current network design, that could reduce the population of
nodes able to keep up, with no limit in the loss of decentralization.