Network privacy at a glance
What wallet calls can reveal
Assumes Tor mode, indexed sync, and no endpoints set to bypass Tor.
Tor hides your network address from services. Those services still see the request data they receive.
- Sensitivity
- Low: public data
- Moderate: usage patterns
- High: wallet or transaction links
Chain and token or oracle interests. These queries don't need a wallet account.
Chains, sync ranges, circuit variants, proposal interests and timing. Matching notes to your wallet stays on your device.
Peer identity, selected chains and activity timing. Discovery DNS also goes through Tor.
The relay sees client ID, topics and timing. The dapp you approve receives accounts and signed responses.
Addresses, assets, recipient names, governance participation, and links between accounts and activity.
Recipient, amount and call data during preparation, and the full signed transaction when sent. Related steps stay linkable.
Pair, amount and source accounts. Approved requests also reveal delivery and refund terms, and signed orders or hooks.
The chosen broadcaster sees execution data, fees and proofs. Waku peers see ciphertext, chain, topic and timing.
Commitments, public note keys, and links between proofs and outputs can be tied to a specific RAILGUN transaction.
Your local network and the Tor relays you connect to directly see your real IP and that you use Tor. Wallet data travels inside Tor.
The paired browser or bridge receives the wallet and device data you allow. This is a local or LAN connection you set up.
Shared versus isolated
Shared traffic uses the wallet's common Tor session. Isolated traffic gets its own circuit group for its account, operation or origin. Separate groups can still leave through the same exit IP, and identifiers inside the requests can still link them.
What indexed sync changes
POI lookups for your wallet's own commitments stay on your device. Public POI updates and transaction or output proof submissions still contact the POI service, over the routes shown above.
Sensitivity describes what the recipient can learn. It is not a vulnerability rating. The Direct rows cover Tor itself and local integrations. Under these assumptions, every other call in the table goes through Tor.