Skip to main content
BIP-44 on secp256k1. The same path and the same key on every EVM network Trustodian supports: Ethereum, Polygon, BNB Smart Chain, Base, Arbitrum, Optimism and Avalanche. Addresses are checksummed hex beginning 0x, one per index.
The network is not part of the key. Your Ethereum address and your Polygon address are the same string, and the balance you see depends only on which network the wallet is pointed at. So an imported EVM wallet showing nothing is almost always the network selector, not the phrase — check that before anything else.

The index

{index} is the address leaf, so all your EVM wallets sit under one account, m/44'/60'/0'. This is also how account numbering works in a standard wallet, so the mapping is direct: To reach your third wallet, import the phrase and add accounts until three exist.
Some wallets offer a “Ledger Live” style path, m/44'/60'/{index}'/0/0, which varies the account rather than the address. It produces entirely different addresses from the same phrase. Trustodian does not use it.

How to recover it

MetaMask, Rabby, Trust Wallet

Step-by-step for all three, including what to do when a wallet asks for the path directly
Any BIP-39 wallet that derives on m/44'/60'/0'/0/{index} reproduces these addresses. That page walks through the three whose interface needs explaining; anything else you already know how to drive will work just as well.

Verifying

Compare the restored address, character for character, against the one shown in Trustodian. Do not judge by the balance. See Troubleshooting.

Vaults

EVM vaults are Gnosis Safe contracts. The owners and threshold live on-chain, so nothing has to be rebuilt: once your owner key is imported, any Safe interface pointed at the vault address finds the vault and your membership in it. Your Recovery Kit records that address, so you do not have to remember it. See How vaults recover.
Last modified on September 17, 2026