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
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
|
Return-Path: <jim.rogers.907@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 69AC55AA
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 21 Dec 2017 22:18:39 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-pf0-f173.google.com (mail-pf0-f173.google.com
[209.85.192.173])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 92CF93D9
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 21 Dec 2017 22:18:38 +0000 (UTC)
Received: by mail-pf0-f173.google.com with SMTP id n6so14521668pfa.4
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 21 Dec 2017 14:18:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=from:to:references:in-reply-to:subject:date:message-id:mime-version
:thread-index:content-language;
bh=WH6SIbyAj4EqRK/+AVL9KHSyDkjPHpesjyPaoM1I9j4=;
b=gaWwJraQMFDj/WJ6WjGqqgDPSj3jMag/zzywd0Eh/1DKTUjl2k9RSd4FwXMuXcViUu
3W3BQk32NmzUdVW5SawpoOvHaclNLDVr5LMrVk8C4iYvyyG7VkzDPl3oOhbW9KG38EZC
xV57iSmlatUpPFZ1JUJYVnVUQ7bbjuForcbsfBUMqa4Shoj1WQHqbv350Hbf0oTgOmJC
1Ej6kKFUpLzmhLXR0nudfsJ1pjgAA2kzzpPnNqG+nsEO/4rMPvU/j4htvVGTg042jql+
GNLmHJrYfvAJhSavCQCf+Wu84ue8kaE5htbpAmnbz+4bxZIjwv5dw9evu918V4uQmwDC
6XYQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:from:to:references:in-reply-to:subject:date
:message-id:mime-version:thread-index:content-language;
bh=WH6SIbyAj4EqRK/+AVL9KHSyDkjPHpesjyPaoM1I9j4=;
b=rMr6rXjOuM9weddUQ/nfpiDoxbB1maHY/wGVo1VvrceQg97568x/oTGYxhos+Mkvqd
04EfKCmh6y8qCWcR9okvtRGmpIKChISDE83dUKQnIVbpAI5I8TiIUDCpUS8VLHMvQqIF
rzykl5OFqseI/dFSczGZZfWUWqoT2X82nH6HbkZwNEnC/5xcdLemq9EMTjkrl5eMXBhW
hlJG7LxVdnI3rdkwCBbusYn6FtwgNnuyXLvTGA/8S0C9gtVRQiM31zCc2Mx374WivbFJ
ci4xBU2wjLqojAAQ9rKrCWaajIu40UsRssR4bPXdoE7d4ciTE0ZQQw/vtWoM2BgMVXC7
HBdg==
X-Gm-Message-State: AKGB3mK2vPeTo6QJgzTH0rFB8jC99eVPAl6DbuWwGbkXlaiFZPjejzQ8
PtYiNi7kAm6qRRMULTy37JegqMbo
X-Google-Smtp-Source: ACJfBos99/9bihJYgmk4JklTSPAdWH2Q3I917TROVN0aSCxyCZQoAURllLqERqekZ7JwQwywu8TQ/g==
X-Received: by 10.101.73.2 with SMTP id p2mr1695482pgs.107.1513894717881;
Thu, 21 Dec 2017 14:18:37 -0800 (PST)
Received: from PC624 ([12.17.138.216]) by smtp.gmail.com with ESMTPSA id
b127sm34084127pgc.70.2017.12.21.14.18.36
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Thu, 21 Dec 2017 14:18:37 -0800 (PST)
From: "Jim Rogers" <jim.rogers.907@gmail.com>
To: "'Jameson Lopp'" <jameson.lopp@gmail.com>,
"'Bitcoin Protocol Discussion'" <bitcoin-dev@lists.linuxfoundation.org>
References: <CAKaEYhJ0vC8wf9yYjovfoZLB-TTvEnVB2a3mkC-YDzmnLwtz1Q@mail.gmail.com>
<CADL_X_fw01-PfyTPXqYAyzwV9CO8tPLrd1_eZu16Z_kz-xM7LQ@mail.gmail.com>
In-Reply-To: <CADL_X_fw01-PfyTPXqYAyzwV9CO8tPLrd1_eZu16Z_kz-xM7LQ@mail.gmail.com>
Date: Thu, 21 Dec 2017 13:18:32 -0900
Message-ID: <002d01d37aa9$a513db40$ef3b91c0$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_002E_01D37A5E.352D92D0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQD3yV1mlUzXxzoBKOUW+y4fiFBoGgGxCEd+pPg3TgA=
Content-Language: en-us
X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,
HTML_MESSAGE,RCVD_IN_DNSWL_NONE,URIBL_RED autolearn=no version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Mailman-Approved-At: Thu, 21 Dec 2017 22:31:45 +0000
Subject: Re: [bitcoin-dev] Total fees have almost crossed the block reward
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol 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: Thu, 21 Dec 2017 22:18:39 -0000
This is a multipart message in MIME format.
------=_NextPart_000_002E_01D37A5E.352D92D0
Content-Type: text/plain;
charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
It seems that the exchanges are doing everything that they can to slow =
things. Not only have the major exchanges not implemented segwit yet, =
but a bigger, less addressed issue is that they have start applying =
transfer limits on crypto as well as cash. They do not respond for =
months to requests to upgrade limits, and this results in many =
transactions instead of one to transfer crypto to cold storage devices.=20
=20
These issues may self-resolve over time, since I think they are all =
impacted by KYC and the explosive growth.=20
=20
=20
From: bitcoin-dev-bounces@lists.linuxfoundation.org =
[mailto:bitcoin-dev-bounces@lists.linuxfoundation.org] On Behalf Of =
Jameson Lopp via bitcoin-dev
Sent: Thursday, December 21, 2017 1:03 PM
To: Melvin Carvalho <melvincarvalho@gmail.com>; Bitcoin Protocol =
Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Total fees have almost crossed the block =
reward
=20
I'd hope that the incentives are in place to encourage high volume =
senders to be more efficient in their use of block space by batching =
transactions and implementing SegWit, though this may not be the case =
for providers that pass transaction fees along to their users.
=20
We've been trying to be more proactive about outreach regarding =
efficient use of block space to our own customers at BitGo - when we =
break down the cost savings of implementing a new technique, it =
generally helps to hasten their adoption. I suspect that in many cases =
this is an issue of education - we should be more proactive in calling =
out inefficient uses of block space.
=20
Good resources to bookmark and share:
=20
https://bitcointechtalk.com/saving-up-to-80-on-bitcoin-transaction-fees-b=
y-batching-payments-4147ab7009fb
=20
https://blog.zebpay.com/how-zebpay-reduced-bitcoin-transaction-fees-a9e24=
c788598
=20
- Jameson
=20
On Thu, Dec 21, 2017 at 4:30 PM, Melvin Carvalho via bitcoin-dev =
<bitcoin-dev@lists.linuxfoundation.org =
<mailto:bitcoin-dev@lists.linuxfoundation.org> > wrote:
I asked adam back at hcpp how the block chain would be secured in the =
long term, once the reward goes away. The base idea has always been =
that fees would replace the block reward.
At that time fees were approximately 10% of the block reward, but have =
now reached 45%, with 50% potentially being crossed soon
https://fork.lol/reward/feepct
While this bodes well for the long term security of the coin, I think =
there is some legitimate concern that the fee per tx is prohibitive for =
some use cases, at this point in the adoption curve.
Observations of segwit adoption show around 10% at this point
http://segwit.party/charts/
Watching the mempool shows that the congestion is at a peak, though it's =
quite possible this will come down over the long weekend. I wonder if =
this is of concern to some.
https://dedi.jochen-hoenicke.de/queue/more/#24h
I thought these data points may be of interest and are mainly FYI. =
Though if further discussion is deemed appropriate, it would be =
interesting to hear thoughts.
_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org =
<mailto:bitcoin-dev@lists.linuxfoundation.org>=20
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
=20
------=_NextPart_000_002E_01D37A5E.352D92D0
Content-Type: text/html;
charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 15 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal>It seems =
that the exchanges are doing everything that they can to slow things. =
Not only have the major exchanges not implemented segwit yet, but a =
bigger, less addressed issue is that they have start applying transfer =
limits on crypto as well as cash. They do not respond for months to =
requests to upgrade limits, and this results in many transactions =
instead of one to transfer crypto to cold storage devices. =
<o:p></o:p></p><p class=3DMsoNormal><o:p> </o:p></p><p =
class=3DMsoNormal>These issues may self-resolve over time, since I think =
they are all impacted by KYC and the explosive growth. <o:p></o:p></p><p =
class=3DMsoNormal><o:p> </o:p></p><p =
class=3DMsoNormal><o:p> </o:p></p><p class=3DMsoNormal><b>From:</b> =
bitcoin-dev-bounces@lists.linuxfoundation.org =
[mailto:bitcoin-dev-bounces@lists.linuxfoundation.org] <b>On Behalf Of =
</b>Jameson Lopp via bitcoin-dev<br><b>Sent:</b> Thursday, December 21, =
2017 1:03 PM<br><b>To:</b> Melvin Carvalho =
<melvincarvalho@gmail.com>; Bitcoin Protocol Discussion =
<bitcoin-dev@lists.linuxfoundation.org><br><b>Subject:</b> Re: =
[bitcoin-dev] Total fees have almost crossed the block =
reward<o:p></o:p></p><p class=3DMsoNormal><o:p> </o:p></p><div><p =
class=3DMsoNormal>I'd hope that the incentives are in place to encourage =
high volume senders to be more efficient in their use of block space by =
batching transactions and implementing SegWit, though this may not be =
the case for providers that pass transaction fees along to their =
users.<o:p></o:p></p><div><p =
class=3DMsoNormal><o:p> </o:p></p></div><div><p =
class=3DMsoNormal>We've been trying to be more proactive about outreach =
regarding efficient use of block space to our own customers at BitGo - =
when we break down the cost savings of implementing a new technique, it =
generally helps to hasten their adoption. I suspect that in many cases =
this is an issue of education - we should be more proactive in calling =
out inefficient uses of block space.<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p> </o:p></p></div><div><p =
class=3DMsoNormal>Good resources to bookmark and =
share:<o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p> </o:p></p></div><div><p =
class=3DMsoNormal><a =
href=3D"https://bitcointechtalk.com/saving-up-to-80-on-bitcoin-transactio=
n-fees-by-batching-payments-4147ab7009fb">https://bitcointechtalk.com/sav=
ing-up-to-80-on-bitcoin-transaction-fees-by-batching-payments-4147ab7009f=
b</a><o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p> </o:p></p></div><div><p =
class=3DMsoNormal><a =
href=3D"https://blog.zebpay.com/how-zebpay-reduced-bitcoin-transaction-fe=
es-a9e24c788598">https://blog.zebpay.com/how-zebpay-reduced-bitcoin-trans=
action-fees-a9e24c788598</a><o:p></o:p></p></div><div><p =
class=3DMsoNormal><o:p> </o:p></p></div><div><p class=3DMsoNormal>- =
Jameson<o:p></o:p></p></div></div><div><p =
class=3DMsoNormal><o:p> </o:p></p><div><p class=3DMsoNormal>On Thu, =
Dec 21, 2017 at 4:30 PM, Melvin Carvalho via bitcoin-dev <<a =
href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" =
target=3D"_blank">bitcoin-dev@lists.linuxfoundation.org</a>> =
wrote:<o:p></o:p></p><blockquote style=3D'border:none;border-left:solid =
#CCCCCC 1.0pt;padding:0in 0in 0in =
6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><div><div><div><div><=
p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>I asked adam back at =
hcpp how the block chain would be secured in the long term, once the =
reward goes away. The base idea has always been that fees would =
replace the block reward.<o:p></o:p></p></div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'>At that time fees were approximately 10% =
of the block reward, but have now reached 45%, with 50% potentially =
being crossed soon<br><br><a href=3D"https://fork.lol/reward/feepct" =
target=3D"_blank">https://fork.lol/reward/feepct</a><o:p></o:p></p></div>=
<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'>While this bodes =
well for the long term security of the coin, I think there is some =
legitimate concern that the fee per tx is prohibitive for some use =
cases, at this point in the adoption curve.<o:p></o:p></p></div><p =
class=3DMsoNormal style=3D'margin-bottom:12.0pt'>Observations of segwit =
adoption show around 10% at this point<br><br><a =
href=3D"http://segwit.party/charts/" =
target=3D"_blank">http://segwit.party/charts/</a><o:p></o:p></p></div><p =
class=3DMsoNormal style=3D'margin-bottom:12.0pt'>Watching the mempool =
shows that the congestion is at a peak, though it's quite possible this =
will come down over the long weekend. I wonder if this is of =
concern to some.<br><br><a =
href=3D"https://dedi.jochen-hoenicke.de/queue/more/#24h" =
target=3D"_blank">https://dedi.jochen-hoenicke.de/queue/more/#24h</a><o:p=
></o:p></p></div><p class=3DMsoNormal>I thought these data points may be =
of interest and are mainly FYI. Though if further discussion is =
deemed appropriate, it would be interesting to hear =
thoughts.<o:p></o:p></p></div><p class=3DMsoNormal =
style=3D'margin-bottom:12.0pt'><br>______________________________________=
_________<br>bitcoin-dev mailing list<br><a =
href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.l=
inuxfoundation.org</a><br><a =
href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
target=3D"_blank">https://lists.linuxfoundation.org/mailman/listinfo/bitc=
oin-dev</a><o:p></o:p></p></blockquote></div><p =
class=3DMsoNormal><o:p> </o:p></p></div></div></body></html>
------=_NextPart_000_002E_01D37A5E.352D92D0--
|