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

Migrate the Fact0rn default node to allow Tor

Public commit record

What the developer wrote

Authored by sneurlax

78/100 · Adequate
Migrate the Fact0rn default node to allow Tor

updateDefaults keeps the saved node's tor and clearnet flags, so existing
installs kept the old clearnet-only Fact0rn default even though it now
allows Tor. With Tor turned on that node is rejected and Fact0rn cannot
refresh or pass the node test.

Add a one-time migration that enables Tor on the saved Fact0rn default
node. Only a node that still matches the old shipped default on every
field the user can edit (host, port, name, SSL, failover, login, clearnet
only) is touched, so a node the user customised keeps its settings.
Clearnet stays enabled, so nothing changes with Tor off, and later
choices are left alone.
✓ 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 bug where the Fact0rn cryptocurrency default node in Stack Wallet stayed set to 'clearnet only' even after the app shipped a new default that supports Tor. For users who turned on Tor, the wallet could no longer connect to that node, so Fact0rn balances would not refresh and the node health test would fail. The patch adds a one-time database migration that flips Tor support on for the default Fact0rn node, but only if the user has not customized it. It is a connectivity/usability fix, not a vulnerability that lets an attacker steal funds or run code.

Recommended action

Treat as a routine bug-fix release. No urgent security response is required. Verify the migration runs cleanly on existing installs and that Tor-enabled Fact0rn wallets can refresh and pass the node test. Consider documenting the Tor connectivity improvement in release notes.

Security signals we found

01

Network-layer connectivity fix for Tor users

02

Migration touches only a single, narrowly matched default node

03

No cryptographic, authentication, or authorization changes

04

No input parsing, deserialization, or remote code paths modified

05

Tests assert customized nodes are not altered

Risk score

Why this scored 25/100

Our methodology →
Potential impact 4/30
Exploitability 2/25
Stealth signal 2/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.