Understand how seedrecover.py selects derivation paths, and how to configure it for altcoins or non-standard wallets.
A derivation path describes how a wallet derives individual addresses from a master seed. Different wallet software and different coins use different paths, so using the wrong path during recovery will produce the wrong addresses — causing the tool to miss the correct seed even if it’s tested.seedrecover.py handles this automatically for common wallets, but understanding the path system helps when recovering altcoins, non-standard wallets, or when you need to tune performance.
By default, seedrecover.py checks the first account of each address type on all common derivation paths for the selected coin. For BIP39 wallets with no coin specified, it defaults to Bitcoin paths.All derivation path lists live in the derivationpath-lists/ folder of the repository. You can edit them to add or remove paths — removing paths you know are irrelevant improves search speed.
Cardano derivation differs significantly between wallet vendors. BTCRecover checks all three Shelley derivation types by default, which can have a noticeable performance impact. If you know which wallet generated the seed, disable the other two types in derivationpath-lists/ADA.txt.
Path prefix
Derivation type
Used by
icarus:1852'/1815'/0'
Icarus
Adalite, Yoroi, Daedalus, Atomic, Ellipal, Trezor T (< 24 words)
ledger:1852'/1815'/0'
Ledger
Adalite and Yoroi with Ledger Nano
trezor:1852'/1815'/0'
Trezor
Adalite and Yoroi with Trezor T (24-word seeds only)
Only Shelley-era addresses are supported. Byron-era addresses are not currently supported.
Sharing an address format does not guarantee that a coin uses the same derivation function. Custom path recovery is best-effort for unsupported coins.
If you want full support added for a coin not listed above, test it, then submit a pull request with a unit test and any required address-handling code.