In this track: Wallets without mystery
beginner · 3 MIN READ

One recovery phrase, many accounts

A deterministic key tree can produce several account identities.

LET’S PICTURE IT

A tree has many branches from one root. Cutting or exposing the root can affect much more than one branch.

SEE IT FOR YOURSELF
From a public address to a verified signatureStep 1 / 4
From a public address to a verified signaturePublic address0x0000…0001Share to receiveAnother personCan read the addressCannot sign for youPublic identifier ≠ secret authorizationLocal signerPrivate key stays hereSign the chosen requestSigned requestMessage + signatureSecret key not includedThe moving packet represents a signature, not a keySignatureCheck the exact messageCheck the signing contextVerificationAuthorization checkedIntent still mattersValidity and safety are different questionsWallet interfaceReads public dataRequests authorizationNetwork stateBalances and recordsIndependent verificationNo wallet is connected in this local illustration

An address is public receiving information. It is not the private key that authorizes actions.

Animated local teaching model. No wallet, RPC or live blockchain data. Some labels and hashes are abbreviated for readability.

Accounts can come from one root

Hierarchical deterministic wallets derive multiple keys using a defined path from seed material. The same inputs and compatible rules reproduce the same derived keys. This helps explain why one backup can restore several accounts.

A new account can share the same secret root

Pressing “create account” in a wallet may add another derived account rather than generate a completely independent recovery phrase. The app’s terminology varies, so check what it actually created.

A restoration can show a different subset

Apps may choose different default derivation paths or scan a limited number of accounts. Restoring a phrase does not guarantee that every app immediately displays the same list. Keep non-secret account and path information when the wallet requires it.

One leak can have a wider impact

Do not assume that a phrase exposure affects only the currently selected address. Learn the recovery design before using it. The derivation-path lesson explains how compatible wallets choose a branch of the tree.

QUICK CHECK · NO PRESSURE

Does “add account” always create an independent recovery phrase?

Your progress stays in this browser.
Keep exploring the original referencePrimary specification on GitHub ↗

Original explanations by EtherTools. Examples are educational and source-linked; this site is independent of the Ethereum Foundation. Our approach.