PumpRugdocs

HomeDocumentation › Getting started

Getting started

1. Create an account

Open the launcher and choose Create an account. You need a username, an email address and a password of at least 8 characters. If the server has Google Sign-In configured you can use the Google button instead — an unrecognised Google account signs up, a known one signs in.

The first account created on a fresh server becomes the admin. An admin can list accounts and disable one, and nothing more — there is no route by which an admin can read another user's keys, launches or funds.

2. Fund your wallet

There is nothing to set up. Your account is given its own funding wallet when you sign up — freshly generated on the server, used for nothing else, and empty until you put SOL in it. It is the source of every lamport a launch spends and the destination every sweep returns to.

The launcher shows its deposit address at the top of the Funding wallet card. Copy it, send SOL to it from any exchange or wallet, and press Refresh. That address is public — it can only receive.

Why generated and not pasted. The old flow opened on a box asking for your base58 private key. That teaches exactly the habit every drainer scam depends on — exporting a key out of your real wallet into a web form — and it puts one key in two places at once. A wallet minted here starts empty, does one job, and you can walk away with it whenever you like.
How the key is stored. Encrypted with AES-256-GCM before it reaches the database, using a secret held only in the server's environment. The database alone is not enough to spend your funds. The running process must still decrypt the key to sign transactions, so a PumpRug server remains a sensitive machine — treat it like one, and keep only what a launch needs in this wallet.

Exporting your wallet

The key is yours. Open your profile (your username, top right), find Funding wallet → Export wallet, confirm your account password and the private key is revealed with a one-click copy. Import it into Phantom, Solflare or anything else with "Import private key" and the SOL moves with you.

The reveal is throttled, the password is required every time on accounts that have one, and the key hides itself again after two minutes so it cannot sit on an unattended screen.

Withdrawing your SOL

Money leaves the same way it arrives. In your profile, under Funding wallet → Withdraw SOL, paste a destination address, enter an amount (or tick Empty the wallet), confirm your account password and press Withdraw. You get the transaction signature back as a Solscan link.

Two things it refuses to do. It will not withdraw while a campaign is running — that SOL is already committed to wallets and buys in flight, and pulling it mid-run turns a launch into a half-funded failure; stop the campaign first. And it will not leave the wallet stranded below the rent-exempt minimum: ask for an amount that would leave unusable dust behind and it rounds up and empties the account instead.

Solana transfers are final. There is no reversal and no support desk. Paste the destination address — never retype it — and check it before confirming.

Using a wallet you already own

Still supported, just no longer the default. Under the Funding wallet card, open Use a wallet I already own and paste a base58 private key. It replaces the generated wallet — export that one's key first if it still holds SOL, because this server keeps the only copy of it.

How much SOL do I need?

For one launch, roughly:

dev buy + 0.03 (creation rent & fees) + (buy wallets × per-wallet funding) + 0.05 reserve

A 15-wallet launch at the defaults (0.05 dev buy, 0.02 per wallet) needs about 0.41 SOL. PumpRug checks the balance before it moves anything and refuses with the exact figure if it is short.

3. Build a token queue

The queue is the list of tokens a campaign will launch, in order. Each entry is a name, a symbol, a description and an image.

You do not have to invent five of them to see how it works. Press Load 5 sample tokens under the queue and PumpRug fills it with five ready-made entries, images included. They are ordinary queue rows once added — rename them, replace the images, reorder them, or delete the ones you do not want.

Sample tokens are sample content, not a sandbox. Launching one creates a real token on pump.fun with real SOL. There is no practice mode.

What happens when you press Start

A campaign works through the queue one token at a time, top to bottom. For each token:

  1. Fund — fresh wallets are generated for this token (1 dev + the buyers) and topped up from your funding wallet.
  2. Launch — the token is created on pump.fun and every wallet buys it in the same bundle, so the buys land with the create rather than behind it.
  3. Sell — when your sell trigger fires (profit target, elapsed time, buy volume, or you pressing Sell) every wallet sells its position.
  4. Sweep — whatever is left in those wallets, plus rent reclaimed from closing empty token accounts, is swept back to your funding wallet.
  5. Next — the campaign moves to the next queued token and does it again, until the queue runs out or you press Stop.

So five queued tokens means five launches, back to back, each finishing before the next begins. The settings on the Campaign card are shared by all of them — you set them once, not per token. The first launch takes 90–120 seconds before anything appears, because wallets are funded and the image is pinned to IPFS before the token exists.

4. Run the pre-flight check

Pre-flight proves every external dependency answers before any SOL moves. It spends nothing. It checks that the Solana RPC responds and is not rate-limiting, that your funding wallet exists and holds a balance, that IPFS metadata hosting accepts your credentials, and that pump.fun's transaction builder will build a create transaction. Fix anything red before launching.

5. Your first launch

Start small: 10 wallets, a 0.01 dev buy, 0.013 per buy wallet. Watch the live log. When it reaches bought you hold the token across every wallet and nothing further happens until you sell. Read Launches next.