> For the complete documentation index, see [llms.txt](https://asigna.gitbook.io/asigna/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://asigna.gitbook.io/asigna/bitcoin-multisig/recovery/ledger-setup-in-sparrow.md).

# Ledger Setup in Sparrow

This guide outlines the steps to recover your Ledger multisig setup using Sparrow Wallet. Follow these quick steps to regain access to your multisig wallet:

#### ➱ Create a New Wallet

In Sparrow Wallet, start by creating a **New Wallet**. 

<figure><img src="/files/f9xQdPLqZnLRZpjQqUMI" alt="" width="375"><figcaption></figcaption></figure>

Choose the **Multi Signature** policy type and select **Native SegWit (P2WSH)** script type. Configure the cosigners with the same number of owners and the signing threshold that matches your Asigna Vault.

<figure><img src="/files/ydjkOXJlJCBgBMkWU9tG" alt=""><figcaption></figcaption></figure>

#### ➱ Add Your Ledger Device

Click **Connected Hardware Wallet** and **Scan** button to connect your Ledger device and add as one of the multisig cosigners.

<figure><img src="/files/c3rDTNdEotSY0QpomRtn" alt=""><figcaption></figcaption></figure>

#### ➱ Set the Derivation Path

Turn off the **Validate Derivations** in Sparrow -> Preferences.

<figure><img src="/files/uF1PKZhpBxRfPPbUcqSt" alt="" width="563"><figcaption></figcaption></figure>

Locate the derivation path of your Ledger account in the **Permissions** section of your Vault.

<figure><img src="/files/rYtYIMdRT3WkYQmlJ4ME" alt=""><figcaption></figcaption></figure>

Copy your derivation path and go back to Sparrow. Click **Show derivation...** to reveal the input for the custom derivation path. Paste the copied derivation and click **Import** button.

<figure><img src="/files/wfG9B7EjKopvbp5xFHzT" alt="" width="563"><figcaption></figcaption></figure>

#### ➱ Verify the Fields

Confirm that the **Master Fingerprint** and **xPub** fields in Sparrow match the ones displayed in your Asigna Vault.&#x20;

If there’s a discrepancy, please contact [support](/asigna/appendix/contact-us.md).

<figure><img src="/files/C9QFSntSiDBI8jpxJfuu" alt=""><figcaption></figcaption></figure>

#### ➱ Add Other Owners' Wallets

To complete the multisig setup, add the Ledger accounts of other cosigners.

There are 2 ways to do it:

1. If you own multiple Ledger devices/accounts within the same multisig setup, add each additional Ledger account by repeating the previous steps.
2. Use **xPub/Watch Only Wallet** method. To do this, you need to obtain each owner’s **xPub**, **derivation**, and **master fingerprint** from the **Permissions** section of your Vault.

<figure><img src="/files/ao9HUTOTzhiU3PHdnlk8" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/aKhtq3dDOMFHPr8ZhBpL" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/7pUuKAbPg1aLITbkgvB4" alt=""><figcaption></figcaption></figure>

#### ➱ Verify the Setup

After adding all cosigners, click **Apply** in Sparrow Wallet. In the **Addresses** tab check that the first generated address for your multisig setup matches the one displayed in your Asigna Vault.&#x20;

If you encounter any issues, please contact [support](/asigna/appendix/contact-us.md).

<figure><img src="/files/IO6ISfqird4AxvvmC2QW" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://asigna.gitbook.io/asigna/bitcoin-multisig/recovery/ledger-setup-in-sparrow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.