Build a privacy threat model before picking tools
An Ethereum privacy threat model names the observer, the information you want to protect, and the limits of each precaution. Start with a specific concern; a wallet setting cannot hide every kind of data.
Turn a vague worry into one clear question
Example: keeping a savings balance out of a work chat
Suppose a coworker knows the address on your public profile. Your concern is that they can see its balance. Changing an RPC provider will not hide that balance from them. A threat model helps match the action to the problem. Write down the observer, the fact you want to protect, and what is still exposed.
- Observer: A coworker with your public address.
- Exposed fact: The balance recorded at that address.
- Limit: A wallet setting cannot erase the public record.
Keep in mind: Keep this note free of passwords and recovery words. Review it before you publish another address.
Who are you trying to protect information from?
A curious coworker, an application operator, an RPC provider, and an exchange do not see the same data. Begin with a concrete observer rather than a promise of total anonymity. List what that observer already knows, such as a public address, an email, or the time you made a payment.
Which data needs a separate precaution?
Onchain means recorded on the blockchain. This data includes transfers, contract calls, and events. Network data can include IP addresses and request timing. Application data may include connected accounts and analytics identifiers. Protecting one layer does not automatically protect the others. A private proof can still be submitted through an identifiable browser session.
Make the trade-off explicit
More separation can mean more accounts to back up, more transaction fees, and more chances to make a mistake while using the system. Rank your concerns by consequence. Protecting a recovery phrase from accidental cloud exposure is usually more urgent than polishing a low-impact browser preference.
Review after a change
Revisit the model when you publish an address, use a new wallet, accept an employer payment, or start using a new chain. Record assumptions, not secret credentials. A useful model is a short working document: observer, exposed information, precaution, and remaining limitation.
For market context, see our timestamped ETH/USD reference and check the quote’s freshness before using it.
Apply your threat model to the service receiving your wallet’s requests.
Check the source
This is an original, AI-assisted educational explanation. Sources and limitations are provided for verification; it is not personalized financial advice. Read the editorial policy or report a correction.
