Running Cold Storage Demos Without a Real Device

Hardware wallet tutorials have a structural problem. The part beginners most need to see — initialising a device, writing down a recovery phrase, confirming it — is the exact part that cannot be filmed with a real device, because the phrase on screen is the wallet. Presenters work around it by blurring, by using a phrase they promise to discard, or by skipping the step and describing it instead.

All three are bad. Blurring teaches nothing. A discarded phrase is a phrase that existed, was photographed, and is now someone's responsibility to have actually discarded. And skipping the step leaves the beginner alone at precisely the moment they are most likely to make an unrecoverable mistake.

The second problem is cheaper but more common: a demo needs a portfolio in it to look like anything, and a real portfolio in a public video is a disclosure nobody intended to make.

The first is hardware. A team recording walkthroughs needs a device per presenter, in the right model, at the right firmware. Anyone who has tried to keep a support team's demo devices matched knows the version drift that follows. A simulated device manager sidesteps that entirely: pick the model the customer is asking about, and the screen matches what they are looking at.

The second is exposure. A simulated portfolio is not a real one, so there is nothing to leak — no address, no balance, no holdings, and no recovery phrase in existence to be careless with. That is not a small convenience. It is the difference between a walkthrough anyone on the team can record and one that only the person with the demo device can.

The trade is that a simulated demo proves nothing about your holdings, which for a teaching demo is not a trade at all. A tutorial's job is to show what the screens look like and what order they come in.

Hardware wallet owners are the most heavily phished group in crypto, and the attacks converge on one moment: something that looks like the real app asks for the 24 words. The defence that works is not a warning, it is recognition — knowing what the legitimate flow looks like well enough that the illegitimate one feels wrong immediately.

That is a teaching problem, and it needs screens. Showing a learner the genuine device detail screen, the genuine app installation flow, the genuine send confirmation — repeatedly, until the shape is familiar — is what makes the fake stand out later. Doing that with a real funded device, over and over, for every cohort, is not practical.

The single rule that makes this responsible rather than reckless: the real app never asks for your recovery phrase to do any of this. Teach that alongside the screens, and the demo does more good than the device would have.

A simulated wallet screen used to teach is a teaching aid. The same screen presented as evidence of what someone holds is a lie, and no amount of production quality changes which one you made. The difference is not in the pixels — it is in what the screen is being asked to prove.

Practically, that means labelling. If a simulated screen appears in a tutorial, a course, a support article or a conference slide, say so in the frame rather than only in a description nobody reads. It costs a line of text and it removes the ambiguity entirely.

It also means keeping the numbers ordinary. A teaching demo about receiving your first Bitcoin does not need a seven-figure balance behind it, and a modest one is both more useful to the learner and harder to mistake for a claim.