How pumpr works
pumpr is a pump.fun launchpad with Proof-of-Belief staking. Every token launched streams creator fees back to its holders — forever.
#Overview
pumpr wraps pump.fun's bonding-curve launchpad with a send-to-stake fee-sharing layer. When someone creates a token on pumpr, pumpr takes custody of the token's creator wallet so that every SOL of creator fee earned on pump.fun can be routed back to the people holding and staking the token, proportional to how long they commit.
#Launching a token
- Fill in name, ticker, image, and optional socials.
- pumpr generates a fresh Solana wallet per launch — the
dev wallet— and shows you its address. You never see its private key; pumpr custodies it. - You send 0.05 SOL to the dev wallet.
- pumpr detects the deposit, shows you a
LAUNCH NOWbutton, and on click signs the pump.fun create-token transaction from the dev wallet. The dev wallet becomes the official creator, so pump.fun creator fees flow to it. - pumpr then generates three per-token staking wallets (1-day, 3-day, 7-day) and creates their SPL token accounts so users can send directly.
#Cost breakdown
| Item | Cost | Paid by |
|---|---|---|
| pump.fun create-token tx | ~0.02 SOL | dev wallet |
| 3 × staking ATA creation (rent) | ~0.006 SOL | dev wallet |
| Escrow SOL reserve for unlock fees | ~0.003 SOL | dev wallet |
| Priority + tx fees | ~0.001 SOL | dev wallet |
| Total | ~0.03 SOL | leaves ~0.02 SOL buffer |
#Send to stake
There is no connect wallet step for staking. To stake, send the token to one of three staking addresses shown on the token page — from any wallet (Phantom, Solflare, Ledger, or even an exchange withdrawal).
pumpr indexes the incoming transfer, credits your sender address as a staker, and starts a timer matching the tier you sent to.
#Lock tiers
| Tier | Lock | Multiplier | Purpose |
|---|---|---|---|
| 1-day | 24h | 1.00× | baseline |
| 3-day | 72h | 1.75× | boosted |
| 7-day | 168h | 3.00× | max belief |
Multipliers weight your share of rewards. Longer stake = bigger slice of the fee pool each hour you're active.
#Earning rewards
Every hour pumpr runs a distribution job for each token:
- Calls
collectCreatorFeevia pumpportal so any accumulated pump.fun fees arrive in the dev wallet. - Computes each active deposit's weight:
amount × tier_mult × fraction_of_hour_active - Splits available SOL: 90% to stakers pro-rata, 10% to the protocol treasury.
- Sends SOL directly to each staker's sender address. No claiming, no signing, no extra fees on your side.
#Auto-unlock
When your lock period elapses, a worker sweeps eligible deposits and transfers the tokens back to the original sender address. There's no button to press — it happens within a minute of the unlock time.
During the lock your tokens are held by the staking wallet and cannot be moved by you. During the lock you continue to earn rewards every hour at your tier multiplier.
#Custody model
pumpr custodies two kinds of keys per launch:
- The dev wallet — needed to sign pump.fun create-token and later
collectCreatorFeecalls on your behalf. - The 3 staking wallets — needed to transfer tokens back to senders when their locks expire.
Keys are encrypted at rest (AES-GCM) and only ever decrypted in-memory inside the signing service. No user assets other than staked tokens (and only during their own lock) are touched.
#Why send-to-stake
Most Solana dapps require a wallet extension and an on-chain signature for every action. pumpr stakes by transfer instead, so:
- No wallet popups, no "connect" prompt.
- Works from any wallet (including CEX withdrawals).
- Rewards arrive back at the same wallet you sent from — same operational flow as a Solana transfer.
The cost of this UX is that pumpr holds the staking wallets temporarily — a model closer to a custodial staking pool than a fully trustless escrow. We're explicit about this.
#Known risks
- Custodial staking wallets. If pumpr is compromised, staked tokens are at risk.
- pump.fun dependency. pumpr launches and fees all depend on pump.fun being operational and maintaining the current creator-fee model.
- RPC dependency. Holders + bonding curve data require a reliable Solana RPC. Public endpoints rate-limit aggressively.
