> For the complete documentation index, see [llms.txt](https://zardoz.gitbook.io/zardoz-docs-1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zardoz.gitbook.io/zardoz-docs-1/bundle-trading.md).

# Bundle trading

## Bundle trading

The **Bundle** panel on a token page fires coordinated **buys or sells** across your **vault trading wallets** in parallel.

Create vault wallets first under **Portfolio → Trading wallets**.

### Panel overview

| Control             | Behavior                                                              |
| ------------------- | --------------------------------------------------------------------- |
| **Buy / Sell mode** | Switches quick presets — ETH amounts (buy) vs sell % (sell)           |
| **Top presets**     | Applies to selected wallets, or **all** if none selected              |
| **Pencil icon**     | Edit preset sizes                                                     |
| **Per-wallet row**  | Custom ETH amount + ▶, or tap row preset only                         |
| **DUMP**            | Sell 100% on selected (or all) vault wallets                          |
| **All excl DEV**    | Sell everything except wallets tagged **DEV** (launch bundle wallets) |
| **Whales**          | Outside holders ≥1%, excluding LP and your vault addresses            |

### Live row data

Each vault row refreshes every few seconds:

* ETH balance
* Token bag size
* Hold % of supply
* Unrealized PnL (where calculable)

Fund **each** vault before firing — empty wallets fail that row only; others still execute.

### Typical workflows

#### Seed a launch

1. Launch token with optional bundle buy in [/launch](https://zardoz.fun/launch)
2. Tag participating vaults as **DEV**
3. Later: **All excl DEV** to exit bundle while keeping dev allocation

#### Snipe with size split

1. Generate 5–20 vault wallets
2. Fund each with equal ETH
3. Token page → Bundle → Buy mode → hit top preset on all rows

#### Exit

1. Switch to Sell mode
2. Use 25/50/75/100% presets per row or **DUMP**

### DEV tag

Mark wallets that participated in **your** launch bundle. Enables:

* **All excl DEV** — retail dump without touching dev wallets
* Visual distinction in bundle list

Set tags in Portfolio → Trading wallets or via `PUT /api/trading-wallets`.

### Gas & slippage

Each vault row is a **separate transaction**. Budget:

```
total_gas ≈ num_wallets × gas_per_swap
```

Same slippage setting applies per swap as the main trade panel.

### Security

Vault private keys are encrypted in browser local storage. Download backups when importing. Zardoz servers never receive vault keys for browser-only vaults (session trading wallets API is for Google-linked vault sync — see Wallets).

Next: Launching · Wallets


---

# 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://zardoz.gitbook.io/zardoz-docs-1/bundle-trading.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.