> For the complete documentation index, see [llms.txt](https://docs.j.tools/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.j.tools/tools/boost/pump-volume.md).

# Pump Volume

[Pump Volume](https://j.tools/en/tools/pump-volume) is a J Tools module for generating trading volume on a Pump.fun token through coordinated multi-wallet activity. It is aimed at Pump.fun token creators and promoters who want visible volume on their token. The tool is being rebuilt, so this page describes what it is meant to do and what you can use today.

{% hint style="warning" %}
**Coming soon.** Pump Volume is a placeholder in the current build. It performs no on-chain action, charges no fee, and cannot generate volume yet. Everything below is the planned design, not live behavior.
{% endhint %}

{% hint style="warning" %}
**About fees.** Every action has two costs: the Solana **network fee** paid to validators, and the **J Tools platform fee**. The platform fee always shows in the app before you confirm, and nothing is charged until you sign. Fees can change over time, so trust the in-app summary rather than a number you saw once.
{% endhint %}

## What it will do

The planned tool points a coordinated set of wallet actions at one Pump.fun token to drive trading volume on it. Based on the current design, that means:

* A single target: the Pump.fun token mint you want the campaign to run against.
* Coordinated multi-wallet actions instead of a single manual swap.
* Tighter execution controls and anti-error checks built for volume campaigns.

None of this is wired into the handler yet. The current build runs nothing on-chain.

## Current status

* The tool page shows a "coming soon" screen only. There is no live form or run button.
* The handler takes no real input and always returns a fixed "coming soon" result. Validation passes unconditionally because there is nothing to validate.
* No DEX or platform routing, fee, or execution step is implemented.
* The page is excluded from search indexing while it is rebuilt.

## What to use meanwhile

If you want volume or maker activity on Solana while Pump Volume is rebuilt, these are the related boost tools:

* **Volume Bot** for automating volume cycles with execution logic you set.
* **Pump Comment** for activity on a Pump.fun token's comment feed.

If you are still launching a Pump.fun token, **Pump.fun Create** mints the token and gets it onto the [bonding curve](/getting-started/glossary.md) first. See [Related tools](#related-tools) for the links. Note that Volume Bot and Pump Comment are also being built out, so check each page for its current status.

[**See Pump Volume in the app →**](https://j.tools/en/tools/pump-volume)

## Before you start (when it ships)

When Pump Volume goes live, expect the usual J Tools setup:

* A connected wallet ([how to connect](/getting-started/quick-start.md)).
* Enough SOL for network fees and any platform fee shown in the in-app fee summary.
* The Pump.fun token you want the campaign to target, picked with the built-in token selector.

The exact inputs are not final. The current source defines only a target token-mint field, so this list may change before launch.

{% hint style="info" %}
Pump Volume is flagged as higher-risk in its configuration because the planned design coordinates many wallet and transaction signing operations, the kind of pattern you also see in [bundles](/concepts/bundles-and-jito.md). Wallets like Phantom tend to warn on flows that sign in bulk. That is a property of the planned design, not a sign that anything is wrong. See the note below.
{% endhint %}

{% hint style="info" %}
**About wallet warnings.** Some tools sign more than one thing in a single step, for example creating a token and its metadata together. Phantom can show a caution banner for these multi-step transactions. The banner is expected here and does not mean something is wrong. Read what you are signing, then approve.
{% endhint %}

## If something goes wrong

The tool is not active, so there are no live errors to troubleshoot yet. Once it ships, common issues and their fixes will be listed here, with the full set in the [Error codes reference](/reference/error-codes.md).

## FAQ

<details>

<summary>Can I use Pump Volume today?</summary>

No. It is a coming-soon placeholder being rebuilt with tighter execution controls and improved anti-error checks. The page shows a "coming soon" screen and the tool does not run on-chain. Use [Volume Bot](/tools/boost/volume-bot.md) or [Pump Comment](/tools/boost/pump-comment.md) in the meantime, and check each for its current status.

</details>

<details>

<summary>What will it cost?</summary>

No fee is configured today, because the tool has not launched yet. When Pump Volume ships, the cost appears in the in-app fee summary before you confirm, and on the [Fee schedule](/reference/fee-schedule.md). Ignore any fee figures quoted elsewhere for this tool until it launches.

</details>

<details>

<summary>Does it only work with Pump.fun tokens?</summary>

That is the intent. The planned design targets a single Pump.fun token mint per campaign. Pump.fun is a bonding-curve launchpad, not a pool DEX, so the flow is built around that. Final platform support is decided when the tool is built.

</details>

<details>

<summary>Why does my wallet flag this tool as risky?</summary>

The planned design coordinates many wallet actions, which Phantom and similar wallets treat as higher-risk. The tool's configuration carries a high risk level for that reason. It is a config flag tied to the intended design, not observed behavior, since the tool signs nothing yet.

</details>

<details>

<summary>Does J Tools hold my keys?</summary>

No. J Tools is non-custodial. It never holds or requests your keys, and you sign every transaction in your own wallet. That holds for Pump Volume once it ships.

</details>

## Related tools

{% content-ref url="/pages/SyDtWrNajVH0Y5kGtFI1" %}
[Volume Bot](/tools/boost/volume-bot.md)
{% endcontent-ref %}

{% content-ref url="/pages/tgyrWGKVBipag0ha0T5S" %}
[Pump Comment](/tools/boost/pump-comment.md)
{% endcontent-ref %}

{% content-ref url="/pages/xENB3pWkEElG6NsYww6X" %}
[Pumpfun Create](/tools/launch/pumpfun-create.md)
{% endcontent-ref %}

{% hint style="success" %}
**J Tools is non-custodial.** We never hold your private keys and never ask for them. Every transaction is built in your browser and signed by your own wallet. If any page ever asks you to paste a private key, stop, close it, and let us know.
{% 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 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.j.tools/tools/boost/pump-volume.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.