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

Add Tor support for Ethereum

Public commit record

What the developer wrote

Authored by kroplabeskidu

78/100 · Adequate
Add Tor support for Ethereum

web3dart was handed a plain http Client, so ETH and ERC-20 RPC could not
use Tor and the coin was flagged as not Tor-ready. Give it an IOClient
wrapping a SOCKS5-proxied HttpClient instead, the same way Solana does it,
and do the same for the node connection test.

Also add the usual node tor/clearnet mismatch check and set torSupport.
✓ 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 adds Tor privacy support for Ethereum in Stack Wallet. Previously, Ethereum RPC traffic always traveled over the regular internet (clearnet), even when the user turned on Tor, because the underlying library used a plain HTTP client. The patch routes Ethereum traffic through the Tor SOCKS5 proxy when Tor is enabled, and adds a check that warns if the selected node conflicts with the user's Tor setting. It also adds tests to confirm the proxying works.

Recommended action

No immediate user action required. The fix should be included in the next release. Users relying on Tor for Ethereum should verify they are on a build containing this commit and that their selected Ethereum node supports Tor or is configured appropriately.

Security signals we found

01

Previously Ethereum RPC and ERC-20 token traffic bypassed Tor despite the user's Tor setting, causing potential IP/transaction graph leakage.

02

Patch enforces SOCKS5 proxying for Ethereum RPC when Tor is enabled.

03

Adds Tor/clearnet node mismatch guard consistent with other coins.

04

Adds unit tests verifying proxy routing and direct fallback behavior.

05

Removes outdated comments incorrectly stating Ethereum cannot use Tor with web3dart.

Risk score

Why this scored 38/100

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