From: Dave Scotese <dscotese@litmocracy•com>
To: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Fee estimation requirements
Date: Mon, 5 Jul 2021 09:39:40 -0700 [thread overview]
Message-ID: <CAGLBAhd+s9SurpSK+DAFv9t46hRtF7CEQr_XMO7L_aia95c9+Q@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 739 bytes --]
At https://github.com/bitcoin/bitcoin/issues/22404#issuecomment-874168305
no explanation is given for a peculiar rule about estimating fees, that "you
have to wait around for a couple of blocks *after* being synced before fee
estimation will work." The rule is true, but it needn't be true, and the
software would be more useful if it were not true. If it does seem
impossible to break this rule, perhaps some brainstorming is in order. I
estimate fees quite often on my own, although I am trusting the block
explorers in their reporting of the fees for the most recent blocks. The
software doesn't need to trust anything once it has been synced.
If this is simply a matter of priorities, it would be useful to point that
out.
Dave.
[-- Attachment #2: Type: text/html, Size: 1553 bytes --]
reply other threads:[~2021-07-05 16:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAGLBAhd+s9SurpSK+DAFv9t46hRtF7CEQr_XMO7L_aia95c9+Q@mail.gmail.com \
--to=dscotese@litmocracy$(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