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
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
|
Return-Path: <voisine@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 11DC5ABF
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 27 Jun 2015 07:14:43 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-qk0-f182.google.com (mail-qk0-f182.google.com
[209.85.220.182])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 419C7E7
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 27 Jun 2015 07:14:42 +0000 (UTC)
Received: by qkbp125 with SMTP id p125so66807302qkb.2
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 27 Jun 2015 00:14:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc:content-type;
bh=hR/S4+YQYNCxzY5iABTVCpgnDmIw8PT5EdEE7IoyaPE=;
b=fTGBdwmA4oOePDVpTQXazRlvpn02K41FCuMjYrR1KFrIue//cYlaZAx05EGitK5cAm
XSKdrE1wemEhEOeuiWtRxFjnAZ4mQNclQr9194jFYJEnoZNiZujirxauVkI++No9e2Rs
5orcNeOY9yh57p67kj0YTDrU6hEbIbI1RQZNT63VJYPWrqKN8uWW0F/NnDLsYBWFbaKv
ZwQwu8obegpWG5BsYIZDQs+f8ylOl6tee8LPAPS3aObAf4QtCat90JX5AjHfczwaZC46
lILMjWo+hgow4LKX6H/N5/aXrxzJtvGQfDoUa/RFrD2zvpa/ouePlwGlJZz0gJ387zd5
vkIw==
MIME-Version: 1.0
X-Received: by 10.55.33.215 with SMTP id f84mr11900021qki.60.1435389281529;
Sat, 27 Jun 2015 00:14:41 -0700 (PDT)
Received: by 10.140.91.37 with HTTP; Sat, 27 Jun 2015 00:14:41 -0700 (PDT)
In-Reply-To: <558E3EFD.9040602@ktorn.com>
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>
<558E3EFD.9040602@ktorn.com>
Date: Sat, 27 Jun 2015 00:14:41 -0700
Message-ID: <CACq0ZD5S6dDcBh9fsHCgbPJXom4vF8VymtHXogODjfD38RDNfA@mail.gmail.com>
From: Aaron Voisine <voisine@gmail.com>
To: Filipe Farinha <filipe@ktorn.com>
Content-Type: multipart/alternative; boundary=001a1144d2fa3d762505197a9cef
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,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] 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 07:14:43 -0000
--001a1144d2fa3d762505197a9cef
Content-Type: text/plain; charset=UTF-8
Also remember that the sender is not the one who cares about delays or even
getting confirmations at all, it's the receiver who's concerned with these
things. They have to tell the sender up-front what they're willing to
accept in exchange for goods and services.
Aaron Voisine
co-founder and CEO
breadwallet.com
On Fri, Jun 26, 2015 at 11:13 PM, Filipe Farinha <filipe@ktorn.com> wrote:
> 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
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
--001a1144d2fa3d762505197a9cef
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Also remember that the sender is not the one who cares abo=
ut delays or even getting confirmations at all, it's the receiver who&#=
39;s concerned with these things. They have to tell the sender up-front wha=
t they're willing to accept in exchange for goods and services.</div><d=
iv class=3D"gmail_extra"><br clear=3D"all"><div><div class=3D"gmail_signatu=
re"><div dir=3D"ltr"><div><div dir=3D"ltr"><div><br>Aaron Voisine</div><div=
>co-founder and CEO<br><a href=3D"http://breadwallet.com" target=3D"_blank"=
>breadwallet.com</a></div></div></div></div></div></div>
<br><div class=3D"gmail_quote">On Fri, Jun 26, 2015 at 11:13 PM, Filipe Far=
inha <span dir=3D"ltr"><<a href=3D"mailto:filipe@ktorn.com" target=3D"_b=
lank">filipe@ktorn.com</a>></span> wrote:<br><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex"><span class=3D"">On 27/06/2015 03:36, Peter Todd wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
* Make websites with easy to understand displays of what the current mempoo=
l<br>
=C2=A0 =C2=A0backlog is, and what fee/KB is needed to get to the front of t=
he queue. We've<br>
=C2=A0 =C2=A0done a great job for Bitcoin price charts, let's extend th=
at to transaction<br>
=C2=A0 =C2=A0fees.<br>
<br>
</blockquote></span>
+1<br>
<br>
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 impac=
t, both in terms of storage space as well as transaction volume spikes.<br>
<br>
Just recently I suggested the need for a BIP to standardize reporting of &q=
uot;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.<br>
<br>
<a href=3D"https://community.blockstack.org/t/blockstore-footprint-on-block=
chain/68/5?u=3Dktorn" rel=3D"noreferrer" target=3D"_blank">https://communit=
y.blockstack.org/t/blockstore-footprint-on-blockchain/68/5?u=3Dktorn</a><br=
>
<br>
IMHO keeping the users informed of potential issues before committing trans=
actions to the network can go a long way towards preventing frustration and=
potential backlashes against blockchain tech.<span class=3D"HOEnZb"><font =
color=3D"#888888"><br>
<br>
Filipe Farinha</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</div></div></blockquote></div><br></div>
--001a1144d2fa3d762505197a9cef--
|
