jwinterm f48373282f electrum: make the fallback privacy tradeoff visible to operators ...

Falling back to public Electrum is a PRIVACY decision, not just an availability
one: the queries carry user addresses. It is easy to miss because the failover
is silent and correct, so the only symptom is that balances keep working. Our own
LTC Fulcrum was dead for 11 days with every lookup going to third parties, and
nothing surfaced it.

- startup: log how many third-party fallbacks are configured and how to fail
  closed instead, so the posture is visible in the operator's own logs
- .env.example: state the tradeoff at the setting, with both choices spelled out
  rather than a default presented as obviously correct
- OPERATOR_SETUP: same note where an operator configures chains

Also expands the shipped fallback lists (BTC 3 -> 8, LTC 4 -> 7), which is both
more resilience and a wider spread of which server sees any given query.

2026-08-02 20:56:32 -04:00

..

design

docs(examples): operator cookbook — six deployment recipes + premium-relay spec

2026-07-02 19:47:46 -04:00

operations

electrum: make the fallback privacy tradeoff visible to operators

2026-08-02 20:56:32 -04:00