A single hardware wallet can control many Ethereum accounts. That sentence is short and plain. But how does that actually work? And what should you expect when you add multiple eth wallets on ledger hardware (or any hardware wallet)?
In practical terms: your hardware wallet holds one root secret (derived from your seed phrase). From that root it deterministically derives private keys and thus many ethereum addresses. This page explains the technical side, the UX side (how account lists are created in apps), and the safety choices you need to make when you manage multiple eth accounts ledger-style.
See also: derivation-paths and ledger-live.
Two standards do most of the work: BIP-39 (seed phrase) and BIP-32/BIP-44 (hierarchical deterministic key derivation). The canonical specs are available here: BIP-39, BIP-32, BIP-44.
For Ethereum the commonly used coin_type is 60 (per BIP-44). That results in derivation paths such as:
But apps differ. Some create new "accounts" by incrementing the account' index (m/44'/60'/1'/0/0) rather than the address_index. Which one a given app uses is an app-level decision.
Why care? Because if you add an account in one app and then open a different app that uses a different derivation convention, the second app may not show that account unless you select the same derivation path.
Short answer: an "account" (in many wallet UIs) maps to a derivation path or to an address group. An "address" is a single public address that can receive funds.
Concrete example: you might use one account for long-term BTC (or ETH) holdings, and another account for day-to-day DeFi. That keeps balances separate for bookkeeping and reduces linkability across activities (privacy benefit).
(Which should you pick? It depends on what you want: privacy, accounting, or smart-contract interaction isolation.)
The hardware wallet itself doesn't list "accounts" the way an app does. The device holds the keys; the wallet app displays named accounts and lets you add or remove them. Typical destinations:
What I noticed in testing: companion apps often create separate "accounts" by incrementing the BIP-44 account index, while browser wallets typically enumerate multiple addresses from one account by incrementing the address_index. Keep that difference in mind.
How to add a second Ethereum account without exposing your seed phrase.
Why verify on-device? Because the hardware wallet's screen is the only trusted display — it proves the address was generated by your keys (not the app). Always do this step.
See more detailed step-by-step guides: add-accounts-apps, metamask-setup, myetherwallet-guide.
All accounts are deterministic. That means a single seed phrase (plus optional passphrase) restores all accounts. What I've found: many users misunderstand this and think separate accounts are independent backups — they are not.
Practical advice: use metal backup plates for your seed phrase (see metal-backup-plates). And do not import your seed phrase into random software wallets or reveal it to anyone.
Multisig (multiple signers required to execute transactions) is a different security model from using multiple accounts on one device. Multisig raises the bar for attackers because compromise of a single device does not allow theft. It is commonly implemented via smart contracts for Ethereum (see multisig-setup and multisig-compatibility).
When to use multisig? For larger shared safekeeping, organizational funds, inheritance planning, or when you want geographic separation of keys.
And remember: a hardware wallet can be one signer in a multisig scheme — that is common practice.
If you bought a device from an unofficial seller, your recovery phrase or device may be compromised. Don't use it; see where-to-buy-safely and common-mistakes.
| App model | How extra accounts are created | Address verification on device | Multisig friendly |
|---|---|---|---|
| Companion app (desktop/mobile) | Often increments BIP-44 account index (m/44'/60'/1'...) | Yes (on-device) | Yes (via external services) |
| Browser extension wallet | Usually enumerates address_index within account (m/44'/60'/0'/0/x) | Yes, when connected | Some integrations available |
| Web wallet (MEW style) | Can import various derivation paths | Yes (hardware prompt) | Depends on wallet |
(Image placeholder: Derivation path diagram (placeholder))
Q: Can I recover my multiple eth accounts if the device breaks? A: Yes. Restore the seed phrase (and passphrase if you used one) on a compatible wallet and the same derivation paths will recover your accounts. See backup-and-recovery.
Q: Is using a passphrase safe for creating more accounts? A: It increases isolation but raises the risk of permanent loss if you forget the passphrase. I use it only when I need clearly separated vaults; otherwise I use separate accounts without a passphrase.
Q: What happens if the company behind my hardware wallet goes bankrupt? A: Your seed phrase controls your funds, not the company. You can restore to another compatible wallet. See company-failure-recovery.
Q: Is Bluetooth safe for a hardware wallet? A: Bluetooth increases convenience, but it widens the attack surface. If you care about maximum isolation, prefer USB or air-gapped workflows. See connectivity-usb-bluetooth-nfc.
Q: Are multiple eth accounts the same as multisig? A: No. Multiple accounts are separate keys derived from one seed. Multisig requires multiple independent signers.
Multiple eth accounts on a single device are a feature of deterministic wallets — they make bookkeeping, privacy separation, and specialized workflows possible without creating extra seed phrases. But remember: all accounts flow from one seed (plus optional passphrase). Protect that seed. Verify addresses on-device. And pick the account model (address_index vs account index) that suits your workflow.
Next steps: follow the step-by-step guides in add-accounts-apps and read the recovery guidance at seed-phrase-management. If you plan multisig, see multisig-setup.
Want hands-on walkthroughs? Check the step-by-step pages linked above and test with a small transaction first.