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
|
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 A2EA682D
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 4 Aug 2015 10:53:09 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wi0-f171.google.com (mail-wi0-f171.google.com
[209.85.212.171])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 23C2E10A
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 4 Aug 2015 10:53:09 +0000 (UTC)
Received: by wibxm9 with SMTP id xm9so18227590wib.1
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 04 Aug 2015 03:53:07 -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=HkcS7M6g9N9hS/EHMQKN1pKKRZ1/4pzJZun0ovdOjJM=;
b=RyPcI2ZgXwoXYnR1IXhaYhgtKlKxLRRD2Lkj7TjihWY6b8IFX5xJwAr+DaEJHTPFfN
zKO+j200AS9J86g6SoUu4kCCCZXF4dUFqhdde/xTUPhippRivM9AdWCl3rV+cOK8vZZQ
IBX6e5StKo+kdRTerMtjrlIjET0IhQkUvivvEBq+NQ4jYbNkEhJ1K81ksG81xOWJzUXM
QYpnEA9TKXlaIOTS9Xbm3cCCQXJvHvDSqljCME9IBQ2BV9CE3kiBBYqoafwyyMp4JpVH
jIEkL2TODW+AEL1PtXtUknkUfWipPEgnP4K2t4Hl9nXWQ2P8gktl7MvojttjWASY17/+
hQNg==
X-Gm-Message-State: ALoCoQkO91WS3eiJkKqlzPIEDT5ITniBjF4WGtRpf6WLpu1Eb+q+gnnmAm+nYCM5gD6wsYlscI3O
MIME-Version: 1.0
X-Received: by 10.180.109.106 with SMTP id hr10mr45196320wib.58.1438685587391;
Tue, 04 Aug 2015 03:53:07 -0700 (PDT)
Received: by 10.194.31.230 with HTTP; Tue, 4 Aug 2015 03:53:07 -0700 (PDT)
In-Reply-To: <CANe1mWzm2+qRh43bxdbE-VAbQKRJFiD5ss7wZV6x+FGCGV+FCA@mail.gmail.com>
References: <CANe1mWxsAPzWut_gDqe4R-SkDPBYM392NzeVqbUzjwh+pydsWQ@mail.gmail.com>
<CALqxMTEMajz6oHnGvocxy=xDFMBc1LaX1iWYM=w1PF0rH3syFg@mail.gmail.com>
<CANe1mWzm2+qRh43bxdbE-VAbQKRJFiD5ss7wZV6x+FGCGV+FCA@mail.gmail.com>
Date: Tue, 4 Aug 2015 12:53:07 +0200
Message-ID: <CABm2gDpDJyCdM_ivRccueAUvfqHdds+y7+iGRaTRaR4AC6iQZw@mail.gmail.com>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
To: Jim Phillips <jim@ergophobia.org>
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 <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] A reason we can all agree on to increase block
size
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: Tue, 04 Aug 2015 10:53:09 -0000
On Mon, Aug 3, 2015 at 8:53 AM, Jim Phillips via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
>
> Yes I've had a couple other people point that out to me as well and the l=
ogic is sound. Unfortunately that doesn't help solve the actual issue that =
mining is currently consolidated within the jurisdiction of a single politi=
cal body that is not exactly Bitcoin friendly. I don't know how to solve th=
at issue aside from pointing it out and hoping miners outside of China poin=
t to different pools and build more farms in smaller countries. Venezuela f=
or example has cheap electricity and could be a good place to mine. Iceland=
too.
It's interesting how realizing that the blocksize consensus limit does
the opposite of what you initially thought when starting the thread
didn't changed your conclusion from
"If you're truly worried about larger blocks causing centralization,
think about how, by restricting blocksize, you're enabling the
Communist Chinese government to maintain centralized control over 57%
of the Bitcoin hashing power."
to
"If you're truly worried about larger blocks causing centralization,
think about how, by INCREASING blocksize, you're enabling the
Communist Chinese government to POTENTIALLY INCREASE ITS centralized
control over 57% of the Bitcoin hashing power."
The new conclusion is just "somebody should mine from Venezuela and
Iceland" instead.
If you were so concerned about mining centralization, now that you
understand how the blocksize maximum influences it (by being the only
consensus rule that limits it) and if you were consequent, now you
would warn about the dangers of increasing the blocksize consensus
limit in this particular moment in time when mining centralization
looks already really bad (ie 57% hashrate in the same jurisdiction).
Another possibility is that you don't really care about mining
centralization and you were only looking for an argument in favor of
increasing the blocksize, which for some other reason you have already
concluded that must be done as soon as possible.
|
