From: Alex Morcos <morcos@gmail•com>
To: st-bind@posteo•de,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Idea: More decimal places for lower minimum fee
Date: Thu, 10 May 2018 09:05:27 -0400 [thread overview]
Message-ID: <CAPWm=eUP=Q0k7ahM-g2g4hUkGKaPd6C4-4jA0Xbnn_wRLqWNQA@mail.gmail.com> (raw)
In-Reply-To: <f3683e4eb1b51d75476564a5b4f51651@posteo.de>
[-- Attachment #1: Type: text/plain, Size: 1296 bytes --]
Fee rates in Bitcoin Core are measured in satoshis/kB. There are a couple
places where a minimum of 1000 satoshis/kB is assumed.
Setting "incrementalrelayfee" to a smaller than default value and either
leaving "minrelaytxfee" unset or also setting it smaller will be sufficient
to allow your node to accept and relay transactions with smaller fee
rates. Of course without the rest of the network making these changes
and/or the miners being willing to mine those transactions, it won't be of
much benefit.
Fee estimation doesn't distinguish fee rates less than 1000 sats/kB. This
would be more substantial to change.
On Thu, May 10, 2018 at 4:10 AM, st-bind--- via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> Currently, the minimum fee of 1 satoshi per byte corresponds to about 0.09
> USD per kB, which is no longer insignificant. Maybe the time has come now
> to introduce more decimal places and make the minimum fee 1 of the new
> smallest unit. This way, everyday payments would again be possible with
> virtually no fee without flooding the mempool with free spam transactions.
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 1925 bytes --]
prev parent reply other threads:[~2018-05-10 13:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 8:10 st-bind
2018-05-10 13:05 ` Alex Morcos [this message]
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='CAPWm=eUP=Q0k7ahM-g2g4hUkGKaPd6C4-4jA0Xbnn_wRLqWNQA@mail.gmail.com' \
--to=morcos@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=st-bind@posteo$(echo .)de \
/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