> ## 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.

# Solana

> What a Trustodian Solana wallet is, the all-hardened path, and importing into Phantom or Solflare

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

SLIP-0010 on the ed25519 curve, with **every level hardened**. Note the apostrophe after the final `0`.

## The index varies the account

`{index}` sits at the account level, not at an address leaf. Your first Solana wallet is account 0,
your second is account 1, and each is an independent subtree.

| Trustodian Solana wallet | Path | Account in Phantom or Solflare |
| :- | :- | :- |
| 1st | `m/44'/501'/0'/0'` | Account 1 |
| 2nd | `m/44'/501'/1'/0'` | Account 2 |
| 3rd | `m/44'/501'/2'/0'` | Account 3 |

Adding an account in a Solana wallet walks up the same level the Trustodian index walks up, so the
ordering matches. But a tool that restores only the first account shows wallet #1 and nothing else,
with no hint that the rest exist.

> [!NOTE]
>
> Because the path is fully hardened, no public key can derive its children. There is no Solana
> equivalent of scanning an account xpub for addresses: a tool either holds the seed and derives, or it
> cannot enumerate anything. A Solana wallet therefore finds accounts by deriving candidates and
> checking which have on-chain activity, which means an account that has never transacted will not be
> found for you.

## The path variants that produce different wallets

Solana wallets have historically used several conventions. Only the first matches Trustodian.

| Path | Result |
| :- | :- |
| `m/44'/501'/{index}'/0'` | **Correct.** What Trustodian derives |
| `m/44'/501'/{index}'` | A different key. One level shorter |
| `m/501'/{index}'/0/0` | A different key again. The deprecated legacy form |

If a wallet offers a derivation path chooser, take the option ending in `/0'` **after** the account
index: four levels, all hardened.

## Phantom

**1. Install Phantom from phantom.app**

Type the domain yourself.

**2. Import the secret recovery phrase**

Choose the import option rather than creating a new wallet, and enter the words.

**3. Let Phantom discover accounts, then check what it found**

Phantom restores the accounts it can find prior on-chain activity for, across the derivation
conventions above. It does not ask you to choose a path. Compare the addresses it restored against
your Trustodian Solana wallets.

**4. Add accounts for anything it missed**

Add them from within the wallet after setup; each new one takes the next account index, in order.

## Solflare

Solflare's import has an advanced option that exposes the derivation path, which makes it the better
choice when you need to be certain which convention is in use.

**1. Install Solflare from solflare.com**

Type the domain yourself.

**2. Import using the recovery phrase**

Enter the words in order.

**3. Open the advanced option and set the path**

Choose the four-level all-hardened form, `m/44'/501'/{index}'/0'`, rather than the three-level one.
Solflare's default is not necessarily the same as Phantom's, so set it deliberately rather than
accepting what is offered.

**4. Verify the address before using it**

If the path is right, the first address matches your first Trustodian Solana wallet.

## Verifying

Compare the address, not the balance. If account 0 does not match, do not keep adding accounts
hoping the right one appears: every later account derives from the same wrong root. See
[Troubleshooting](https://trustodian-recovery.mintlify.site/troubleshooting.md).

## Vaults

Solana vaults use the Squads program, whose owners and threshold live on-chain. Once your owner key
is imported, a Squads interface reading the chain finds the vault and your membership in it.

> [!WARNING]
>
> **A Solana vault has two addresses, and the one holding the funds is not the one to keep.**
>
> The address you send to is a vault PDA, derived from the Squads **config account**. That derivation
> runs one way: the config account produces the vault address, and the vault address cannot be turned
> back into the config account. A Squads interface has to be pointed at the config account.
>
> Your [Recovery Kit](https://trustodian-recovery.mintlify.site/recovery-kit.md) records both, with the config account marked. A Solana vault kept
> by its funds address alone cannot be reopened.

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.