> 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). # Holder Booster [Holder Booster](https://j.tools/en/tools/holder-booster) creates a batch of brand new wallets and has each one make a small, real on-chain buy of your token through pump.fun, PumpSwap or Raydium. Every wallet ends up holding the token, so your unique-holder count goes up with genuine buys instead of empty transfers. You sign one funding transaction. A J Tools worker then fans the SOL out to every wallet and runs the buys for you. {% 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 %} ## When to use this * You want to lift your token's unique-holder count with real buys, not just balance transfers. * Your token is live and tradable on pump.fun's bonding curve, PumpSwap, or Raydium. * 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 just need to send tokens to a list of addresses you already control, use [Multi Sender](/tools/wallets/multi-sender.md) instead. ## 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. Mints with transfer hooks or transfer fees are blocked (these are [Token-2022](/concepts/spl-vs-token2022.md) extensions), and a token with an active freeze authority triggers a warning. * Enough SOL in your wallet to cover the buys, the per-wallet overhead, 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. {% hint style="danger" %} The buy amount per wallet is set by the platform to keep each new holder as cheap as possible. You decide **how many** holders to add, not how much each one spends. This is a high-risk Phantom tool because every fresh wallet is funded from your wallet, so the whole batch is traceable to you on-chain. {% endhint %} ## Step by step {% stepper %} {% step %} ### Configure the run Pick your token with the selector, then set the holder count (1 to 2000 per run). Choose whether each wallet buys the same amount (Equal) or a varied, more organic spread (Varied), set the per-buy slippage, and pick the pacing. A live cost breakdown shows the micro-buy per wallet and the total buys. It also shows the platform fee and an estimated total. {% 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 wallet that was just created, and it is the only way to recover the tokens or any leftover SOL in them 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 locked platform wallet. Approve it once in your wallet. The signed transaction, the plan, and the wallet keys go to the J Tools worker. {% endstep %} {% step %} ### Watch it run The worker broadcasts the funding transaction, spreads SOL from the distributor to every holder wallet, and runs each buy. 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) {% 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 %} ## The options, explained | Field | What it does | | --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Token | The SPL mint every new wallet will buy. Pick it with the built-in selector. It must be tradable; untradable, transfer-hook, and transfer-fee mints are blocked. | | Holder count | How many fresh wallets to create, from 1 to 2000 per run. Default 15. Quick presets add +100, +500, or +1000. | | Buy-amount mode | **Equal** gives every wallet the same buy. **Varied (organic)** jitters the amount around a median for a more natural spread. Default is Varied. | | Slippage | Per-wallet buy slippage. Auto uses a sensible default, or choose 1%, 3%, or 5%. | | Pacing | **Fast** runs several buys at once with tight spacing. **Drip** runs one buy at a time, spread evenly over a window. Default is Fast. | | Drip window | Only used with Drip pacing. How long to stretch the buys over: 1 hour, 6 hours, or 24 hours. Default 6 hours. | {% hint style="info" %} The total buy amount is calculated for you. It is the fixed per-wallet micro-buy multiplied by your holder count, so it grows only with the number of holders you add. See the live cost breakdown and the [Fee schedule](/reference/fee-schedule.md) for the platform fee, which is charged per holder. {% endhint %} ## Supported platforms The worker buys through whichever [route](/concepts/dexes-and-liquidity.md) can fill the order for your token. {% tabs %} {% tab title="pump.fun" %} For a token still on its pump.fun bonding curve, buys go through the curve directly. {% endtab %} {% tab title="PumpSwap" %} Once a token has a PumpSwap pool, buys route through it. {% endtab %} {% tab title="Raydium" %} Tokens listed on Raydium are bought through their Raydium market. {% endtab %} {% endtabs %} ## If something goes wrong * **Token is not tradable.** The pre-flight check could not find a market for the mint, or the mint uses a transfer hook or transfer fee. These are blocked. Make sure the token is live on pump.fun, PumpSwap, or Raydium first. * **Freeze authority warning.** The token still has an active [freeze authority](/concepts/authorities.md), which means the new holders might not be able to sell. Revoke it first with [Make Immutable](/tools/secure/make-immutable.md) or [Revoke Freeze](/tools/secure/revoke-freeze.md) if you control it. * **Not enough SOL.** The balance check ran before you signed and your wallet is short. Top up to cover the buys, the per-wallet overhead, and the platform fee, then try again. * **Start is blocked.** You have not downloaded the wallet backup yet. Save it, then start. * **Some buys failed.** A few wallets can fail under load or thin liquidity. The progress view shows the failed count and logs. The tokens and leftover SOL stay in those wallets, recoverable through your backup file. For the full list, see the [Error codes reference](/reference/error-codes.md). ## FAQ
Are these real holders or fake balances? Each wallet makes a real on-chain buy and keeps the token, so they are genuine buys that raise your unique-holder count. They are not airdrops or empty transfers.
Can anyone tell the wallets are mine? Yes. Every wallet is funded from your wallet through the distributor, so on-chain the trail leads back to your source wallet. Cluster tools like Bubblemaps can still link them. The tool is upfront about this; it boosts the count with real buys but does not hide who is behind them.
Why can I not set how much each wallet buys? The per-wallet buy is fixed by the platform to keep each new holder as cheap as possible. You control the holder count and the spread (Equal or Varied), not the size of each buy.
What happens if I lose the backup file? The backup is the only copy of those wallets' private keys, and it is saved as plain JSON with no password. Lose it and you lose access to any tokens or leftover SOL sitting in the generated wallets. Store it somewhere safe right after the download.
How does one signature fund so many wallets? You sign a single funding transaction that pays the distributor wallet and the platform fee. The worker then spreads SOL from the distributor to every holder wallet and runs the buys. That gets past the old limit of roughly 25 transfers in one transaction, so a single signature can fund any number of holders.
Does J Tools hold my keys? No. The wallets are generated in your browser, you sign the funding transaction yourself, and the backup stays with you. J Tools never asks for or stores your private keys.
## Related tools {% content-ref url="/pages/ABVX2mBQDoCv7DEdVmKp" %} [Multi Sender](/tools/wallets/multi-sender.md) {% endcontent-ref %} {% content-ref url="/pages/IkDuDGRTPYj2wcjtbIre" %} [Holder Snapshot and Analytics](/tools/utilities/token-snapshot.md) {% endcontent-ref %} {% content-ref url="/pages/7CPBHR61Y6akMdkeSBGW" %} [Batch Collector](/tools/wallets/batch-collector.md) {% endcontent-ref %} {% content-ref url="/pages/a7TACAPAW24OFOSbtgNw" %} [Wallet Generator](/tools/wallets/wallet-generator.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/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.