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
104
105
106
107
108
|
Return-Path: <jtimon@jtimon.cc>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 84ED1504
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 23 Jul 2015 18:47:10 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wi0-f176.google.com (mail-wi0-f176.google.com
[209.85.212.176])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 157761BF
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 23 Jul 2015 18:47:09 +0000 (UTC)
Received: by wibud3 with SMTP id ud3so36848333wib.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 23 Jul 2015 11:47:08 -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
:content-transfer-encoding;
bh=YGBp+Bb77PNbS8hW5FF3/F1/6KESCiDuKAviSL5DeLI=;
b=SAQo4cCKgYP5qVpH+DvsR0CRyUfiCCk3iAiMJVaT3Zt37ozDcS6546thuj26llmyW5
75Ackkqlirmc5mvAjK5iWzeUY1kDw5X76YVh6veaPBBsy2Ni8urx1nOzEwIxHugE8OD0
M5awpLv4tgIT8gfk9yL9w8pWAD0CD+7DxhHHsN37hKJXot9glPbnaPK0sN7PzgHF96qJ
KSHRUg+bMhQajifcnJ8N/vZ9v1wMmZE22gJo9fts55pE7MGAUJ4KopGuodPq7s9eVxmM
CTPZqJ6E413NrEA+OIll4EPz/KBtdRNjmVoWfDkvN7gCIpOUM9O/28wJGjpT//e+t47+
4JPw==
X-Gm-Message-State: ALoCoQk9tJDEqKo7iiq3MOn6dVEkMwdlg1YQfjuAUfz0rbemZcHT2Oonl4W0M3Pjf73+V8zVStr0
MIME-Version: 1.0
X-Received: by 10.180.92.40 with SMTP id cj8mr18485656wib.92.1437677228605;
Thu, 23 Jul 2015 11:47:08 -0700 (PDT)
Received: by 10.194.95.168 with HTTP; Thu, 23 Jul 2015 11:47:08 -0700 (PDT)
In-Reply-To: <DA1298CE-1C3B-4153-A72D-A0F89D6F1833@mac.com>
References: <CAPg+sBgs-ouEMu=LOVCmOyCGwfM1Ygxooz0shyvAuHDGGZYfJw@mail.gmail.com>
<CAPg+sBgugLSVEwDLXhgey86_rM2fTjGWXFuXsiZioJKCZiHiNg@mail.gmail.com>
<CADm_WcbnQQGZoQ92twfUvbzqGwu__xLn+BYOkHPZY_YT1pFrbA@mail.gmail.com>
<CAPWm=eW8RgrG1CMEAMN4GeiMjZecFvNtZB_Y4rZNeofWSD0=Wg@mail.gmail.com>
<CADm_WcYCUHs9Qe_T6WJOCUSK6stXYD8v6z5JcGHfRMURoOSFTA@mail.gmail.com>
<CABm2gDq3JyZx0QCRDbcNSLSOBKdpi4h_7VN1XL8N42U38+eBAA@mail.gmail.com>
<55B113AF.40500@thinlink.com>
<CABsx9T1MTc-GmuQyFN1vaFK=CDWV_L214Pi9nR6jLMouQQD0fw@mail.gmail.com>
<trinity-f82ce2cb-7260-4b58-a577-9a1b6afad214-1437670245144@3capp-mailcom-bs02>
<DA1298CE-1C3B-4153-A72D-A0F89D6F1833@mac.com>
Date: Thu, 23 Jul 2015 20:47:08 +0200
Message-ID: <CABm2gDoGUZ2eC6Jogt6zA6vWOkqZyteb+kUYqs-E54PL=UEyiQ@mail.gmail.com>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
To: Robert Learney <robertlearney@mac.com>
Content-Type: text/plain; charset=UTF-8
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] Bitcoin Core and hard forks
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: Thu, 23 Jul 2015 18:47:10 -0000
On Thu, Jul 23, 2015 at 7:14 PM, Robert Learney via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> That=E2=80=99s not exactly what=E2=80=99s happened though, is it Cipher? =
Gavin put forward
> 20Mb then after analysis and discussion has moved to 8Mb, whereas the oth=
er
> camp of core developers is firmly stuck in the =E2=80=981Mb or bust=E2=80=
=99 group.
His proposals actually end up with 20 GB and 8 GB respectively. I'm
not sure if you count me on the =E2=80=981Mb or bust=E2=80=99 group, but I'=
m not
firmly stuck anywhere.
I've never said that the block size should never be increased, that it
shouldn't change now, that 8 MB is too much or anything like that
because I simply don't have the data (and I don't think anybody has
it). I invite people to collect that data and I've written a patch to
bitcoin to facilitate that task.
Do you really think that's an obstructionist attitude?
My position could be summarized like this:
- We're going to hit the limit tomorrow, and Bitcoin will fail when we do.
- I'm not so sure we will hit the limit tomorrow but even accepting
the premise, this is a non sequitur. Fees will probably rise, but
that's not necessarily a bad thing. A limit that is meaningful in
practice must happen eventually, mustn't it? If not now, when are we
planning to let that "disaster" happen?
- That's too far in the future to worry about it.
- Does that mean waiting, say, 4 more subsidy halvings, 8? 10?
- Just don't worry about it
I'm not opposing to anything, I'm just patiently waiting for some
answers that never seem to arrive.
If people interpret questions or the fact that when people use
fallacious arguments I like to identify the concrete fallacy they're
using and state it so publicly (I do it for sport and "against all
sides") as "opposition", I don't really think I can do anything about
it.
|
