ANON
Privacy, without the mythsEthereum is public. Your identity is the missing piece. Build a privacy threat model before picking tools Address reuse and ENS can turn separate moments into a profile
Your wallet. Your boundaries.What your Ethereum wallet can reveal before you send anything Token approvals: disconnecting a dapp does not revoke its allowance Recovery phrase security: private, recoverable backups
Inside the privacy stackZero knowledge is a proof property, not a privacy guarantee The RPC connection is part of your privacy model Stealth addresses: private receiving, with caveats
ETH priceAboutEditorial policy

Ethereum is public. Your identity is the missing piece.

Ethereum is pseudonymous, not anonymous. An address does not require a real name, but its transfers and contract activity are public. A name, profile, or service record can connect that activity to a person.

Transparent ledger beneath a frosted profile, illustrating visible activity without a recorded name.

What can a stranger actually learn?

A public address is a trail, not a name

Imagine you post a donation address on your profile. A stranger can now connect that profile to the address. They can look up its public activity. They still cannot prove why each payment happened. A transfer shows movement of funds, not the full story behind it.

  • Visible: The address, recorded transfers, and interactions with contracts.
  • Not proved by a transfer: The owner’s motive, a private agreement, or who controls another address.
  • Worth checking: Whether you have linked the address to a name in another place.

Keep in mind: Start with an address you already treat as public. There is no need to share a new address with this site.

Separate evidence from an ownership guess

One address can have more than one role

Imagine a club publishes an address to collect event payments. Its balance is visible, but calling that balance the treasurer’s personal wealth would add a claim the ledger does not establish. The address could hold money for several people. Describe the recorded action first and keep assumptions about ownership separate.

Write down what would support the claim

A public statement linking a person to an address is different from two transfers happening close together. Even a public link does not explain every later payment. Use a threat model to record what an observer knows, what they can only guess, and which future disclosures you can control.

What does an Ethereum address reveal?

Ethereum does not require a real name to create an ordinary account. It does, however, publish transfers and actions involving contracts. Someone can inspect an address without asking its owner. A pseudonym keeps the name out of the address; it does not keep activity off the ledger. This distinction matters when a public donation address is also used for savings or everyday payments.

How can an address be linked to a person?

An exchange withdrawal, a public ENS name, an invoice, or a social post can connect a person to an address. That connection may make older transactions easier to interpret. Observers can also guess at links from timing and transaction patterns, but a pattern alone is not proof that two addresses have the same owner. Treat confident claims about ownership with care.

Think in boundaries

Write down who you want privacy from and which facts matter: balances, people or services you transact with, or browsing activity. A wallet setting that reduces telemetry cannot remove transaction history from Ethereum. Similarly, avoiding public address reuse does not prevent an exchange from retaining its own records. Different observers require different precautions.

A practical first audit

Open a block explorer using an address you already consider public. Look at transfers, token approvals, and linked names. Ask what a stranger could infer without special access. Do not paste private keys or recovery phrases into an explorer. Use the findings to change future habits, while assuming that previously published information can remain available indefinitely.

Example: matching times do not prove matching owners

Two people withdraw from an exchange within the same minute. An observer sees two transfers close together and guesses that the receiving addresses belong to one person.

The timestamps support a claim about when the transfers happened. They do not establish who controls the destinations. A service can handle unrelated customers close together in time. The public record needs other evidence before that ownership claim is justified.

Write down the fact separately from the guess: “These transfers happened close together” is narrower than “One person owns both addresses.”

Check the source

Ethereum.org documentation

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.

Build a privacy threat model before picking tools

Build an Ethereum privacy threat model around the observer, exposed information, practical precautions, and the limitations that remain.

Address reuse and ENS can turn separate moments into a profile

Understand how Ethereum address reuse, public ENS names, and repeated payments can connect activity to an identity.