From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137]) by lists.linuxfoundation.org (Postfix) with ESMTP id 01817C000E for ; Mon, 5 Jul 2021 16:39:55 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp4.osuosl.org (Postfix) with ESMTP id D56EC40310 for ; Mon, 5 Jul 2021 16:39:55 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org X-Spam-Flag: NO X-Spam-Score: -1.65 X-Spam-Level: X-Spam-Status: No, score=-1.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no Received: from smtp4.osuosl.org ([127.0.0.1]) by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LKEDvfRdKPai for ; Mon, 5 Jul 2021 16:39:54 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.8.0 Received: from mail-lf1-f45.google.com (mail-lf1-f45.google.com [209.85.167.45]) by smtp4.osuosl.org (Postfix) with ESMTPS id 4D667402D3 for ; Mon, 5 Jul 2021 16:39:54 +0000 (UTC) Received: by mail-lf1-f45.google.com with SMTP id t17so33518823lfq.0 for ; Mon, 05 Jul 2021 09:39:54 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=HVN6oVNFsiTDdgMVVnx4j2clAvCgFa5GZynxmgDjUNE=; b=XqtuBgNTlggYcWuOOnYgOcO5kHPdgTjD3kpOSkES7uhST9cK9Vg8kExjhIdNfjgUrj nXwUUmuxb80UlQdvb+zOgLnFV7Th1tkY2znkRtMCAfNclaKdhiBLSVX04Fnv6BjRUdHZ 81dyjjMrlVK6b8rdiboDFR3+7ZQodA++MQrZb2vROdymMaTvLl1u7KCWJO6R0QYn3BoW ML5/gFDkvUXfyFpAePwD0sui0HH7yViZigZfPKZLmPB4tRIzMQCBJCsif3uvURLZ62H+ tlCBTUDUw/Zv9sHlmdeZ6uxEFdmm/WqyMqqrtOSTPWtOvG69HY+cEjZFsP36NBEL8ZNe 5mqg== X-Gm-Message-State: AOAM531m2KWTdkLRs7DUhR3yUMMyU6FN9AaQbE7mMZ/CIFxlphICn+9S kMKrtjKiKW3LqYKNviMgZeOUzGb+oAJemfT7G6miotxSzF4= X-Google-Smtp-Source: ABdhPJylDkDJDcAvsI+LdmogLXZ1AERKuUYUlY4tiZOlA8lZvvlZnIPU3eWvR4lk9NRkG1rQx698L4RsuCTc5K/qILA= X-Received: by 2002:a05:6512:3144:: with SMTP id s4mr6668132lfi.169.1625503191924; Mon, 05 Jul 2021 09:39:51 -0700 (PDT) MIME-Version: 1.0 From: Dave Scotese Date: Mon, 5 Jul 2021 09:39:40 -0700 Message-ID: To: Bitcoin Dev Content-Type: multipart/alternative; boundary="00000000000056041505c662f4e4" Subject: [bitcoin-dev] Fee estimation requirements X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jul 2021 16:39:56 -0000 --00000000000056041505c662f4e4 Content-Type: text/plain; charset="UTF-8" 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. --00000000000056041505c662f4e4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
At=C2=A0https://github.com/bitcoin/bitcoin/issues/= 22404#issuecomment-874168305 no explanation is given for a peculiar rul= e about estimating fees, that "you have to wait around for a couple of blocks=C2=A0after=C2=A0being synced bef= ore fee estimation will work."=C2=A0 The rule is true, but it n= eedn't be true, and the software would be more useful if it were not tr= ue.=C2=A0 If it does seem impossible to break this rule, perhaps some brain= storming is in order.=C2=A0 I estimate fees quite often on my own, although= I am trusting the block explorers in their reporting of the fees for the m= ost recent blocks.=C2=A0 The software doesn't need to trust anything on= ce it has been synced.

If this is simply a matter of pri= orities, it would be useful to point that out.

Dav= e.
--00000000000056041505c662f4e4--