From f9f822f4378147e14a96e6735ef2a7aa616cb03c Mon Sep 17 00:00:00 2001 From: Davide Grilli Date: Mon, 27 Jul 2026 08:21:12 +0200 Subject: [PATCH] Document real fallback Electrum servers in .env.example Use PalladiumWallet's mainnet bootstrap server list (ChainProfiles.cs) as the example instead of a generic placeholder, since those are the actual servers this deployment should fall back to. --- .env.example | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/.env.example b/.env.example index e23b8ce..48c8e71 100644 --- a/.env.example +++ b/.env.example @@ -9,7 +9,10 @@ ELECTRUM_USE_SSL=true # confirmation goes through this one connection, which makes a single server the # platform's biggest single point of failure. A typo here fails at startup rather # than during the outage when the fallback is what you need. -# Example: ELECTRUM_FALLBACK_SERVERS=node2.example.net:50002,node3.example.net:50001:notls +# These are the mainnet bootstrap servers from the PalladiumWallet repo +# (src/Core/Chain/ChainProfiles.cs, ChainProfiles.Mainnet.BootstrapServers) — the +# same ones the reference wallet falls back to: +# Example: ELECTRUM_FALLBACK_SERVERS=173.212.224.67:50002,144.91.120.225:50002,66.94.115.80:50002,89.117.149.130:50002 ELECTRUM_FALLBACK_SERVERS= # Fernet key protecting the master xprv at rest. Generate with: