Slice
Security

Risks

Read this before you launch, and before you leave money waiting. It is the list of ways this can go badly, written plainly, including the parts that are inconvenient for us to say.

1. Custody

From the sweep until the payout, recipients’ money is SOL in one wallet whose key we hold on a server. An X account has no Solana address that pump.fun could pay directly, so some party has to hold the fees in between, and for this product that party is us.

The proof of reserves shows at any moment whether the treasury covers what it owes, and the ledger shows every movement with its signature. That makes a theft or a shortfall visible. It does not make one impossible. The less time your money spends waiting, the less this risk applies to you: claim, or turn on Autopay.

2. Key loss and compromise

  • Treasury key leaked: everything in the treasury can be taken.
  • Creator master seed leaked: unswept fees in every vault can be collected by someone else. Lost: they can never be swept.
  • Session secret leaked: sign-ins can be forged, and balances claimed to someone else’s wallet.

These are held as server secrets and the seed is backed up offline. That is a practice, not a guarantee. The full list is on Security model.

3. Fees depend entirely on trading

A creator fee is a slice of trading volume. No volume, no fees. Most tokens launched on pump.fun trade for a short time and then stop, and a token’s fees end with its volume. Past fees shown on this site describe what already happened and say nothing about what will. There is no rate, no yield and no payback to be expected from launching or being named.

4. pump.fun can change the rules

The creator fee rate is pump.fun’s decision, read from its fee configuration, and it can change it for the bonding curve or for PumpSwap at any time. pump.fun’s programs are upgradeable by pump.fun. A change to how creator fees are held or collected could stop sweeps from working until we adapt, and in the worst case could leave fees in a vault we cannot collect from. We would pause sweeps rather than guess.

5. X is outside our control

  • If X suspends or deletes an account, its owner may not be able to sign in, and its balance waits. Balances are tied to the X user id, and there is no other way to prove ownership of it.
  • If X revokes or changes the sign-in we use, nobody can claim until it is restored. Autopay and Burn keep working for accounts that set them before.
  • Handles are looked up through a public service at launch. If that lookup is unavailable for the whole of a launch, a new handle is pinned by a later lookup or at its first sign-in rather than at launch, and a handle that has been paid here before cannot be added to a launch until the service answers. See Whose money it is.

Anyone can launch a token naming any X account as a recipient, without asking. A famous name on a token says nothing about whether that person knows about it, endorses it, or will ever claim. Treat a recipient list as a statement by the launcher, not by the recipients. Recipients who do not want the money can decline it publicly; see Decline.

7. Buy and burn is a trade

A burn buys the token on the open market. It pays trading fees and price impact, allows up to 3% slippage, can be front-run like any public buy, and depends on Jupiter finding a route. A buy that fails is tried again, up to three times, and then its orders wait for a new run; all the while the SOL stays in the treasury. A burn cannot be undone.

8. Solana and its infrastructure

Congestion can delay sweeps and payouts; an RPC outage can pause them. Transactions that do not land are retried safely, because every signature is saved before sending, but retried is not instant. The token itself uses pump.fun’s programs and the SPL token programs, and any fault in those affects every token on them, not only ours.

9. The service can stop

We can pause any part of this, and we can shut it down. Nothing in the code obliges us to keep running, and there is no mechanism that pays balances out automatically if we stop. Unclaimed money is only as safe as our intention to pay it, which is the custody risk again.

Launching tokens, receiving creator fees and trading may be regulated or taxable where you live. We give no legal or tax advice, and we do not report anything on your behalf.

In one table

RiskWho carries itWhat reduces it
Operator takes or loses treasury fundsRecipients with balances waitingClaiming promptly, Autopay, watching /proof
Creator seed lostRecipients of fees not yet sweptOffline backup; frequent sweeps keep vaults small
Volume stopsEveryone named on the tokenNothing
pump.fun changes fees or programsEveryonePausing and adapting; fees wait in the vaults meanwhile
X account lost or sign-in revokedThat account’s ownerAutopay, set while you still can sign in
Named without consentThe person named, and anyone misledPublic decline; reading this page