summaryrefslogtreecommitdiff
path: root/0f/e95a031385ab988153d629bb94bab492cac362
blob: ee64f873fca46f316314f4947af04debddca6fb6 (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
Return-Path: <filipe@ktorn.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 2BB41ABF
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 27 Jun 2015 06:13:14 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from laozi.macaubase.com (z83l79.static.ctm.net [202.175.83.79])
	by smtp1.linuxfoundation.org (Postfix) with ESMTP id EC9B1179
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 27 Jun 2015 06:13:12 +0000 (UTC)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by laozi.macaubase.com (Postfix) with ESMTP id 93E867D41AE
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 27 Jun 2015 14:13:10 +0800 (HKT)
X-Virus-Scanned: amavisd-new at macaubase.com
Received: from laozi.macaubase.com ([127.0.0.1])
	by localhost (laozi.macaubase.com [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id ElMlRIcaOuV2
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 27 Jun 2015 14:13:10 +0800 (HKT)
Received: from dmac13-2.local (nz168l31.bb18094.ctm.net [180.94.168.31])
	by laozi.macaubase.com (Postfix) with ESMTPSA id 8090F7C41EC
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 27 Jun 2015 14:13:09 +0800 (HKT)
Message-ID: <558E3EFD.9040602@ktorn.com>
Date: Sat, 27 Jun 2015 14:13:17 +0800
From: Filipe Farinha <filipe@ktorn.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8;
	rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: bitcoin-dev@lists.linuxfoundation.org
References: <CAPg+sBjOj9eXiDG0F6G54SVKkStF_1HRu2wzGqtFF5X_NAWy4w@mail.gmail.com>	<CADm_Wca+ow4pMzN7SyKjsMdFo0wuUerYYjf5xKs5G_2Q2PzMmA@mail.gmail.com>	<CAPg+sBg=sn7djO_8H16NDg7S7m7_0eTcrgLVofMWQ2ANz+jw9w@mail.gmail.com>	<CADm_WcbQog_UCV=JPHyqTRxKbaGY7jedtHE_D8jJSe_thMg05w@mail.gmail.com>	<CAPg+sBhrBUSfPdMjbLthLEFD17zBC3LoWf9LvZsOD1Vp0D78BQ@mail.gmail.com>	<558DA56F.3010703@jrn.me.uk>
	<20150626193630.GB17829@muck>
In-Reply-To: <20150626193630.GB17829@muck>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] The need for larger blocks
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: Sat, 27 Jun 2015 06:13:14 -0000

On 27/06/2015 03:36, Peter Todd wrote:
> * Make websites with easy to understand displays of what the current mempool
>    backlog is, and what fee/KB is needed to get to the front of the queue. We've
>    done a great job for Bitcoin price charts, let's extend that to transaction
>    fees.
>
+1

This is especially important if take into account all the projects that 
aim to build upon the bitcoin blockchain and that can have a significant 
impact, both in terms of storage space as well as transaction volume spikes.

Just recently I suggested the need for a BIP to standardize reporting of 
"delay alerts" in wallets, so that users can act accordingly (i.e. 
fee-bump, postpone, cancel) before sending their transactions during 
these periods of increased transaction volume.

https://community.blockstack.org/t/blockstore-footprint-on-blockchain/68/5?u=ktorn

IMHO keeping the users informed of potential issues before committing 
transactions to the network can go a long way towards preventing 
frustration and potential backlashes against blockchain tech.

Filipe Farinha