# Tips & Best Practices

## Wallets & treasury

**Start with wallets.** Create and fund the right **types** before launches or bots.

**Segregate wallet types.** Keep bundler, volume, and fast-volume pools separate.

**Treasury first.** Deposit to treasury, then **Fund** outward — easier than per-wallet CEX deposits.

**Randomize funding.** Use variation so balances are not identical on-chain.

**Sweep after campaigns** so capital returns to treasury for the next operation.

## Before running bots

**Pre-check balances** before volume or fast volume.

**Dry run Fast Volume** when trying a new token or wallet set.

**Use the Volume Calculator** for USD volume goals — always sanity-check native budget against real balances and gas.

## Launches & Solana

**Keep Tokens open** after launch for live metrics and campaign status.

On Solana, prefer **Jito hidden bundle** when you want independent-looking buyers with minimal transfer trails.

For Pump.fun metadata, follow PumpPortal guidance (Pinata for programmatic IPFS, canonical `ipfs.io` URIs in metadata).

## Subscriptions

**Pro for heavy use** — multiple concurrent volume bots, unlimited bundler/launches, and lower performance fees matter for active operators.

Renew before expiry to avoid interrupted campaigns.

## Security

* Never share exported wallet XML or private keys with anyone
* Use a strong, unique password for your Velox Labs account
* Log out on shared computers

## Liquidate All

Confirm token address and chain before liquidating. This sells the token from **every** wallet on that chain — it cannot be undone from the UI.


---

# Agent Instructions: 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:

```
GET https://docs.veloxlabs.xyz/tips-and-best-practices.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.