Inside Ethereum’s privacy technology
Zero-knowledge proofs, RPC choices, and stealth addresses protect different parts of an Ethereum activity. Check what each method hides, who can still observe it, and how recovery or later spending affects that boundary.
Follow the complete data path
Use the proofs guide to distinguish private inputs from public data. The RPC guide covers requests outside the chain, while stealth addresses address receiving-account linkage. These explain different boundaries; combining them is not a blanket privacy guarantee.
Ask exactly what the technology hides
A proof, a request, and a payment destination
Zero-knowledge proofs concern what a proof reveals. RPC choices concern who receives chain queries. Stealth addresses concern links to a receiving address. Each solves a different part of the privacy problem. Combine the ideas only after you understand their limits.
- Before choosing: Name the information you want to protect.
- Before relying on it: Check what remains public and how recovery works.
Zero knowledge is a proof property, not a privacy guarantee
Understand what zero-knowledge proofs can hide and why public inputs, account identities, and application metadata can still reveal information.
The RPC connection is part of your privacy model
Learn how Ethereum RPC requests expose account queries and connection data to a provider, and what changing an endpoint or running a node can change.
Stealth addresses: private receiving, with caveats
Understand how Ethereum stealth addresses create fresh payment destinations, why later spending can reveal links, and what to check about recovery.