Wallet simulator or testnet: which one your demo needs

They solve different problems and are constantly confused. One proves the code runs; the other controls what the screen says. Almost no demo needs both.

Published: 12 September 2026

What a testnet actually gives you

A testnet is a real blockchain with coins that have no market value. The cryptography is real, the signatures are real, blocks are produced, and a transaction takes as long as a transaction takes. If your question is « does the send flow work end to end », nothing else answers it.

What it does not give you is control of what appears on screen. Faucets hand out whatever they hand out. Token symbols carry their test prefixes. There are no market prices, so the fiat column — which on a wallet home screen is the largest text on the page — is empty, zero, or wrong.

What a simulator gives you

Exact values, instantly, at the resolution you need. Five tokens with the quantities you decide, a total that adds up, a day's change that matches the rows above it. And nothing behind it: no signature, no confirmation, no hash, nothing to look up.

The question that decides

Does the artefact need to prove something, or show something?

A QA run before release, a bug report about a failed signature, a security review: those need proof, so they need a testnet, or mainnet with an amount small enough not to matter. A listing image, a deck slide, a tutorial frame, a design review: those need a screen, so they need a composed one.

The mistake that costs the most time is using a testnet for the second kind. Teams spend an afternoon topping up faucets to produce a screenshot that then shows 0.4 tokens of something nobody recognises, and end up retouching it in an image editor anyway — which is composing a screen, with extra steps and a worse result.

A note on mainnet screenshots

The third option people reach for is their own wallet. It is the worst of the three for anything public: the address is visible, the balance is visible, and both are permanent once posted. There is a separate piece on demonstrating a wallet without showing a real balance; the short version is that a screenshot of a real account is a disclosure, not an illustration.

Questions

Can I use a testnet instead of a wallet mockup?

For proving that a flow works, yes — a testnet is better, because it is real. For a screenshot or a listing image it usually is not: testnet balances, token names and addresses look like testnet, and that is what your audience will see.

Why do testnet screenshots look wrong?

Because the values are not chosen. Faucet amounts are arbitrary, token symbols carry testnet prefixes, and prices do not exist, so the fiat column is empty or zero. The screen is real and tells the wrong story.

Which one should I use for an App Store listing?

A composed screen. Apple's reviewers judge whether the images represent the app accurately, not whether the numbers came from a chain — and a listing showing an empty faucet balance represents it badly.