Total Donations

[2ndtlmining]

On the home screen
Sum total of all the donations in the last year to the Donar addresses (should be 2)
Amount of unique donars and the sum total. Also show the last donation

[2ndtlmining]

Scoped this out against the live chain before building, and the real numbers raise a design decision worth settling first.

What the data actually looks like

Scanned both donation addresses (t1aUmu7HDr7BtwmdR1Y9i2K6KFRZs4Bumbt current, t1ebxupkNYVQiswfwi7xBTwwKtioJqwLmUG pre-2026-09-03), deduped by txid, on 2026-09-12:

	Last 365 days	All time
Total	91,225.07 FLUX	94,694.05 FLUX
Unique donors	10	63
Donation txs	23	94

Last donation: 1.00 FLUX, 2026-08-09.

The problem: one wallet is 99.1% of the last year

90,440.07  t1gesjNJGfzU8shfMZj6DVDatRKA3LQj8Nh   <-- 99.1% of the total
   500.00  t1cDcyWN8CHFAm5sd36Dovqf73rsURP3tck
   100.00  t1VWFxF8RDzpH8YgXyCDmwRS7ikWVCXvcBX
    50.00  t1JprekhQLq2GXBuonotzt88ukNj5LRv8dF
    50.00  t3Yt7EFUkFJsGDsr8St2KgjZxKK8FiwS5Gi
    45.00  t1X1hKAb9rYmsikPKVJXBHueJU4VeuV7Tbb
    20.00  t1dKfgfuj28cYT1hwWSTycCcsV4o7ksRoXc
    10.00  t1e4sQRcuHdoMXuebzzCeXumJhMaxRcsrDF

Everything except that one wallet adds up to 785 FLUX across 9 donors.

A panel headlining "91,225 FLUX donated" on a page about transparency would imply broad community backing that the data does not show. If that top wallet is the project's own address moving funds — which the size and pattern suggest — then publishing it as a donation total is the opposite of transparent. This needs a call before the panel is built, because it decides what the headline number even is.

Three other things the data forces:

1. The 365-day window flatters nothing. 10 donors in the last year vs 63 all-time. Showing only the last year hides most of the project's actual support history.
2. "Last donation" is a month old. A prominent "Last donation: 2026-08-09" risks reading as "this project is abandoned". It needs a design that degrades well when donations are sparse — relative time ("5 weeks ago") plus context, not a bare date.
3. 23 transactions from 10 donors is a small enough dataset that a chart would be mostly whitespace. This wants well-designed stat tiles and a short recent-donations list, not a graph.

Plumbing

Most of the hard part exists. api/globalStats.js's fetch_total_donations() already scans both addresses, paginates, routes through the explorer pool with 429 failover, dedupes by txid, and keeps "explorer unreachable" distinguishable from "no donations" (see #213/#196 for why each of those matters). It returns a transaction count for one wallet, because achievements gate on that.

This feature needs the same scan aggregated differently — network-wide sum, unique senders, most recent. So: extract the scan, add an aggregate alongside the existing per-wallet count, don't duplicate the scan logic. The aggregate is pure over captured tx data, so it unit-tests cleanly.

Note the old address is 18 pages and DONOR_MAX_PAGES_FETCHED is 20 — close enough to the cap to be worth a deliberate decision rather than inheriting it by accident.

Placement

This belongs on Home and does not conflict with #242. #242's agreed direction is to repurpose Home toward donor-feature promotion once its network panels move to the Network tab — a donations-transparency panel is exactly that content, so it will stay put rather than being built twice.

Slotting it as its own wave after the small-UI batch (#246/#247/#248/#255) and before the Network tab rebuild (#254/#242).

[2ndtlmining]

Decisions from the maintainer — scope is now settled, and it grew a second half.

1. Exclude t1gesjNJGfzU8shfMZj6DVDatRKA3LQj8Nh

That address is the maintainer's own wallet, not a third-party donation. Excluding it changes the headline from a misleading 91,225 FLUX to the real community figure:

785 FLUX from 9 donors, last 365 days.

Implementation note: it goes in a neutrally-named constant (e.g. EXCLUDED_FROM_DONATION_TOTALS) with a comment explaining only that these are project-owned addresses whose transfers are not third-party donations — no need to characterise whose wallet it is. Same list should be reusable if more project addresses appear later.

2. Window: last 365 days, as originally specified

All-time (63 donors / 94,694 FLUX) stays out of scope.

3. NEW — per-wallet donation status, both states

The insight driving this: most people arrive at the node site, paste a wallet, and watch their nodes. That is the moment to say something about donating.

• Has donated → acknowledge it. A "Donor" badge already exists next to Current Wallet Address on /nodes, so this half is partly built — it needs the visual treatment brought up to match the new panel.
• Has not donated → the missing half. A distinct icon and a warm, non-nagging ask, roughly "Finding this data useful? Consider supporting development." Not a guilt trip, not a modal, not something that fires on every page load.

Both states need a proper icon and considered wording — this is the part that has to feel designed rather than bolted on. The not-donated state is shown to the majority of visitors, so getting its tone right matters more than the donated state.

Design constraints worth stating up front:

• It must not shout. This sits on a dashboard people use daily; anything animated or dismissible-but-recurring will be hated.
• It must degrade honestly when the explorer is unreachable — "we could not check" is not the same as "you have not donated", and showing the ask to an actual donor because a fetch failed would be a bad experience.
• The donation address and amount threshold are already defined (DONOR_THRESHOLD_FLUX = 10, DONOR_WINDOW_DAYS = 365), so "has donated" has an existing, tested definition in donor/donorStatus.js — reuse it rather than inventing a second rule.