How Ledger Live Device Screens Work in a Demo

Phantom, Trust Wallet and Exodus are self-custody software wallets: the keys live on the phone, and the app is the whole product. Ledger Live is a different thing. It is a companion app for a physical device that holds the keys, and almost every screen in it assumes that device exists somewhere nearby.

That distinction matters in education and support: the app displays accounts and prepares actions, while the physical device holds keys and approves transactions. A portfolio-only walkthrough omits the most important security boundary.

A complete demo should therefore explain the role of the device, while making clear that RPWallet's device and balances are simulated.

Open My Ledger in the real app and you get a device illustration that matches the model, a name you chose, a firmware version, and a line confirming the device is genuine. Below that sits a storage bar with a used figure in kilobytes, an app count, and the space remaining.

The storage figure is useful for explaining that blockchain apps consume device storage while balances do not. The simulated app count and bar update together so a trainer can demonstrate that relationship without a physical device.

Models also differ. A Nano S and a Ledger Stax do not have the same storage or controls; touchscreen models expose options such as a lock-screen picture and device language that button models do not. Select the model the lesson is actually about.

On a Ledger device, each chain family is signed by its own small app: Bitcoin, Ethereum, Solana, XRP, Cardano, Cosmos, Tron, Zcash and so on, each with its own version number and size in kilobytes. A device that has never had the Solana app installed cannot sign a Solana transaction, and Ledger Live knows it.

The mapping is by signing family, not by network badge. Polygon, Base, Arbitrum, Optimism, Linea, Scroll, BNB Smart Chain and roughly twenty other EVM networks use the Ethereum app. A multi-network EVM lesson therefore needs one Ethereum device app, not a separate app for every network.

The app list is part of the security model: it explains which types of transaction a physical device can review and sign.

A balance is one number, so a static image can carry it. A staking position is not one number. It has a validator, a minimum stake the network enforces, an amount that has been accruing since a specific moment, and — when it is unwound — a cooldown before the funds come back.

In the simulator, those quantities are linked so an educator can show how elapsed time affects illustrative rewards, why networks have minimums, and what an unstake cooldown means. None of the displayed figures represents an actual position or expected return.

The simulated minimums differ per network: Cardano and Polkadot use whole units, Solana and Cosmos use hundredths, and Ethereum uses thousandths. Explain these as product-demo inputs rather than financial guidance.

For a structured lesson, start with the device — model, name, and the apps it carries — before moving to portfolio screens. That order mirrors the relationship between physical hardware and its companion app.

In RPWallet's Ledger Live interface, add a simulated device from the profile screen, open My Ledger, install the blockchain apps used in the lesson, and then configure fictional balances for the walkthrough. The storage bar updates as apps are installed.

Nothing in that flow touches a real device or a recovery phrase, which is the point. The screens are simulated end to end, and the honest disclosure that they are simulated is what makes the content publishable.