From 1aad89ac97c08504aafbebd994574ec9747c94ed Mon Sep 17 00:00:00 2001 From: hunicus <93150691+hunicus@users.noreply.github.com> Date: Mon, 6 Jun 2022 12:29:02 -0400 Subject: [PATCH] Update fee faq --- frontend/src/app/docs/api-docs/api-docs-data.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/frontend/src/app/docs/api-docs/api-docs-data.ts b/frontend/src/app/docs/api-docs/api-docs-data.ts index eb98c6596..1927c62d9 100644 --- a/frontend/src/app/docs/api-docs/api-docs-data.ts +++ b/frontend/src/app/docs/api-docs/api-docs-data.ts @@ -6107,7 +6107,7 @@ export const faqData = [ showConditions: bitcoinNetworks, fragment: "looking-up-fee-estimates", title: "How can I look up fee estimates?", - answer: "
See real-time fee estimates on the main dashboard.
Low priority is suggested for confirmation within 6 blocks (~1 hour), Medium priority is suggested for confirmation within 3 blocks (~30 minutes), and High priority is suggested for confirmation in the next block (~10 minutes).
" + answer: "See real-time fee estimates on the main dashboard.
Here is an overview of Mempool's feerate suggestions:
In all cases, the suggested feerate is adjusted lower if any of the projected blocks involved in the calculation are not full (e.g. if there is only 1 projected block with a size of 1.2 MWU, Mempool will suggest a feerate of 1 sat/vB—not the median feerate of transactions in the block).
Projected blocks use feerates, transaction sizes, and other metrics to forecast which transactions will be in future blocks. Actual blocks will turn out to be different: miners have their own views of the mempool, their own algorithms for determining which transactions to include in a block, etc.
Ultimately, the Bitcoin network is not perfectly predictable, so fee estimation cannot be perfectly precise.
Use Mempool's feerate suggestions as a guide, and understand that they do not guarantee transaction confirmation in any period of time.
" }, { type: "endpoint",