> 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/holder-booster.md).
# Solana Holder Booster: Add Real Holders
Holder Booster is an automated tool that creates a batch of brand new wallets and fills each one with your token. The tokens come from one real on-chain market buy: a short-lived distributor wallet buys a small bag, then splits it across all the new wallets. Every wallet ends up holding the token, so your unique-holder count goes up. You sign one funding transaction, and a J Tools worker then runs the buy and the distribution for you.
## What it is
Holder Booster generates a set of fresh wallets in your browser, then makes one small market buy of your chosen token through pump.fun, PumpSwap, or Raydium from a short-lived distributor wallet. The distributor fans the purchased tokens out to every fresh wallet in chunked on-chain transfers, paying each wallet's token-account rent along the way. Because each wallet finishes the run holding a non-zero token balance, it counts as a distinct holder. The holder wallets never hold SOL and never sign anything. You choose how many holders to add and how the distribution is paced; the buy size and slippage are set by the platform to keep each new holder as cheap as possible. The whole batch is funded from your own wallet, so it is traceable to you on-chain.
## Why use this tool
There are a few honest, practical reasons to use it:
* **Holder-count visibility.** Many token explorers, screeners, and community trackers surface a unique-holder number. Some projects want that number to reflect many wallets that actually hold the token instead of a single concentrated one.
* **Seeding a fresh token.** A token that just launched can start with one or two holders. Spreading purchased tokens across many wallets gives a more distributed early holder base.
* **Tokens from a real buy.** Unlike sending tokens you already hold to a list of addresses, the tokens here come from one live market buy and land in brand new wallets created for the run. On-chain the footprint is one trade plus token distributions to the new wallets, which keeps the cost per holder close to the account rent.
For the limits of that, see [Responsible use](#responsible-use) below.
## How it works (under the hood)
At a user level, the flow is simple. You configure a run, then the tool generates one short-lived distributor wallet plus all of your fresh holder wallets directly in your browser. You sign a single funding transaction that sends SOL to the distributor and the platform fee to the platform wallet. From there a J Tools worker takes over: it broadcasts your funding transaction, makes one real market buy of a token bag from the distributor, then fans the tokens out to every holder wallet in chunked transfers until the batch is complete or you stop it. The distributor pays each holder wallet's token-account rent; the holder wallets themselves never hold SOL and never sign.
The tool is non-custodial. You authorize the wallets by generating them yourself and downloading their keys in a backup file; J Tools never asks for or stores the private key of your connected wallet. The worker signs only with the distributor wallet created for this run; the holder wallets' keys never leave your browser and exist only in the backup you download. You keep the backup, so you keep control of the tokens in those wallets.
## When to use it
* Your token is live and tradable on pump.fun's bonding curve, PumpSwap, or Raydium.
* You want your unique-holder count to reflect many wallets holding tokens that were really bought on a live market.
* You accept that the new wallets are funded from your own wallet, so cluster tools like Bubblemaps can still link them back to you.
If you only need to send tokens you already hold to a list of addresses you control, use [Multi Sender](/tools/wallets/multi-sender.md) instead. Holder Booster is for creating brand new holder wallets and sourcing their tokens from a live market buy.
After a run, open the mint in [J Map](/tools/utilities/j-map.md) to see how the top of the holder table reads to an outsider. J Map only draws holders down to the depth you pick, up to the top 500, so the small fresh wallets a booster run creates usually sit below that cutoff and never appear. What you are checking there is the shape of the wallets that do carry weight, and whether any of them trace back to addresses you control.
## Before you start
* A connected wallet that can sign a versioned transaction ([how to connect](/getting-started/quick-start.md)).
* A token that is tradable on pump.fun, PumpSwap, or Raydium. [Token-2022](/concepts/spl-vs-token2022.md) mints are blocked when they carry a transfer hook, a transfer fee, a permanent delegate, the non-transferable or confidential-transfer extension, or a default account state of frozen. A plain freeze authority does not block the run and does not warn you: the transfers still land and the wallets still count as holders.
* Enough SOL in your wallet to cover the bag-buy, the per-holder account rent, and the platform fee. The page checks your balance before you sign.
* A place to save the wallet backup file. You cannot start a run until you download it. It is the only copy of the new wallets' private keys.
## Step by step
{% stepper %}
{% step %}
### Configure the run
Pick your token with the selector, then set the holder count (1 to 2000 per run) and the pacing. The buy size and slippage are set automatically by the platform. Three tiles update as you type: the holder count, an estimated total cost, and how long the run will take. Below them a single **Total to pay** figure covers the bag-buy, the per-holder rent and the platform fee together, with a footnote naming the \~0.00204 SOL rent and the 0.001 SOL fee per holder. The bag-buy is never shown as its own line.
{% endstep %}
{% step %}
### Build the plan
Click **Build plan**. J Tools runs a quick token check, then generates one short-lived distributor wallet plus all of your fresh holder wallets right in your browser. Nothing about those wallets leaves your machine yet.
{% endstep %}
{% step %}
### Download the wallet backup
Save the backup JSON. It holds the private key of every holder wallet that was just created, and it is the only way to recover their tokens (or reclaim the account rent) later. The run stays locked until this file is downloaded.
{% endstep %}
{% step %}
### Fund and start with one signature
J Tools builds a single funding transaction: SOL to the distributor wallet, then the platform fee to the platform wallet. Approve it once in your wallet. The signed transaction, the plan (the holder addresses and what each one receives), and the distributor wallet's key go to the J Tools worker. The holder wallets' keys never leave your browser; they exist only in your downloaded backup.
{% endstep %}
{% step %}
### Watch it run
The worker broadcasts the funding transaction, buys the token bag from the distributor, then distributes tokens to every holder wallet in chunked transfers. The page polls for progress every few seconds and shows completed and failed counts, worker logs, and a live ETA. When it finishes, you get links to the funding transaction on Solscan, the token's holders view, and Token Snapshot so you can verify the result.
{% endstep %}
{% endstepper %}
[**Open Holder Booster in the app →**](https://j.tools/en/tools/holder-booster)
## The options, explained
* **Token:** The SPL mint the run buys and distributes. Pick it with the built-in selector. It must be tradable on pump.fun, PumpSwap or Raydium. Mints with no route are blocked, and so are Token-2022 mints carrying a transfer hook, a transfer fee, a permanent delegate, the non-transferable or confidential-transfer extension, or a frozen default account state. Blocked mints are refused before anything is charged.
* **Holder count:** How many fresh wallets to create, from 1 to 2000 per run. Default 15. Quick presets set the count to 100, 500, or 1000.
* **Pacing:** **Fast** runs the distribution chunks back to back. **Drip** spreads them evenly over a window. Default is Fast.
* **Drip window:** Only used with Drip pacing. How long to stretch the distribution over: presets of 30 minutes and 1, 3, 6, 12, or 24 hours, or type a custom value between 5 minutes and 72 hours. Default 6 hours.
The buy amount is not an input. The platform buys the smallest viable bag for your holder count, with slippage set automatically, and most of the per-holder cost is the 0.00204 SOL token-account rent. The total therefore grows with the number of holders you add, not with the size of any buy.
## Fees and costs
{% 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 %}
**Current platform fee: 0.001 SOL per holder wallet, collected once inside the funding transaction.** The app shows the exact amount before you sign.
| Cost | Amount |
| -------------------- | -------------------------------------------------- |
| J Tools platform fee | 0.001 SOL per holder wallet |
| Solana network fee | a small amount per transaction, paid to validators |
Example: 100 new holders cost 0.1 SOL in platform fees.
On top of the platform fee you pay Solana network fees: one for the funding transaction, one for the single bag-buy, and one per distribution transaction, which seeds six wallets at a time. Counting everything, budget about 0.00314 SOL per holder: 0.00204 SOL of token-account rent, roughly 0.0001 SOL of network headroom, and the 0.001 SOL fee. The bag-buy is one-time and small, from 0.005 SOL on a short run up to about 0.021 SOL at 2000 holders.
## Responsible use
The tokens these wallets hold come from a real buy, but the holders are not organic demand. You are paying to add wallets you control, so a high holder count created this way is artificial activity. It can mislead buyers who read holder count as a sign of genuine interest, it may breach the rules of explorers, screeners, or trading platforms, and depending on where you operate it may carry legal risk. Use it transparently, do not present the result as organic, and treat the decision as your own responsibility.
## Security and custody
* **What the bot is authorized to do.** The worker signs only with the distributor wallet created for this run, to make the single bag-buy and distribute the tokens. It never sees the holder wallets' keys and does not touch any other wallet you hold.
* **You keep the keys.** The backup JSON is the only copy of the holder wallets' private keys, saved with no password. It is how you recover their tokens later. Store it safely the moment you download it.
* **Stop control.** A run only starts once you sign the funding transaction, and a **Cancel** button sits at the top of the progress card for as long as it is running. Cancelling stops the remaining chunks. Holders already seeded keep their tokens, and the unspent SOL stays in the distributor wallet, which is in your backup. The platform fee is charged up front for the full holder count and is not refunded for the part you cancelled.
## Common mistakes and troubleshooting
* **Token is not tradable.** The pre-flight check could not find a market for the mint, so the run is refused before anything is charged. Make sure the token is live on pump.fun, PumpSwap, or Raydium first.
* **Mint is blocked by a Token-2022 extension.** The run is refused before anything is charged when the mint carries a transfer hook, a transfer fee, a permanent delegate, the non-transferable or confidential-transfer extension, or a frozen default account state. A freeze authority on its own does not block the run and produces no warning, though the holders you create could be frozen later if you keep it. Clear it with [Revoke Freeze](/tools/secure/revoke-freeze.md) or [Make Immutable](/tools/secure/make-immutable.md) if you want that off the table.
* **Not enough SOL.** The balance check ran before you signed and your wallet is short. Top up to cover the bag-buy, the per-holder rent, and the platform fee, then try again.
* **Start is blocked.** You have not downloaded the wallet backup yet. Save it, then start.
* **Some distributions failed.** A few chunks can fail under load or RPC congestion. The progress view shows the failed count and the logs. Wallets in a failed chunk receive nothing, and their share stays in the distributor wallet, which is in your backup file. The platform fee was charged for every holder you planned, not for every holder that landed, and there is no refund for the difference. If every chunk fails the run is marked failed with `ALL_HOLDERS_FAILED`.
* **Lost the backup.** The backup is the only copy of the holder wallets' keys. Without it you cannot recover their tokens. There is no reset.
For the full list, see the [Error codes reference](/reference/error-codes.md).
## Related tools
{% content-ref url="/pages/ABVX2mBQDoCv7DEdVmKp" %}
[Multi Sender and Airdrop](/tools/wallets/multi-sender.md)
{% endcontent-ref %}
{% content-ref url="/pages/IkDuDGRTPYj2wcjtbIre" %}
[Token Holder Snapshot](/tools/utilities/token-snapshot.md)
{% endcontent-ref %}
{% content-ref url="/pages/7CPBHR61Y6akMdkeSBGW" %}
[Batch SOL and Token Collector](/tools/wallets/batch-collector.md)
{% endcontent-ref %}
{% content-ref url="/pages/biKUAmB4vuIiL2aReFe0" %}
[J Map: Token Cluster Map](/tools/utilities/j-map.md)
{% endcontent-ref %}
{% hint style="success" %}
**J Tools is non-custodial.** We never store or transmit your private keys and never ask for your seed phrase. Every transaction is signed in your own browser, and nothing about a key ever reaches our servers. A few multi-wallet tools do let you paste private keys for throwaway hot wallets, which stay in your browser tab and are used only to sign locally. Never paste a key tied to long-term holdings, and if a page ever asks for your seed phrase, stop and close it.
{% 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/holder-booster.md?ask=&goal=
```
`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.