How to demo a wallet without showing a real balance

A screenshot of your own wallet publishes an address and an amount, permanently, to an audience that includes people looking for exactly that pair.

Published: 13 September 2026

What one screenshot actually contains

Three things, and their combination is the problem. The address, which is public by design but not linked to you until you link it. The balance, which is also public but only if someone knows which address to look at. And the moment, because a screenshot is timestamped by the post that carries it.

Individually these are unremarkable. Together they turn an anonymous entry in a public ledger into a named one, and the link cannot be undone afterwards. Deleting the post does not delete the association; it was read, cached and indexed the day it went up.

Why redaction is weaker than it looks

The instinct is to blur the address and post anyway. It is weaker than it looks, because the rest of the frame is identifying. An address with four visible characters, five tokens in a particular mix, quantities to five decimal places, and a timestamp — that is a query, not a mystery, and an explorer answers it.

The same applies to cropping. A crop removes pixels; it does not remove the fact that the account was described precisely enough to find.

Three alternatives that work

Compose the screen. If the point is what the interface looks like — a listing image, a tutorial frame, a deck slide — then the numbers were never load-bearing. Pick them. Nothing behind the image means nothing to leak, and no redaction to get wrong.

Use a testnet. If the point is that the flow works, a testnet gives you a real signature and a real confirmation with nothing at stake. See wallet simulator or testnet for which of the two a given demo needs.

Use a throwaway account. A fresh address holding a token or two, used for nothing else and never funded from your main one. This is the option people reach for and get wrong most often: funding it from the account you were trying not to reveal connects them permanently, in public, in one transaction.

The one case where a real screenshot is right

When the audience is you or your team, and the artefact is a bug report. A support ticket about a balance that renders incorrectly needs the real screen. Send it privately, and take the same care you would with any other account detail.

Questions

Is it safe to post a screenshot of my crypto wallet?

Not for a public audience. The image ties an address to a balance and to you, permanently, and it is trivially searchable afterwards. Public addresses are already public — the harm is in the link to a person.

Does blurring the address make a wallet screenshot safe?

Often not. Partial characters, the token mix, the exact amounts and the timestamp are frequently enough to identify the account on an explorer. Redaction removes the display, not the information.

What should I use for a public demo instead?

A composed screen with values you chose, a testnet if the flow itself is the point, or a dedicated account holding a trivial amount and nothing else.