> ## Documentation Index
> Fetch the complete documentation index at: https://trustodian-recovery.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# EVM wallets

> Restoring Trustodian EVM wallets in MetaMask, Rabby or Trust Wallet

Use this for every EVM network: Ethereum, Polygon, BNB Smart Chain, Base, Arbitrum, Optimism and
Avalanche. They all share one key and one address. What you are recovering, and why the index behaves
as it does, is on [Ethereum and EVM chains](https://trustodian-recovery.mintlify.site/ethereum.md).

The path you need:

```
m/44'/60'/0'/0/{index}
```

## MetaMask

MetaMask derives Ethereum accounts on that exact path by default, so nothing has to be entered.

**1. Install MetaMask from metamask.io**

Type the address in yourself. Extensions impersonating MetaMask are common in search results and
in extension stores.

**2. Choose to import an existing wallet**

On first run, pick the option to import a wallet using a secret recovery phrase rather than
creating a new one.

**3. Enter the phrase and set a local password**

The password is new and local to this browser. It is not your Trustodian password and has no
relationship to your phrase.

**4. Add accounts until your wallet appears**

Account 1 is index 0. Use MetaMask's account menu to add further accounts, which walk up the
index. Compare each address against the one shown in Trustodian.

> [!WARNING]
>
> MetaMask does not offer a custom derivation path for accounts created from the phrase. Everything
> Trustodian derives for EVM sits on MetaMask's default path, so this is not a limitation here, but it
> does mean you cannot use MetaMask to check a non-standard path if something looks wrong. Use Rabby
> for that.

## Rabby

Rabby exposes a derivation path choice when importing a seed phrase, which makes it the better tool
when you need to see which path is in use or reach a specific index.

**1. Import the seed phrase**

Choose the seed-phrase import option and enter the words.

**2. Select the standard BIP-44 path**

Where a path selector is offered, take the BIP-44 standard option, the one matching
`m/44'/60'/0'/0/{index}` and varying the last component. Avoid a "Ledger Live" style option,
which varies the account instead (`m/44'/60'/{index}'/0/0`) and produces entirely different
addresses from the same phrase.

**3. Select the addresses that match**

Rabby lists the addresses derived under the chosen path. Tick the ones matching your Trustodian
wallets; the list is in index order, so the first entry is index 0.

## Trust Wallet

Trust Wallet imports a multi-coin secret phrase and derives Ethereum on the standard BIP-44 path.

**1. Import with a secret phrase**

Choose the import option and enter the words. Trust will restore several chains at once from the
one phrase.

**2. Check the Ethereum address**

Compare it against your first EVM wallet in Trustodian.

> [!NOTE]
>
> Trust Wallet restores the first account on each chain. If you have more than one EVM wallet, use
> MetaMask or Rabby, which let you walk up the index.

## If a wallet asks for the path directly

Some tools want the **account** path and derive the index themselves; others want the full leaf path
for one address.

| The tool wants | Enter |
| :- | :- |
| An account path, plus an index or account number | `m/44'/60'/0'/0` with index `{index}` |
| A full path to one address | `m/44'/60'/0'/0/0` for your first wallet, `.../1` for the second |

`m/44'/60'/0'/0/0` and `m/44'/60'/0'/0` differ by one level: the first is an address, the second is
the account above it. If a tool rejects one, try the other.

## After the import

Compare the address, not the balance. If it does not match, or it matches and the funds are not
there, go to [Troubleshooting](https://trustodian-recovery.mintlify.site/troubleshooting.md). If the address matched, start with the network
selector — see [Ethereum and EVM chains](https://trustodian-recovery.mintlify.site/ethereum.md).

EVM vaults use Gnosis Safe, whose configuration is on-chain: point a Safe interface at the vault
address and your imported key is an owner of it. See [How vaults recover](https://trustodian-recovery.mintlify.site/vaults.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.