> 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/dashboard-and-account/wallets-page.md).

# Manage strategy wallets

The Wallets page manages your strategy wallets: create them, back them up, fund them, see their balances and orders, link them to strategies, and empty them. For what a strategy wallet is and where its key lives, read [Wallets in Surge](/core-concepts/wallets-in-surge.md) first.

### The wallet list

Each wallet card shows its label, address, ADA and token balances (refreshed about every minute, and only accepted as "zero" after two consecutive empty readings so a blip never shows a drained wallet), connection status (Connected / Not connected / Not backed up), the linked strategy if any, and actions. A capacity bar shows how many of the 20 wallet slots are used. A dismissible "how wallets work" explainer sits at the top.

### Wallet actions

| Action                | What it does                                                                                                                                                                |
| --------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Generate              | Creates 1 or more new wallets (count preset or slider), with a label and optional immediate strategy assignment. Asks you to choose a folder for key files first            |
| Import                | Drag-and-drop a CSV/JSON export (contains private keys) to add wallets from another device                                                                                  |
| Export / Back up all  | Downloads every wallet's key. Store safely                                                                                                                                  |
| Back up (per wallet)  | Registers the wallet with Surge (proof of ownership by signature) `[VERIFY: whether this also downloads the key file, or whether "Download key file" is a separate action]` |
| Fund                  | Sends ADA and optionally one token from your browser wallet into this wallet; browser wallet signs                                                                          |
| Send                  | Builds a transfer out of this wallet to any address; strategy wallet signs after the transaction guard                                                                      |
| Receive               | Address and QR code                                                                                                                                                         |
| Sweep                 | Opens Surge's separate sweep tool in a new tab; you carry the key file across yourself                                                                                      |
| Rename                | Label, up to 64 characters                                                                                                                                                  |
| Activate / Deactivate | Hide from builders and the swap page without deleting                                                                                                                       |
| Delete                | Removes the wallet from Surge and this browser. Empty it first                                                                                                              |
| Refresh balances      | Forces a re-read                                                                                                                                                            |

### Wallet details

Click a wallet for: the token table with values, an estimate of the minimum ADA the wallet must keep to hold its tokens, on-chain transaction history (paginated), the linked strategy resolved from every strategy type, and additional actions: **link / unlink strategy**, **reconnect from key file**, **export keys**, and **Recover stuck order** for any order from this wallet that is still open at a DEX (see [Cancelling stuck orders](/orders-and-transactions/cancelling-stuck-orders.md)).

The Send form warns when the amount would leave less ADA than the wallet's tokens require, and refuses amounts that overshoot the balance.

### Funding tips

* Fund with at least the builder's **Required balance** plus a few ADA. Grid needs roughly 10–12 ADA of spare ADA at all times to keep going.
* A funding transfer takes a minute or two to land; a confetti banner confirms it once the balance rises.
* Tokens whose decimals are unknown to Surge cannot be amount-entered in the Fund form until the registry knows them.

### Sweep funds

The dashboard's sweep-profits dialog is not functional in the current build. To move funds out of a strategy wallet use **Send** or **Sweep** here.


---

# 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://docs.surgecardano.com/dashboard-and-account/wallets-page.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.
