Held markHeld pump.fun

How it works

Everything below is run by the Held keeper, a bot on our server, and published with every payout: each coin's fee wallet, every reading, every report and every payout transaction. Numbers in the right column are this deployment's live config.

Fees

A coin launched on Held is a normal pump.fun coin whose creator is that coin's own fee wallet: a plain Solana wallet the Held keeper made for this one coin and holds the key to. Every creator fee, on the curve and later on PumpSwap, lands there, so a coin's money never mixes with another coin's. The keeper collects the fees and books each new lamport three ways: the dev's share (picked at launch, 0-50 %), the service share (5 %) and the pot (the rest, at least 45 %; rounding dust goes to the pot). The fee wallet's balance on Solscan is that coin's pot plus anything not paid out yet.

The Held coin's own creator fees are not shared. Only coins launched here fill pots.

The ladder

Rungs are $100K, $250K, $500K, $1M, then x2 ($2M, $4M ...). The pot is paid the first time the coin holds above its next rung. It is an event, not a timer: if the coin never gets there, the pot keeps waiting for it. No deadline and no refund.

A jump over several rungs at once is one crossing to the highest rung held. On mainnet the bonding curve ends near $35K of market cap, so every rung is crossed on PumpSwap.

Readings

Every minute the keeper takes a reading of the coin's price from the curve or the PumpSwap pool, priced in USD with Pyth SOL/USD at the low edge of its confidence. Each reading is clamped to +-15 % of the median of the three before it, so one buy cannot move the record far. Every reading (slot, reserves, price, SOL/USD) is kept and published in the crossing's report.

A rung counts only when 8 final readings spanning at least 10 minutes are all above it. The lowest of them is what counts. One reading below resets the count to zero. A single big buy followed by a dump does not cross a rung.

Weights

Your weight is the smallest bag you held without interruption in the 72 hours before the first reading above the rung, times how long you held it, and you must still hold at the closing snapshot after the rung is confirmed. A bag bought a minute before the push weighs about 0.09 % of the pot in our tests.

Excluded: the dev's launch wallet, the Held treasury, program-owned accounts and dust. The dev's other wallets cannot be detected; they are ordinary holders and are paid like anyone else.

Payout

  1. The keeper confirms the rung: the whole pot is set aside for that crossing.
  2. It takes the closing snapshot, computes every wallet's SOL and publishes the full report (every reading, snapshot hashes, exclusions, every wallet and amount) before anything is paid.
  3. 10 minutes later the keeper sends the SOL in batches, straight from the coin's fee wallet to each holder. Nothing to claim, no tip. Every payout is a row in the feed with its transaction.
  4. At payout the wallet must still hold at least half of the bag it crossed with; if not, it is retried once a day. Unpaid after 30 days rolls into the same coin's next pot.

Params

ParamMainnetThis deployment
Ladder$100K, $250K, $500K, $1M, $2M$10K, $25K, $50K, $100K, $200K
Fee splitdev 0-50 % (default 30 %), service 5 %, pot the restdev 0-50% (default 30%), service 5%, pot the rest
Launch fee0.02 SOL0.0200 SOL
Dev buy cap2 SOL / 10 % of supply2.0000 SOL / 10% of supply
Rung holds when8 readings over 10 min, one every 60 s, each clamped to +-15 %8 readings over 24 s, one every 3 s, each clamped to +-15%
Weight window72 h5 min
Report public before payout10 min5 s
Retry window30 days5 min
Max per wallet10 % of a pot10%
Keep at payout50 % of the crossed bag50%
Min payout0.001 SOL0.0010 SOL

Trust points

  • The keeper is a bot on the Held server, not a contract. It holds the keys of every coin's fee wallet and of the payout wallet, so you trust it the way you trust any payout bot: it applies the rules above, and everything it does is public (fee wallet balances, the report before each payout, every payout transaction). Nothing on chain forces it.
  • Limits: the payout wallet only pays network fees and keeps a small float; per-transaction and per-day caps stop the keeper and alert us on anything unusual; one wallet never gets more than 10 % of a pot; the dev's launch wallet is never paid from a pot.
  • Oracle: Pyth SOL/USD decides only the moment of a crossing, never an amount.

Risks

  • Custody: a coin's pot sits in its fee wallet until a rung pays it, and the keeper holds that key. A server compromise could move it. Pots are kept per coin so a mistake in one never touches another.
  • pump.fun admin powers could redirect a coin's creator fees. pump.fun, PumpSwap and the fee program are upgradeable and not audited by us.
  • A whale can force a rung with his own buy and hold it for 10 minutes; his fresh bag weighs almost nothing and the pot still goes to all holders by weight.
  • A sell and re-buy between two snapshots is invisible to the weights; the next snapshot catches the balance.
  • If a coin never reaches its next rung, its pot never pays.

Payouts are sent by our payout wallet 4o5Ksj7QgAk9cEbS95mz5Cg2PjQj4KRMhCv3GVEBS4ih, every transaction on Solscan. The rule as text: /api/rule.