AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Informational 19 Bitcoin

network: disconnected servers: do not filter out bookmarked raw ":t"

Public commit record

What the developer wrote

Authored by SomberNight

81/100 · Strong
network: disconnected servers: do not filter out bookmarked raw ":t"

In the GUI, when displaying the list of disconnected servers, we were
filtering to only ":s" servers. Instead now we also show ":t" servers
if they are bookmarked.

Also, if bookmarked, we also show disconnected .onion servers, even
when not using a Tor proxy.

fixes https://github.com/spesmilo/electrum/issues/10374
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This is a small user-interface fix in the Electrum Bitcoin wallet. Previously, the list of 'disconnected servers' shown in the network settings only displayed secure ':s' servers and hid plain-text ':t' servers and .onion servers, even if the user had bookmarked them. The change makes bookmarked plain-text and .onion servers visible again so users can see and manage servers they deliberately saved. It does not change how the wallet actually connects to servers or any security-critical networking logic.

Recommended action

No security action required. Treat as a normal bug fix / UX improvement. Reviewers may optionally verify that to_friendly_name() does not expose sensitive internal addresses and that the renamed constant is imported correctly everywhere.

Security signals we found

01

UI-only change; no modification of connection, certificate, or authentication logic

02

No change to default server selection or preferred protocol ('s' remains preferred)

03

No input parsing changes beyond renaming an existing protocol set constant

04

No privilege escalation, code execution, or data-exfiltration path introduced

Risk score

Why this scored 19/100

Our methodology →
Potential impact 2/30
Exploitability 0/25
Stealth signal 0/15
Affected reach 5/15
Confidence 8/10
Evidence quality 4/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.