summaryrefslogtreecommitdiff
path: root/a4/e5669cb6536cd535584f7d0a2469aaff872087
blob: 8b71ea573d53925fa134bd81b25000074a36b392 (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
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
Return-Path: <pieter.wuille@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id CF63EACB
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 26 Jun 2015 15:24:23 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com
	[209.85.212.180])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 25CD5E3
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 26 Jun 2015 15:24:23 +0000 (UTC)
Received: by wiwl6 with SMTP id l6so48226335wiw.0
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 26 Jun 2015 08:24:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=57TIVGzhrZJkVzd/IHeMvlI/6EY8CtvgDVyBr1QfnIU=;
	b=x00LFzzZJY78NAix1Gm7EsBflzfeIalJHCMCJB8sufd5jSve022eii59pku28LVNeP
	4qI1lf0SUObkbuTDOMZihSjtvrcGHGPPHpUevCckBGcueFgseHskZfHyThSlYO5lPObK
	nP+p8mhZVbpFRJtN+Jh1YpYFLLbuUGPzdM9yiKV7PWobMlO2NIdNsbT/wiZ4eGpd2Wne
	NpVtna8TNpWx7zuESysBi1H1+voQBQJAFgxvAT6/R9/0m+VmcR1+lxsrmNWAVVnxFFKE
	TXW7fK6R5OK/X777uNEUQVne/4LrPRRg7ZzgYA4TLlDJG+YwIDmn7FtPj9LFMHB3NK6B
	C/pw==
MIME-Version: 1.0
X-Received: by 10.194.112.3 with SMTP id im3mr4061294wjb.54.1435332261917;
	Fri, 26 Jun 2015 08:24:21 -0700 (PDT)
Received: by 10.194.137.38 with HTTP; Fri, 26 Jun 2015 08:24:21 -0700 (PDT)
In-Reply-To: <558D6E26.4000004@bitcoins.info>
References: <CAPg+sBjOj9eXiDG0F6G54SVKkStF_1HRu2wzGqtFF5X_NAWy4w@mail.gmail.com>
	<558D6E26.4000004@bitcoins.info>
Date: Fri, 26 Jun 2015 17:24:21 +0200
Message-ID: <CAPg+sBiPH_j+FJRuvBG6yWbPkC8-4gnC3UrJgw15apfB+DBxAw@mail.gmail.com>
From: Pieter Wuille <pieter.wuille@gmail.com>
To: Milly Bitcoin <milly@bitcoins.info>
Content-Type: multipart/alternative; boundary=001a1130ce229b3cb405196d551b
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,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 15:24:23 -0000

--001a1130ce229b3cb405196d551b
Content-Type: text/plain; charset=UTF-8

On Fri, Jun 26, 2015 at 5:22 PM, Milly Bitcoin <milly@bitcoins.info> wrote:

> >None of this is a reason why the size can't increase. However, in my
> opinion, we should do it because we believe it increases utility and
> understand the risks; not because we're afraid of what might happen if we
> don't hurry up. And from that point of view, it seems silly to make a huge
> increase at once...
>
> Yes.  I think people/businesses want some kind of assurance that there is
> a path to get things done when needed rather than immediate changes.  Since
> there is currently no clear path/schedule to get any changes accomplished
> they gets anxious.
>

I think you just proved my point by saying "when needed".

-- 
Pieter

--001a1130ce229b3cb405196d551b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Fri, Jun 26, 2015 at 5:22 PM, Milly Bitcoin <span dir=
=3D"ltr">&lt;<a href=3D"mailto:milly@bitcoins.info" target=3D"_blank">milly=
@bitcoins.info</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div cla=
ss=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">&gt;None=
 of this is a reason why the size can&#39;t increase. However, in my opinio=
n, we should do it because we believe it increases utility and understand t=
he risks; not because we&#39;re afraid of what might happen if we don&#39;t=
 hurry up. And from that point of view, it seems silly to make a huge incre=
ase at once...<br>
<br></span>
Yes.=C2=A0 I think people/businesses want some kind of assurance that there=
 is a path to get things done when needed rather than immediate changes.=C2=
=A0 Since there is currently no clear path/schedule to get any changes acco=
mplished they gets anxious.<br></blockquote><div><br></div><div>I think you=
 just proved my point by saying &quot;when needed&quot;.<br><br>-- <br></di=
v><div>Pieter<br><br></div></div></div></div>

--001a1130ce229b3cb405196d551b--