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
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
|
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 E2340273
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 14 Aug 2015 22:35:07 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-oi0-f43.google.com (mail-oi0-f43.google.com
[209.85.218.43])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 13F9610D
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 14 Aug 2015 22:35:07 +0000 (UTC)
Received: by oio137 with SMTP id 137so52326007oio.0
for <bitcoin-dev@lists.linuxfoundation.org>;
Fri, 14 Aug 2015 15:35:06 -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=2jZUonYOoSlThKqQMlr7WUrKomnnj5DctqzY5L1RUFo=;
b=MLdLBYgOyBHlgIJUHBl57ekpl+RdnKhotU9Wc04fTLpLdm4VF1g06ckWSD5eT7u6W+
4kMUQOd1NNqUNd4yPDdOiUIB0RgTQ9Qhp3jAFhD9+smwogk3CkGr7Khz5ZOCHuRBaWrK
5rdfw0slW+pin3qjaAdOxJTh+vw/ghbu+zeNN7chJsKTzqT05UskAqpbl9SkIZRHw1WY
3PTpstKR8B2mvkJl0ZuNdEZb3mZTEToEpJMivcRF/vymE60S3yWCUcgXuVxJhkc7Sms8
mOjzd22sbbX8C5sfKwhgdwg98D73pFCJGaCLwNyPQE0VqrTrnjduLmEschbHk5NBVlVM
EVEQ==
X-Gm-Message-State: ALoCoQkc46NVwIQHroFeaym9xBAeb2KTdlYylag6DU5hTqAmsCNJq3yjSGgX2AiiIC37YIZvRCkG
MIME-Version: 1.0
X-Received: by 10.202.169.138 with SMTP id s132mr34472892oie.71.1439591706435;
Fri, 14 Aug 2015 15:35:06 -0700 (PDT)
Received: by 10.202.71.85 with HTTP; Fri, 14 Aug 2015 15:35:06 -0700 (PDT)
In-Reply-To: <55CB2C57.1070307@mail.bihthai.net>
References: <CABm2gDrfB+c1QTZippYYNX-uhcd9NYUcR-VHug6FYtPmSoz4Bw@mail.gmail.com>
<55CB2C57.1070307@mail.bihthai.net>
Date: Sat, 15 Aug 2015 00:35:06 +0200
Message-ID: <CABm2gDp92omWk-eg5Sp8u4V8Z9hJcT_TcwyZyaw3Nm4ypLiWXQ@mail.gmail.com>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
To: venzen@mail.bihthai.net
Content-Type: text/plain; charset=UTF-8
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 summary list of all concerns related to not
rising the 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: Fri, 14 Aug 2015 22:35:08 -0000
On Wed, Aug 12, 2015 at 1:21 PM, Venzen Khaosan <venzen@mail.bihthai.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Jorge, you say 3 concerns at the end of your message but I only see 1)
> and 2). Assuming you've got a 3) and will add it, I'll contribute:
No, sorry it's 2 concerns/risks with 2 sub-concerns/risks each:
1) Potential indirect consequence of rising fees.
1.1) Lowest fee transactions (currently free transactions) will become
more unreliable.
1.2) People will migrate to competing systems (PoW altcoins) with lower fees.
2) Software problem independent of a concrete block size that needs to
be solved anyway, often specific to Bitcoin Core (ie other
implementations, say libbitcoin may not necessarily share these
problems).
2.1) Bitcoin Core's mempool is unbounded in size and can make the program
crash by using too much memory.
2.2) There's no good way to increase the fee of a transaction that is
taking too long to be mined without the "double spending" transaction
with the higher fee being blocked by most nodes which follow Bitcoin
Core's default policy for conflicting spends replacements (aka "first
seen" replacement policy).
> 4) General, undefined fear that something bad is going to happen when
> nodes choke up on a backlog of transactions.
> - - no specific symptoms are pointed at but presumably there is
> "pre-traumatic stress" at play.
> - - Bitcoin-based businesses are going to lose money, customers and
> potentially fail
> - - people will flee Bitcoin for another cryptocoin and Bitcoin will be
> left in the corner, collecting dust and memories of it will fade as
> SuperCoin with its big blocks becomes all things to all people.
I believe thisbelongs in 2, not really sure if 2.1 or 2.2 since it's
related to both.
> 5) Specific belief that the exchange rate will decline on network
> unreliability
> - - traders and investors will bid the price down, or
> - - traders/investors will stop speculating all together because even if
> their speculation is successful, they're not sure they'll be able to
> get their bitcoin out of exchanges, what with the broken network and all.
> - - The exchange rate reflects Bitcoin's value and not just speculation
> guided by a few large players like in other markets.
I believe "fear of exchange rate declining" can probably be added to
any concern/risk "leaf", so we should probably leave that for the end
or just omit it.
> 6) Belief that Bitcoin's "cargo" is about to be delivered by fate:
> - - see https://en.wikipedia.org/wiki/Cargo_cult
> - - the cargo is variably presumed to be a range of hoped-for events: an
> adoption surge, a speculative rally similar to (or bigger than) 2013,
> or a global financial crisis that sees Bitcoin become the safe haven
> of choice.
> - - for the cargo to be delivered, a "runway" must be built - the larger
> the runway, the larger the cargo delivery. If the current runway is
> not expanded, then the cargo plane will go to a different island and
> won't come to Bitcoin Island.
> - - it is short-sighted and, in a way, ungrateful of the "generals" not
> to expand the runway - it will be their fault that the cargo doesn't
> get delivered and all the island's people, no the whole ocean's
> islands, will suffer because of silly security concerns.
> - - some people have taken the blueprints of the airbase and are
> building a large airstrip elsewhere on Bitcoin Island, but nobody is
> helping them build that long and wide runway. Everybody wants to
> expand this moderate runway - even the renegades who started Big
> Blocks Great Success airstrip.
> - - The sacred site of No-Middle-Zero-Attack-Point is at the start of
> the current runway. To expand it the site must be destroyed, but some
> former generals and many people say: It doesn't matter, we want Cargo,
> not a small attack surface. Just blast it!
I'm not sure I understood this but seems related to the exchange rate.
|
