public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Dan Bryant <dkbryant@gmail.com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] Time to lower minrelaytxfee ?
Date: Fri, 21 Aug 2020 00:55:59 -0500	[thread overview]
Message-ID: <CAAUFj113g15EUXvdQG1caLBar6HakLRag6URA9Q-y52OZEmhzQ@mail.gmail.com> (raw)

It's been 5 years since minrealytxfee was lowered.  At the time
bitcoin was trading for $255 and it was agreed that the fee of 5000
sat/vkB was too high.  It was lowered to 1000 sat/vkB.  In regards to
how much anti-DoS protection that provided, it comes out to $0.00255 /
vkB in USD terms.  To have parity with the last reduction, we would
need to reduce minrealytxfee to 22 sat/vKB, though an even more
conservative reduction to 100 or 50 sat/vKB would be welcome.

With the growing adoption of LN, there is a need for ultra-low-fee
on-chain TXNs.  Having these queue and confirm overnight, or even
waiting until the Sunday lull would still probably be welcome to many
users.  The fact that the mempool is going empty at least every week
indicates that miners have not reached the floor of what they are
willing to mine.

About 2 years ago there was a PR (#13922) to try to make a reduction
from 1000 to 200 sat/vkB.  It was widely accepted but the submitter
eventually closed it in favor of PR #13990.

If minrelaytxfee is already parameterized and configurable in
bitcoin.conf, how could it be detrimental to operation of a node to
change the default?

References:

* https://github.com/bitcoin/bitcoin/commit/9e93640be6c49fa1505ba5c5df8c89210da5a6e4
* https://github.com/bitcoin/bitcoin/pull/13922
* https://github.com/bitcoin/bitcoin/pull/13990


             reply	other threads:[~2020-08-21  5:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-21  5:55 Dan Bryant [this message]
2020-08-21 16:36 ` [bitcoin-dev] Time to lower minrelaytxfee ? Nadav Ivgi
2020-08-21 16:57 ` Greg Sanders

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=CAAUFj113g15EUXvdQG1caLBar6HakLRag6URA9Q-y52OZEmhzQ@mail.gmail.com \
    --to=dkbryant@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /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