public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Gregory Maxwell <greg@xiph.org>
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
Date: Thu, 21 Dec 2017 22:44:32 +0000	[thread overview]
Message-ID: <CAAS2fgQSNdzuiPS3AZ_TjQ2OvkhYJ3ZJUBo7ovP6_O2snuwEMg@mail.gmail.com> (raw)
In-Reply-To: <CAKaEYhJ0vC8wf9yYjovfoZLB-TTvEnVB2a3mkC-YDzmnLwtz1Q@mail.gmail.com>

Personally, I'm pulling out the champaign that market behaviour is
indeed producing activity levels that can pay for security without
inflation, and also producing fee paying backlogs needed to stabilize
consensus progress as the subsidy declines.

I'd also personally prefer to pay lower fees-- current levels even
challenge my old comparison with wire transfer costs-- but we should
look most strongly at difficult to forge market signals rather than
just claims-- segwit usage gives us a pretty good indicator since most
users would get a 50-70% fee reduction without even considering the
second order effects from increased capacity.

As Jameson Lopp notes, more can be done for education though-- perhaps
that market signal isn't efficient yet. But we should get it there.

But even independently of segwit we can also look at other inefficient
transaction styles: uncompressed keys, unconfirmed chaining instead of
send many batching, fee overpayment, etc... and the message there is
similar.

I've also seen some evidence that a portion of the current high rate
congestion is contrived traffic. To the extent that it's true there
also should be some relief there soon as the funding for that runs
out, in addition to expected traffic patterns, difficulty changes,
etc.


On Thu, Dec 21, 2017 at 9:30 PM, Melvin Carvalho via bitcoin-dev
<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
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>


  parent reply	other threads:[~2017-12-21 22:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-21 21:30 [bitcoin-dev] Total fees have almost crossed the block reward 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 [this message]
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
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=CAAS2fgQSNdzuiPS3AZ_TjQ2OvkhYJ3ZJUBo7ovP6_O2snuwEMg@mail.gmail.com \
    --to=greg@xiph.org \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=melvincarvalho@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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