> For the complete documentation index, see [llms.txt](https://docs.leather.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.leather.io/wallet-and-security/wallet-derivation-paths.md).

# Understanding Wallet Derivation Paths

The derivation paths Leather uses for Native SegWit, Taproot and Stacks addresses, and how to find a Leather account in another wallet.

A derivation path tells a wallet which key to create from your Secret Key. One Secret Key can produce many keys, and each path leads to one of them. This is how one Leather wallet holds many accounts with different addresses.

## How to read a path

A path looks like `m/84'/0'/0'/0/0`. The parts are:

`m / purpose' / coin_type' / account' / change / address_index`

* `m` is the master key, created from your Secret Key.
* `purpose` sets the address type: `84` for Native SegWit, `86` for Taproot, `44` for Stacks.
* `coin_type` sets the network: `0` for Bitcoin mainnet, `1` for Bitcoin test networks, `5757` for Stacks.
* `account`, `change` and `address_index` pick one key within that branch.

An apostrophe marks a hardened step.

## Paths in Leather

Account numbers in paths start at 0, so Account 1 in Leather uses `0`.

| Address                | Account 1            | Account 2            | Account 500            |
| ---------------------- | -------------------- | -------------------- | ---------------------- |
| Bitcoin, Native SegWit | `m/84'/0'/0'/0/0`    | `m/84'/0'/1'/0/0`    | `m/84'/0'/499'/0/0`    |
| Bitcoin, Taproot       | `m/86'/0'/0'/0/0`    | `m/86'/0'/1'/0/0`    | `m/86'/0'/499'/0/0`    |
| Stacks                 | `m/44'/5757'/0'/0/0` | `m/44'/5757'/0'/0/1` | `m/44'/5757'/0'/0/499` |

For Bitcoin, the `account` part changes from one Leather account to the next. For Stacks, the last part, `address_index`, changes instead. On Bitcoin test networks, `0'` after the purpose becomes `1'`. Stacks paths are the same on every network.

Leather uses one address of each type per account. It does not move on to a new address after each transaction, as some Bitcoin wallets do.

## Stacks paths on Ledger

When you connect a Ledger device for Stacks, Leather asks for your "Preferred address standard":

* **Legacy Stacks derivation paths** (the default): the Leather paths in the table above, `m/44'/5757'/0'/0/<account>`. Most Stacks wallets use these.
* **Standard derivation paths:** `m/44'/5757'/<account>'/0/0`, where the `account` part changes. Ledger Live uses these.

If the device already has Stacks accounts in Leather, Leather keeps the standard those accounts use. See [How to View Ledger Live STX Funds in Leather Wallet](/balances/how-to-view-ledger-live-stx-funds-in.md).

## Find a Leather account in another wallet

You can restore your Secret Key in another wallet and point it at a Leather path to see the same addresses. In Sparrow, for example:

1. Restore your Secret Key as a new wallet in Sparrow.
2. On the "Settings" tab, under "Keystores", set "Derivation" to the path of the account you want, without the last two parts. For Account 2 with Native SegWit, that is `m/84'/0'/1'`.
3. Open the "Addresses" tab. The first receive address matches the address of that account in Leather.

Entering your Secret Key in another wallet exposes it to that software. Do this only with wallets you trust.

## Related

* [Account Privacy](/wallet-and-security/account-privacy.md)
* [Add or Restore Accounts](/get-started/add-or-restore-accounts.md)