Skip to content

How PumpRings works

PumpRings gives a Pump.fun coin its own computer. The coin's creator fees pay for that computer and for moving its money privately through Helius Privacy Rings. Every job the computer runs leaves a signed receipt.

Network
Solana mainnet-beta via public Solana RPC
Compute account
6fGH7uttw5ZKEwaWEMXYuTvEAPmoiDgaTsWRxmWvty7L
Receipt key
204a86ccd6bec52e625e97ae810cb4c496f9012e9b6c17431a335f18060b9987

The cycle

  1. Connect a Solana wallet and sign one message to prove it is yours.
  2. PumpRings reads the Pump program for bonding curves that name your wallet as creator, or you paste a mint and PumpRings checks it on chain.
  3. Create a VM for one of those tokens and choose what it runs.
  4. Claim your creator fees and send part of them to the VM's compute account, in one transaction you sign.
  5. When the transaction is finalized, PumpRings reads it back from chain and credits the VM. Not before.
  6. Run the VM. A runner on a separate machine executes it in a sandbox and reports measured CPU and memory every few seconds.
  7. Each report is charged against the VM's budget. When the budget runs out, the job freezes and the VM pauses.
  8. When the job ends, PumpRings signs a receipt with the code hash, resources, cost and output hash.

Creator fees

Pump.fun pays creator fees per creator wallet, not per token: all tokens a wallet created share one vault on the bonding-curve program, plus one on PumpSwap once a token graduates. PumpRings reads both through the official Pump SDK, shows the exact claimable amount and the slot it was read at, and builds the claim with the SDK's own instructions. PumpRings never claims or moves fees on its own. If you choose an allocation, the transfer to compute goes in the same transaction as the claim, because both are ordinary instructions you sign together.

What is private

PumpRings uses Helius Privacy Rings, a shielded pool on Solana. In the default ring:

  • Encrypted: the amounts, asset types and memos of transfers inside the ring, and your balance, which only your viewing key can read.
  • Public: every wallet address. A deposit reveals its source, asset and amount. A withdrawal reveals its destination, asset and amount.
  • Public by design: Pump.fun trades, token launches, fee claims and fee-split payouts. A public payout followed by a private deposit can be linked at the deposit, which is why PumpRings batches and rounds deposits.

Your viewing keys are derived in your browser from a wallet signature and never reach PumpRings's servers. PumpRings holds keys for one thing only: each VM's compute inbox, the account that receives private payments for that VM's compute.

Around the ring, PumpRings adds checks you see before signing a deposit or withdrawal: common round sizes, a warning when an amount is within 1% of an earlier move on the other side, when moves are close together in time, or when the same wallet appears on both sides, and a suggestion to withdraw to a fresh wallet. Your share of a coin's fee split can be paid to any wallet, including one registered in the ring. These make tracing harder, not impossible. Trades on Pump.fun stay public.

Run the agent yourself (MCP)

PumpRings serves its agent over the Model Context Protocol at https://pumprings.com/api/mcp (Streamable HTTP). Tools: coin_report, coin_holders, coin_activity, network_health. They are read-only, rate-limited to 30 calls a minute, and every result is signed with the receipt key.

Compute and metering

Prices come from one table, cpu-2026-11-v1, and every receipt names the table it was billed under.

CPU-second used400 lamports
GiB-second of memory reserved60 lamports
Wall-clock second15 lamports
Minimum per job2,000 lamports (0.000002 SOL)

Counters come from the job's own control group on the runner: CPU nanoseconds used, peak memory, and wall time while not frozen. The ledger is double-entry; a credit references a finalized transaction signature, and replaying a signature credits nothing.

Isolation

No user code runs on the machine that serves this site or the API. Each job runs on a separate runner as a transient systemd unit with its own throwaway user, a read-only system, a private /tmp and no devices, under CPU, memory, process-count and wall-time limits. By default it has no network at all. With an allow list, the job can reach only the addresses those hosts resolve to, enforced by the kernel's cgroup IP filter. Secrets are encrypted at rest and handed to the job only as environment variables at start. No wallet key exists on the runner.

Permissions

Each VM has a policy: maximum spend per day, maximum cost per job, run-time and resource caps, network hosts, allowed programs, and whether it may request trades or launches at all. A VM can only request a transaction. The request appears in your console as a decoded preview; nothing happens unless your wallet signs it. The emergency stop halts every job on every VM you own and rejects every waiting request.

Receipts

A receipt is canonical JSON signed with Ed25519. It contains the VM, token mint, job, code hash, runtime, start and finish times, measured resources, cost, status, exit code, output hash, the policy hash that authorized it and the ledger references that paid for it. The explorer checks signatures in your browser. Anyone can check a receipt against the published key.

PumpRings is independently built on Solana. It is not affiliated with Pump.fun, Helius, RingsSOL or Hush.

Connect a Solana wallet

No Solana wallet was found in this browser. Install a wallet such as Phantom, Solflare or Backpack, then reload this page.

You will sign one message to prove the wallet is yours; it only proves ownership. Every transaction after that is shown to you, decoded, before your wallet asks you to sign it.