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

Add onionbalance Tor frontends to default node lists (#3431)

Public commit record

What the developer wrote

Authored by Seth For Privacy

81/100 · Strong
Add onionbalance Tor frontends to default node lists (#3431)

* Add onionbalance Tor frontends to default node lists

Update the primary Monero and Zcash onion nodes to the new
load-balanced onionbalance frontends, add missing Cake Wallet Tor
nodes for Bitcoin and Litecoin, and use the mempool onion frontend
for Bitcoin fee fetching when Tor is enabled. All Cake Tor nodes are
marked isOfficial so they get the official-node badge.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* Remove per-instance Zcash Tor #2 node, superseded by onionbalance frontend

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
✓ 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 commit updates Cake Wallet's built-in lists of cryptocurrency network servers. It replaces some single Tor/onion server addresses with new load-balanced Tor frontends, adds missing Tor server options for Bitcoin and Litecoin, and makes Bitcoin fee estimates use a Tor address when Tor mode is on. The changes are infrastructure/configuration updates rather than code fixes for a vulnerability. There is no direct evidence in the commit that this is a security patch, but routing traffic through Tor can improve user privacy.

Recommended action

Treat as a routine infrastructure/privacy improvement. Review that the new .onion URIs match published Cake Wallet infrastructure, verify ProxyWrapper correctly enforces Tor routing when an onionUri is supplied, and confirm no clearnet fallback leaks occur when Tor is enabled. No urgent security action is indicated by the diff alone.

Security signals we found

01

Adds Tor/onion routing for Bitcoin fee estimates

02

Replaces single Tor nodes with load-balanced onionbalance frontends

03

Marks Cake Wallet Tor nodes as official in default node lists

04

No vulnerability fix, authentication change, or exploit mitigation visible in diff

Risk score

Why this scored 21/100

Our methodology →
Potential impact 2/30
Exploitability 2/25
Stealth signal 3/15
Affected reach 5/15
Confidence 6/10
Evidence quality 3/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.