Fix: Ledger Cardano Shelley vs Byron Derivation Path ADA Recovery
When recovering a Ledger Nano S Plus, Nano X, or Stax onto a new device, or when connecting an existing Ledger to modern Cardano web interfaces such as Eternl, Lace, or Yoroi, users frequently experience total shock: their portfolio balance displays 0.000000 ADA. Staking rewards are absent, and transaction logs show no on-chain activity.
This disappearance is not the result of a hack or private key compromise. Rather, it is caused by an architectural schism in the Cardano blockchain: the migration from the Byron Era (BIP44) to the Shelley Era (CIP-1852).
If you are experiencing address format mismatches or transaction submission rejections between Yoroi and Eternl, consult our companion guide on Cardano Yoroi & Eternl Address Incompatibility.
Cryptographic Root Cause: BIP44 vs CIP-1852 Derivations
Cardano utilizes the Ed25519 elliptic curve with BIP32-Ed25519 hierarchical key derivation.
The Two Era Derivation Schemes
- Byron Era (Legacy - BIP44):
$$\text{m / 44’ / 1815’ / account’ / 0 / address_index}$$
- Address Prefix:
Ae2...orDdzFF...(Base58 encoded) - Staking Support: None (Flat UTXO model without stake credentials)
- Standard for transactions created between 2017 and mid-2020.
- Address Prefix:
- Shelley Era (Modern - CIP-1852):
$$\text{m / 1852’ / 1815’ / account’ / role / address_index}$$
- Address Prefix:
addr1...(Bech32 encoded) - Staking Support: Dual-key construction (Payment Key + Stake Key)
- Standard default for modern Ledger Live and web wallets.
- Address Prefix:
Because the derivation paths diverge at the very first index level (44' vs 1852'), Ed25519 point multiplication produces completely different public/private key pairs. When a user creates a new wallet in Ledger Live or Lace, the client scans only the modern m/1852'/1815'/0'/0/0 path. If the user’s funds were received into a legacy Byron address, the balance remains invisible.
Step-by-Step Recovery Protocol
To locate your stranded Byron ADA and migrate it safely into a modern, stakeable Shelley account without exposing your 24-word seed phrase, execute the following protocol.
1. Close Conflicting Software
Ensure Ledger Live desktop is completely closed to avoid WebUSB / HID communication contention with browser extensions.
2. Connect Ledger via Eternl with Byron Scan Enabled
Eternl is the most comprehensive Cardano power-user wallet for hardware path recovery:
- Open Eternl in a Chromium browser (Brave, Chrome, or Edge).
- Click Add Wallet $\rightarrow$ Pair Hardware Wallet.
- Select Ledger, ensure the Cardano application is open on your physical device, and complete the WebHID pairing handshake.
- On the configuration screen, toggle the advanced option:
[X] Include Byron Accounts (BIP44 m/44'/1815')
- Proceed through account generation. Eternl will query both the
m/1852'andm/44'derivation trees.
[Eternl Multi-Era Discovery Preview]
Account 0 (Shelley - CIP-1852): addr1q... -> Balance: 0.000000 ADA
Account 0 (Byron - BIP44): Ae2td... -> Balance: 18,450.250000 ADA <-- FUNDED!
3. Programmatic Account Auditing via Cardano CLI / SDK
For node operators who prefer verification via Node.js scripts, use @emurgo/cardano-serialization-lib to compute public addresses across both paths:
// scripts/cardanoDerivationAudit.ts
import * as Cardano from '@emurgo/cardano-serialization-lib-nodejs';
// Derivation paths
const SHELLEY_PATH = "m/1852'/1815'/0'/0/0";
const BYRON_PATH = "m/44'/1815'/0'/0/0";
export function explainCardanoAddressDifference() {
console.log('Cardano Era Derivation Comparison:');
console.log(`- Shelley Path: ${SHELLEY_PATH} -> Generates addr1... (Staking supported)`);
console.log(`- Byron Path: ${BYRON_PATH} -> Generates Ae2... (Legacy un-staked)`);
console.log('\nAlways check both trees when restoring wallets created before 2021.');
}
explainCardanoAddressDifference();
4. Execute the Internal Migration Transfer
Once your Byron account is active in Eternl:
- Copy your Shelley receiving address (
addr1...) from your primary Ledger Live account. - Inside Eternl’s Byron account tab, click Send.
- Paste your Shelley
addr1...address as the destination. - Confirm the transaction on your physical Ledger device (verify the destination address character-for-character on the Ledger screen).
- Once confirmed on-chain (~20 seconds), your total balance will populate in Ledger Live, and you can now delegate your ADA to a stake pool to earn rewards.
Cardano Derivation Standards Comparison Table
| Era / Standard | Derivation Path | Address Format | Staking Key Integrated | Ledger Live Default |
|---|---|---|---|---|
| Byron (BIP44) | m/44'/1815'/account'/0/i | Ae2... / DdzFF... | No | Hidden / Legacy |
| Shelley (CIP-1852) | m/1852'/1815'/account'/0/i | addr1... | Yes (role: 2) | Active Default |
| Enterprise (CIP-1852) | m/1852'/1815'/account'/0/i | addr1... (no stake) | No | Optional |
| Reward Account | m/1852'/1815'/account'/2/0 | stake1... | Stake Credential | Automatic |
Frequently Asked Questions
Q: Can I lose my ADA by sending it from a Byron address to a Shelley address?
No. Cardano’s consensus protocol seamlessly processes transactions between Byron and Shelley addresses. Sending ADA from Ae2... to addr1... is a standard on-chain transaction that finalizes cleanly.
Q: Why doesn’t Ledger Live automatically scan Byron accounts?
To streamline synchronization times for the vast majority of users who onboarded after 2020, Ledger Live limits its initial query to CIP-1852 Shelley accounts. Scanning both derivation trees across multiple accounts doubles synchronization latency.
Q: Does my 24-word recovery phrase change when migrating from Byron to Shelley?
No. Your 24-word recovery phrase remains identical. The master root seed inside your Ledger device mathematically derives both the m/44' and m/1852' branches simultaneously from the exact same master secret.