From: Melvin Carvalho <melvincarvalho@gmail•com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Total fees have almost crossed the block reward
Date: Mon, 12 Feb 2018 18:23:35 +0100 [thread overview]
Message-ID: <CAKaEYhJ5sMwBONR1AyYQg5PutwKO08UUGq=76XObk0M0Yt-raA@mail.gmail.com> (raw)
In-Reply-To: <CAKaEYhJ0vC8wf9yYjovfoZLB-TTvEnVB2a3mkC-YDzmnLwtz1Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2767 bytes --]
On 21 December 2017 at 22:30, Melvin Carvalho <melvincarvalho@gmail•com>
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.
>
Just following up on this, for no other reason than I've had my eyes glued
to these stats the last few weeks. I'll share a few more stats links.
Mempool has come down significantly, as have fees. Tho, of course, this
could spike any time.
https://bitinfocharts.com/bitcoin/
Typically fees are :
$2.06 on tx $543 (median) # 0.38%
$3.47 on tx $75,000 (mean) # 0.005%
Aside: An observation on this. High value transactors seems to be getting
a much better deal, than the mean. This lead me to ponder whether the
intuitive metric of satoshi/byte is, in fact, game theory optimal.
Possibly over the short term it is, but over a longer period, those wishing
to increase the longevity of proof of work in general might wish to
consider more progressive fee approaches. Naively, it might be possible to
imagine some kind of gaussian distribution that picks tx according to a
blended combination of sats/byte and %transacted. Perhaps something for
miners and fee estimation algorithms to develop over time.
Segwit adoption has increased, and anecdotal evidence shows that trend to
continue. The release of 0.16 will I think also have a positive effect.
Finally, I came across this wonderful site that shows lightning network
adoption on mainnet
http://shabang.io/
LN is increasing well. Some blocks are not far off 1% lightning funding,
which I think bodes well. I'll go out on a limb and predict that over 1%
of btc tx will be lightning based by year end.
Since such posts are not strictly development, I'll keep them to a
minimum. However, I hope these stats provide useful data points for
project evolution.
[-- Attachment #2: Type: text/html, Size: 3748 bytes --]
next prev parent reply other threads:[~2018-02-12 17:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-21 21:30 Melvin Carvalho
2017-12-21 22:02 ` Jameson Lopp
2017-12-21 22:18 ` Jim Rogers
2017-12-21 23:15 ` Michel 'ic' Luczak
2017-12-21 22:44 ` Gregory Maxwell
2017-12-21 23:35 ` Paul Iverson
2017-12-22 0:30 ` Mark Friedenbach
2017-12-22 1:15 ` Gregory Maxwell
2018-02-12 17:23 ` Melvin Carvalho [this message]
2018-02-12 17:47 ` rhavar
2018-02-12 18:12 ` Peter Todd
2018-02-12 19:41 ` Christian Decker
2018-02-13 19:03 ` Peter Todd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKaEYhJ5sMwBONR1AyYQg5PutwKO08UUGq=76XObk0M0Yt-raA@mail.gmail.com' \
--to=melvincarvalho@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox