summaryrefslogtreecommitdiff
path: root/e8/c814ef4d6e0e6a119d114db3c3e45eb81e222c
blob: cfabffd6db22cb5435005dc7cc5baa61a2bce226 (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
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 A7DC8AAC
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 26 Jun 2015 17:04:24 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-pd0-f174.google.com (mail-pd0-f174.google.com
	[209.85.192.174])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 99F2B17E
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 26 Jun 2015 17:04:23 +0000 (UTC)
Received: by pdjn11 with SMTP id n11so78374152pdj.0
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 26 Jun 2015 10:04:23 -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
	:cc:subject:references:in-reply-to:content-type
	:content-transfer-encoding;
	bh=xLIP1jYhv4bKlvFBR0TYsJHY0HggdH6MsFhNoQ7NdEw=;
	b=fdUGZ+WvPor3zikUjGpJ3pF3l8uWlhhfEeGyVfx17oAEUiX0x4gnU63A6PASX0bse4
	dpuieOz2E2K9jabViX9TsEk+5fnQvr7AtsYsWIAVtzryMz10FZ0TLDjtgP+lUn1/Mclg
	Bg7qUFoarR5NHwUvcjBDWf34vJlwefFrG0vXb2KxHBfWq2bxMIwHHrWvfnTMGbaQboit
	du8x0JBeF5OCLhQaxXIuwPiHwp3yUd1ZB+/8qt/jbfRMhf8zKFsMmO1ySNj4ibKEmJJQ
	GbAwuN6Z6KqmM32eEBCMj0XMviXt73AgaXOnqMkLUfYxotgqc9JYpdN5xKIiqoIKEX5c
	uZLQ==
X-Gm-Message-State: ALoCoQlIWCYDS3ghP3TtmAYiRMhJncAEgJv2HsLOEMYTtztFrUw7bBpgr3paVLyus56sqUlYdHzS
X-Received: by 10.68.201.168 with SMTP id kb8mr5241522pbc.50.1435338263228;
	Fri, 26 Jun 2015 10:04:23 -0700 (PDT)
Received: from [192.168.1.89] (99-8-65-117.lightspeed.davlca.sbcglobal.net.
	[99.8.65.117])
	by mx.google.com with ESMTPSA id sx5sm10521517pab.4.2015.06.26.10.04.20
	(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
	Fri, 26 Jun 2015 10:04:21 -0700 (PDT)
Message-ID: <558D8616.7080204@thinlink.com>
Date: Fri, 26 Jun 2015 10:04:22 -0700
From: Tom Harding <tomh@thinlink.com>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64;
	rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: venzen@mail.bihthai.net
References: <CAPg+sBjOj9eXiDG0F6G54SVKkStF_1HRu2wzGqtFF5X_NAWy4w@mail.gmail.com>
	<558D71EF.1060603@thinlink.com> <558D7C39.6010603@mail.bihthai.net>
In-Reply-To: <558D7C39.6010603@mail.bihthai.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
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
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] The need for larger blocks
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, 26 Jun 2015 17:04:24 -0000

Venzen --

The market for block space is not at all the same as the market for bitco=
in.

The centralization risk that is discussed in relation to the market for
block space arises from the resources (network, storage, processor...)
required to run a full node.  That is a consideration in determining the
actual (as opposed to declared) capacity of the system.

The 1MB cap was not indexed to increasing resource availability to begin
with, so one way to determine the size of any initial hard cap increase
would be to estimate the change in resource availability since that time.=