> For the complete documentation index, see [llms.txt](https://docs.surgecardano.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.surgecardano.com/getting-started/supported-wallets.md).

# Supported wallets

Surge connects to Cardano browser-extension wallets that follow the CIP-30 standard. The following wallets are recognised:

| Wallet     | Notes                                        |
| ---------- | -------------------------------------------- |
| Eternl     | Also detected under its older "ccvault" name |
| Lace       |                                              |
| Ctrl       |                                              |
| OKX Wallet |                                              |
| Vespr      |                                              |
| Flint      |                                              |
| Typhon     |                                              |
| NuFi       |                                              |
| Yoroi      |                                              |
| GeroWallet |                                              |
| Begin      |                                              |

**Nami is not supported.** If you use Nami, import its seed into one of the wallets above.

### What you need from the wallet

* It must be installed as a browser extension and unlocked. Surge lists only the wallets it can actually see in your browser.
* It must be set to the same network as Surge. A mismatch aborts the connection.
* For staking, the wallet must use a normal "base" address (one with a stake key). See [Staking SURGE](/fees-tiers-and-staking/staking.md#who-can-subscribe).

### What the browser wallet is used for

Your browser wallet is your identity and your funding source. It signs a short login message (not a transaction), it funds your strategy wallets, and it signs manual swaps and sends. Automated strategy trades are signed by separate strategy wallets that Surge creates in your browser — see [Wallets in Surge](/core-concepts/wallets-in-surge.md).

### If your wallet is not listed

Extensions sometimes inject themselves a moment after the page loads (Surge's own reconnect to a previously connected wallet retries three times, one second apart, for this reason). Reload the page if your wallet is installed but missing. If it is still missing, the extension is either locked, disabled for this site, or not one of the wallets above.


---

# 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://docs.surgecardano.com/getting-started/supported-wallets.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.