> For the complete documentation index, see [llms.txt](https://docs.eth.solhuger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eth.solhuger.com/project/buy.md).

# Buy

Generate wallets and run multi-wallet buys.

Open a project from the Dashboard, then go to **Project → Buy**. The active project name (e.g. `A-1`) is shown beside the title.

<figure><img src="https://437700151-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fg55WaahfDDbRuav0Znxp%2Fuploads%2Fgit-blob-2a932be054b15401c0e5e9f8270dc5326ad13d7b%2F08-buy.png?alt=media" alt="Buy tokens page"><figcaption><p>Buy tokens page</p></figcaption></figure>

## Configuration

| Field                     | Description                                                                                            |
| ------------------------- | ------------------------------------------------------------------------------------------------------ |
| **Token Address**         | Contract address of the token to buy                                                                   |
| **Template**              | Contract template used by the token (must match the deployed token)                                    |
| **Zombie Wallet #1 / #2** | Helper wallets required by the template. Hover the **?** icon for details and set each with the ⋮ menu |
| **Dead Blocks**           | Number of blocks to wait before buying after trading is enabled (default `2`)                          |

## Toolbar

| Button               | Action                                        |
| -------------------- | --------------------------------------------- |
| **Generate Wallets** | Create new project wallets                    |
| **Download Wallets** | Export wallets for backup                     |
| **Set Token Amount** | Set how many tokens each selected wallet buys |
| **Set ETH Amount**   | Set ETH to allocate to each selected wallet   |
| **Save Project**     | Save the current configuration                |

The header shows **Selected** (wallets ticked) and your **Token balance**.

## Wallets table

| Column             | Description                             |
| ------------------ | --------------------------------------- |
| **Address**        | Wallet address                          |
| **ETH Balance**    | ETH currently in the wallet             |
| **Token Balance**  | Token balance of the wallet             |
| **Tokens To Buy**  | Amount this wallet will buy             |
| **Additional ETH** | Extra ETH reserved, for example for gas |

Use the checkbox in the header to select all wallets.

## Footer controls

| Control                   | Description                                                       |
| ------------------------- | ----------------------------------------------------------------- |
| **Target Wallet**         | Address that receives collected ETH                               |
| **Collect All ETH**       | Sweep ETH from project wallets to the target wallet               |
| **Gas multiplier (125%)** | Gas price multiplier. Use the refresh icon to update the estimate |
| **Simulate**              | Dry-run the buy to check it will succeed                          |
| **Enable & Buy**          | Enable trading and execute the buys                               |

## Recommended flow

1. Enter the **Token Address** and confirm the **Template**.
2. Set the Zombie wallets and Dead Blocks.
3. Click **Generate Wallets**, then **Download Wallets** and back them up.
4. Fund the wallets with ETH.
5. Use **Set Token Amount** and **Set ETH Amount**.
6. Click **Save Project**.
7. Run **Simulate** and fix any errors.
8. Click **Enable & Buy**.

{% hint style="danger" %}
Back up wallet files before funding them. Anyone with a wallet's private key controls its funds.
{% endhint %}


---

# 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.eth.solhuger.com/project/buy.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.
