summaryrefslogtreecommitdiff
path: root/47/b0693d7e865d099ca2e06fd3d90cdc3cde1534
blob: 0e12fa9798f3a002adba4b9ba3c4eef3b8a85adf (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
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 5F6B39B
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 12 Aug 2015 09:59:09 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com
	[209.85.212.178])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id C31DFE2
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 12 Aug 2015 09:59:08 +0000 (UTC)
Received: by wicne3 with SMTP id ne3so211110189wic.1
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Wed, 12 Aug 2015 02:59: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:date:message-id:subject:from:to:cc
	:content-type;
	bh=IOlfLjW2irrBQKDL/SBxummIepsz+c+01MDDOVOzsm0=;
	b=QqObjs82AJG3WQl7TcODb2MjmtMQDyg3EGl31bCpB5Rx3tkMlrZXEUr81s/mll0U1F
	4KEBWxDC9NGvtxZhiCa3zymZNC/5g+GRMhxjA+855Iyq0a+RtfM1bSYxBapWu9+eHDiR
	pAkAZIrTUvSVM3xo59FdxdPHASRu0FxXm+tOT5Gss6MIJm+obe9TNrBpNRDs/v+PEZLU
	EGNNZfLD4R6aKDW/OhBMSjNeVn8VXISc8UtDWg/ILP4x++ilDV399cTtPaioiKBKyavL
	P0+pDH5xMW97GSfQzFsFxiBWVYfGXAH/pXIbA18aFG3lWFFDOQaZfsjOrjauQrr8REQU
	s4Pw==
X-Gm-Message-State: ALoCoQmfdGl20NtyvfeSLPGOzWdqkvo40Gckvubs32oBhVCpEIb1eJuIUz8286nN7lT5TI9c5T3N
MIME-Version: 1.0
X-Received: by 10.194.120.198 with SMTP id le6mr65933230wjb.133.1439373547471; 
	Wed, 12 Aug 2015 02:59:07 -0700 (PDT)
Received: by 10.194.31.230 with HTTP; Wed, 12 Aug 2015 02:59:07 -0700 (PDT)
Date: Wed, 12 Aug 2015 11:59:07 +0200
Message-ID: <CABm2gDrfB+c1QTZippYYNX-uhcd9NYUcR-VHug6FYtPmSoz4Bw@mail.gmail.com>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
To: Thomas Zander <thomas@thomaszander.se>
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: [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: Wed, 12 Aug 2015 09:59:09 -0000

I believe all concerns I've read can be classified in the following groups:

> 1) Potential indirect consequence of rising fees.

- Lowest fee transactions (currently free transactions) will become
more unreliable.
- 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).

- Bitcoin Core's mempool is unbounded in size and can make the program
crash by using too much memory.
- 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).

I have started with the 3 concerns that I read more often, but please
suggest more concerns for these categories and suggest other
categories if you think there's more.