From: Greg Tonoski <gregtonoski@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Call for reconfiguration of nodes to relay transactions with fee-rates below 1 sat/vbyte
Date: Fri, 31 Jan 2025 09:49:44 +0100 [thread overview]
Message-ID: <CAMHHROxVo_7ZRFy+nq_2YzyeYNO1ijR_r7d89bmBWv4f4wb9=g@mail.gmail.com> (raw)
The minrelaytxfee default value of 1000/kvB (1 sat/vbyte) has been set
in Bitcoin nodes since 2013 or earlier. In 2013, 1000 sats were priced
at $0.01, today it is about 100 times more. Wouldn't you like to
consider adjusting your node configuration and lower the hurdle,
perhaps? I would suggest setting minrelaytxfee=0.00000001 (which
translates to 0.001 sat/vbyte) as a rule of thumb. The value could be
set in a bitcoin.conf file. There is negligible number of such
reconfigured nodes relaying transactions with fee-rates below 1
sat/vbyte currently.
There is the intention to unblock transactions with fee-rate below 1
sat/vbyte in Bitcoin. Probably consolidation and multisig types of
transactions would benefit the most.
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/CAMHHROxVo_7ZRFy%2Bnq_2YzyeYNO1ijR_r7d89bmBWv4f4wb9%3Dg%40mail.gmail.com.
next reply other threads:[~2025-01-31 11:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 8:49 Greg Tonoski [this message]
2025-01-31 12:54 ` [bitcoindev] Call for reconfiguration of nodes to relay transactions with fee-rates below 1 sat/vbyte Sjors Provoost
2025-01-31 13:43 ` Greg Tonoski
2025-01-31 14:40 ` Sjors Provoost
2025-01-31 15:13 ` Sjors Provoost
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='CAMHHROxVo_7ZRFy+nq_2YzyeYNO1ijR_r7d89bmBWv4f4wb9=g@mail.gmail.com' \
--to=gregtonoski@gmail.com \
--cc=bitcoindev@googlegroups.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