AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Low 48 Monero

Mark Nano, Banano and Fact0rn as Tor-ready, proxy Stellar node test

Public commit record

What the developer wrote

Authored by kroplabeskidu

83/100 · Strong
Mark Nano, Banano and Fact0rn as Tor-ready, proxy Stellar node test

Nano and Banano already send every request through Tor, and Fact0rn uses
the regular ElectrumX client, so they only needed the torSupport flag.

The Stellar node test proxied its first request but then created a
StellarSDK with the default client, so the follow-up ledger query went
out directly.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
The short version

What changed, and why it matters

This commit fixes a privacy leak in the Stellar wallet connection test and marks three cryptocurrencies (Nano, Banano, and Fact0rn) as supporting Tor. Previously, when testing a Stellar node, the first request went through the Tor proxy, but a follow-up request to check the ledger height was sent directly over the regular internet, potentially exposing the user's IP address and the node they were connecting to. The commit also correctly notes that Nano, Banano, and Fact0rn already supported Tor routing in practice, so their flags were updated to reflect that.

Recommended action

Users relying on Tor for privacy with Stellar, Nano, Banano, or Fact0rn should update to a build containing this commit. Review whether the Stellar node test or similar connection tests in other currency integrations have any other unproxied follow-up requests.

Security signals we found

01

Privacy leak: Stellar node test sent follow-up ledger query directly instead of through Tor proxy

02

Tor support flag corrections for Nano, Banano, and Fact0rn

03

SOCKS5 proxy assignment to HttpClient for Stellar SDK

04

Conditional proxying based on AppFeature.tor and Prefs.instance.useTor

Risk score

Why this scored 48/100

Our methodology →
Potential impact 12/30
Exploitability 10/25
Stealth signal 8/15
Affected reach 7/15
Confidence 7/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.