> For the complete documentation index, see [llms.txt](https://support.backpack.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.backpack.exchange/wallet/actions/multisig.md).

# Multisig

Import your cold storage hardware wallets into Backpack and then connect Backpack to a multisig creation platform.

***

### Step-by-step guide

#### **1. Import your cold storage hardware wallet(s) to Backpack.**

* Open the Settings menu and select 'Add Account'
* Select 'Import Wallet' and choose the appropriate network
* Select 'Use a hardware wallet' and choose 'Use a Keystone wallet'
* Follow directions on device to approve connection
* Proceed with wallet setup instructions

#### **2. Visit a reputable multisig wallet platform that has integrated Backpack Wallet and initiate the setup process.**

* [Squads (Solana) (Recommended)](https://squads.so/)
* [Realms (Solana)](https://app.realms.today/realms/new)
* [Safe (Ethereum)](https://safe.global/)

#### **3. Utilize Backpack Wallet as the interface to manage signatures and transactions.**

**Note:** You will sign transactions on your cold storage hardware device using Backpack Wallet as the connection point.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.backpack.exchange/wallet/actions/multisig.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.