summaryrefslogtreecommitdiff
path: root/15/71819daee810ed93fa901db67b21f927879fe4
blob: ef6227692d1e2001f43fd32a400a48aa525f748b (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
Return-Path: <milly@bitcoins.info>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id D370683D
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 26 Jun 2015 18:32:50 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from mail.help.org (mail.help.org [70.90.2.18])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 49BB27C
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 26 Jun 2015 18:32:50 +0000 (UTC)
Received: from [10.1.10.25] (B [10.1.10.25]) by mail.help.org with ESMTPA
	; Fri, 26 Jun 2015 14:32:45 -0400
References: <CAPg+sBjOj9eXiDG0F6G54SVKkStF_1HRu2wzGqtFF5X_NAWy4w@mail.gmail.com>
	<558D6E26.4000004@bitcoins.info>
	<CAPg+sBiPH_j+FJRuvBG6yWbPkC8-4gnC3UrJgw15apfB+DBxAw@mail.gmail.com>
	<CADm_WcYKkrPO-9tiz8d2FFeLk4K7gSgVJG+4PXysi+n8LtXkYw@mail.gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
From: Milly Bitcoin <milly@bitcoins.info>
Message-ID: <558D9AC8.3020805@bitcoins.info>
Date: Fri, 26 Jun 2015 14:32:40 -0400
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101
	Thunderbird/38.0.1
MIME-Version: 1.0
In-Reply-To: <CADm_WcYKkrPO-9tiz8d2FFeLk4K7gSgVJG+4PXysi+n8LtXkYw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 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] 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 18:32:50 -0000

> Proposing inaction is not the way you convince people that bitcoin can 
> scale.
>
> People and businesses cannot perform any capacity planning and future 
> projections under the proposal of "economic change through inaction."
>
> There will be no growth, by your argument, until there is fee 
> pressure.  And what happens then?

It is not clear he is proposing "inaction."  I am not sure what he is 
proposing other than being against knee-jerk reactions.  He has also 
said he doesn't want to take on the responsibility of deciding on 
whether to approve hard fork changes which is understandable considering 
all the other things he is doing.  Such a responsibility is probably too 
much of a burden to put on any one individual no matter who it is.  The 
next step is to come up with a process to handle proposed hard-fork 
changes other than just to ask the Core maintainer to do it.

Russ