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
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jtimon@jtimon.cc>) id 1YqOYg-0008R2-6o
for bitcoin-development@lists.sourceforge.net;
Thu, 07 May 2015 16:21:58 +0000
Received: from mail-wg0-f51.google.com ([74.125.82.51])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YqOYe-00077g-UP
for bitcoin-development@lists.sourceforge.net;
Thu, 07 May 2015 16:21:58 +0000
Received: by wgyo15 with SMTP id o15so48872544wgy.2
for <bitcoin-development@lists.sourceforge.net>;
Thu, 07 May 2015 09:21:50 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type;
bh=NCuRam9xR8MVSGzKcjsXPvRCw8UZP8Ti9iOOaLv1n7o=;
b=KydwaWBinhKmj2kvPsqrgTWlFJd2jTP2sEqxy7pyFRrswDx2OH7LHZxXe20hQT96dS
d/XymQzITrkKgMP/mcba8EZFEEA7BU51P4QEQDm6PfIHHY+KLO80EbBIl4fpyNZKQqFl
NUXQYtVJaG2WsRc6bkf/9sYl7pgF68Aq8iD3dw/9pU8zupW2zhsMCoHDhYgRt02a1tP9
0Ppv2n6sfBrRuQlE8bTmsF4WHYUl8Xtd25fGNoPCO4N8Us+4LrVyYowLpPtmCCEK/oyM
ZXcz+VOrmoJdbS+6oeKC4TjBo8M5Ao/WqOnhjAr7tcnMtjJTUVAtqktjGd4m33y2G7Y6
Ye+w==
X-Gm-Message-State: ALoCoQkwUl4VIidn55+4RrY2Jn69SaQSfqseoU94m7f2Rx2Iv86h+bvGP5iC1yhvmyU60MOTVnRH
MIME-Version: 1.0
X-Received: by 10.195.17.196 with SMTP id gg4mr8878427wjd.109.1431015710826;
Thu, 07 May 2015 09:21:50 -0700 (PDT)
Received: by 10.194.124.2 with HTTP; Thu, 7 May 2015 09:21:50 -0700 (PDT)
In-Reply-To: <CANEZrP0bmh5braGO5OKTNJU9VC_9=_1RDqHMx=aJBxT1w-q8oA@mail.gmail.com>
References: <554A91BE.6060105@bluematt.me>
<CANEZrP3wGWHdz+ut6pvke5TJJsc1rTFt8sn2KziX35oL5LAsyg@mail.gmail.com>
<CABm2gDpDvk2VsQ+mJ-BoeBKmvu9jBXNujZEFKuCStRNjFL6VOA@mail.gmail.com>
<CANEZrP2zAGCCBhNa4=9yw+A_Dn5o4SQXoPTE_qcJzZ1dFuF2tw@mail.gmail.com>
<CABm2gDqd6iHRUDKZWWTudcC1QkYa+rCuHjz7pMC2K1Db8wpgfA@mail.gmail.com>
<CANEZrP1CU0kB0vXeXUX1L8byaT-Zf2xg+3N+GeNthi_i6bn1qw@mail.gmail.com>
<CABsx9T2Nxvr4fqREMw3_LXftzsxrUAR1+9sVMa8_EpTnH1nN1Q@mail.gmail.com>
<CAPWm=eUFe7dKJCLeNACZ4n9vw0Xj9rHVM_RRLSczGXNU-ShR2w@mail.gmail.com>
<CANEZrP1tCda9EbYgYu5QHN8ZgBCtGP7zRiDaXnq-rWU0ZHR9NQ@mail.gmail.com>
<CAJHLa0Nrp4QEQqrBu6Tb+dohxX2VhWKMnO40xscZF1OJdfPF-A@mail.gmail.com>
<CANEZrP0bmh5braGO5OKTNJU9VC_9=_1RDqHMx=aJBxT1w-q8oA@mail.gmail.com>
Date: Thu, 7 May 2015 18:21:50 +0200
Message-ID: <CABm2gDozyxovazcNEjWsRK0KzNJotWTg9X4m3aOfx7Gr_KprxQ@mail.gmail.com>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
To: Mike Hearn <mike@plan99.net>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1YqOYe-00077g-UP
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Block Size Increase
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 07 May 2015 16:21:58 -0000
On Thu, May 7, 2015 at 4:52 PM, Gavin Andresen <gavinandresen@gmail.com> wrote:
> I would very much like to find some concrete course of action that we can
> come to consensus on. Some compromise so we can tell entrepreneurs "THIS is
> how much transaction volume the main Bitcoin blockchain will be able to
> support over the next eleven years."
Mhmm, I hadn't thought about this. This makes sense and actually
explains the urgency on taking a decision better than anything else
I've heard.
On Thu, May 7, 2015 at 5:29 PM, Mike Hearn <mike@plan99.net> wrote:
> If it's not raised, then ....... well, then we're in new territory entirely.
> Businesses built on the assumption that Bitcoin could become popular will
> suddenly have their basic assumptions invalidated. Users will leave. The
> technical code change would be zero, but the economic change would be
> significant.
This, on the other hand, is a non sequitur [1], another type of fallacy.
Well, several of them, actually:
- If it's not raised, then bitcoin cannot become popular
- If it's not raised, then users will leave
- Businesses built on the assumption that Bitcoin could become popular
were also assuming that it's going to be risen.
These statements may even be true, but they're no logical conclusions
even if they seem obvious to you.
I don't think those claims are strictly true, specially because they
involve predictions about what people will do.
But if they're true they require some proof or at least some explanation.
[1] http://en.wikipedia.org/wiki/Non_sequitur_(logic)#Affirming_the_consequent
|
