> 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/what-is-backpack-wallet.md).

# What is Backpack Wallet?

Backpack is a **security conscious self-custodial crypto wallet** for Solana, Ethereum, Optimism, Arbitrum, Polygon, Base, Sonic and many more blockchains.  It enables you to have complete control over their crypto assets.

## **Backpack Wallet is used for all your crypto needs.**

* sending and receiving crypto assets
* swapping crypto tokens
* staking crypto tokens
* viewing, securing and trading NFTs
* connection with cold storage hardware wallets Ledger, Trezor and Keystone
* multi-sig wallet protection
* connecting to developer testnets

[**Download the Backpack wallet for browser, iOS and Android here.**](https://backpack.app/)

***

## Backpack is a secure place to store NFTs.

NFT **collection locking** is an easy to use feature that **automatically rejects transaction requests** when an NFT is locked in the Backpack Wallet. Note: Collection locking is currently limited to select projects.

<figure><img src="https://cdn.prod.website-files.com/669641f210a1019f2d8231fa/66e0be450f09a6f6779a3aad_66e0be2da1e582580bd26ad5_what_is_backpack_wallet.png" 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 following URL with the `ask` and `goal` query parameters:

```
GET https://support.backpack.exchange/wallet/what-is-backpack-wallet.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 `build a script that syncs our docs to a CMS` 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.