feat: Add mempool-based fee estimation dashboard

[b-l-u-e]

Overview

This PR implements a comprehensive mempool-based fee estimation dashboard for Bitcoin Core.

Features Added

• Dashboard: Real-time mempool visualization with block templates
• Analytics: Detailed fee estimation metrics and comparisons

Key Components using dummy data for now

• Block template visualization showing KWU (Kiloweight Units)
• Real-time fee rate estimation using mempool data
• Performance metrics comparing current vs mempool-based methods

Technical Details

• Frontend: Next.js 14, TypeScript, Tailwind CSS

[ismaelsadeeq]

Really nice work.

High-Level Feedback

• The initial page feels redundant; the landing page should just be the live dashboard.
• The performance metrics currently on the landing page should be moved to the analytics page.

Dashboard

• The heading and text on the dashboard are also redundant.
• I also noticed tt’s challenging to differentiate between the block weight and the removed mempool transaction weight; the numbers are not easy to parse for users 3.8 KWU 3.6KWU what are they? (thinking as the user).
• The blocks height should be more than the width. Hence the blocks can remain rectangular but oriented vertically. Let’s try two blocks: the actual block weight at the bottom and the removed transactions weight at the top. When hovering over or clicking the bottom block, it should become the focus point.
• Low priority, but note: the blocks can be shown as a set of six (similar to what the fee estimator keeps). We could save that data and allow the user to view as many as they want.
• I like the inclusion of transaction size, total fees, size, and block height fields.

Analytics

• For some reason, the analytics page crashes.

Once the approach is finalized, commits should be atomic, with each individual feature separated for easier review.

[b-l-u-e]

Thank you for your feedback.. I will work on the changes suggested

[ismaelsadeeq]

Thanks for the update.

• I think overall this approach looks good. I like the current update the top of the rectangle should display the block heights instead of the current texts,

• The live fee estimate is missing the forecaster.

• Replace "current" with Block Weight, "target" should be something like (Block Txs In Mempool, In Mempool) or similar.

• Better percentages should be in green I think :), and red should indicate lower percentages.

-Anyway, we can spend more time on the nitty-gritty of the page later. For now, this looks good. Feel free to move on to implementing the analytics page. You also choose to integrate it the initial page with the API :) and suggest ways to make it better.

[b-l-u-e]

Referencing PR#2 done by @mercie-ux : relocated the backend-analytics code into the main backend (Flask) in this PR. The new /analytics/mempool-health endpoint now lives in backend/app.py (local mode via getblockstats, optional external source), and the shared DB helpers (database.py) and collector continue to feed fee_analysis.db

Fixed estimatesmartfee calls to use the correct signature and include warnings.
Adjusted getblocktemplate to use {"mode":"template","rules":["segwit","signet"]} for signet.
json_rpc_request.py mempool estimator now returns structured results (with warnings) when templates are empty instead of 500s.
Collector hardening: removed unused imports, ensured percentiles are padded, kept DB helpers (database.py) for init/insert/summary.

Frontend
Dashboard: simplified dark/amber theme, shows chain, mempool/historical components, and clearer warnings.
Stats: simplified layout, mempool health controls, performance metrics now display whenever summary is present (even small data); removed bulky analysis/roadmap panels.
Block template visuals now show “n/a sat/vB” if fee rates are missing.

for the performance metrics should Run the collector.py (from backend/):
source .venv/bin/activate (if you use the venv)
python collector.py
First run does an initial few-block fill, then continuous updates.
Watch the log for [COLLECTOR] Processed Block … lines.
After it processes blocks, hit /analytics/summary?window=1000 (or refresh the stats page). The cards will show real percentages once rows exist.

[ismaelsadeeq]

Superseded by https://github.com/ismaelsadeeq/bitcoin-core-fees/pull/4, thanks.