What are the risks of using a public remote node?
Remote nodes provide convenience but require reliance on infrastructure you do not control.
Quick Answer
Using a public remote node involves trusting the operator to provide accurate blockchain information and not log your activity. The primary risks include potential privacy leaks—where the node tracks your requests for specific transaction outputs—and the risk of the operator providing an incorrect chain state. While network consensus protects your funds, your privacy is compromised when using untrusted third-party nodes.
Privacy Leaks
When querying a node, you reveal which outputs your wallet owns. Even without knowing your identity, the node can track patterns associated with your wallet over time. Using Tor mitigates IP logging but does not resolve the metadata privacy issues inherent in node queries.
Reliability Concerns
A malicious node could potentially withhold information or attempt to mislead a lightweight wallet regarding the current network state. This cannot steal your funds, but it can prevent you from transacting properly, leading to service disruption.
Networking controls in Best Wallet
Best Wallet combines built-in Tor and selectable node connections with everyday XMR management, so network choices are available in the wallet interface. Its documented default uses clearnet for the initial scan and Tor afterwards; select the mode that fits your threat model. These controls do not protect a compromised computer or information disclosed to an external service.
Explore Best Wallet privacy controlsSources
Related reading
Key takeaways
- Public nodes can track your transaction request activity.
- Remote node operators might provide inaccurate blockchain information.
- Running your own node is the only way to avoid these risks.
