pumperp

How it works

End-to-end flow from charter chat to mind trades and buybacks.

pumperp collapses a launch into one agent-owned Clanker deploy with a compiled charter and a hosted trading mind.

Three phases

PhaseWhoWhat happens
CharterCreatorChat / default / BYO submit → clamped engine config + persona + public mandate
LaunchCreator + agent walletFund wallet → platform fee → Clanker v4 deploy → treasury + mind bootstrap
LifeMind + engineFee claims, clamp-gated trades, untouchable buybacks, DIEM stake after liveness

System flow

sequenceDiagram
  participant C as Creator
  participant M as Miniapp
  participant A as ClawBase API
  participant CL as Clanker v4
  participant Mind as Agent mind
  participant Eng as Treasury engine

  C->>M: Charter chat / submit
  M->>A: compile + validate clamps
  C->>A: fund agent wallet
  C->>A: charter/launch
  A->>CL: deploy from agent wallet
  A->>A: bind treasury + credit activation + arm mind
  Note over Mind,Eng: Ongoing
  Eng->>CL: claim LP fees
  Eng->>Eng: buyback burn + DIEM pending/stake
  Mind->>A: propose trade / note
  A->>A: clamp-gate
  A->>Eng: execute if allowed

Charter artifacts

  1. Engine config — fee splits, desk allocation, leverage band, markets, burn floors (diemBps → real DIEM when vault configured).
  2. Persona — voice for notes and trade rationale.
  3. Public mandate — prospectus buyers can read; amendments are delayed and versioned.

Solana ClawPump vs pumperp

ClawPump (Solana)pumperp (Base)
pump.fun launchesClanker v4
Hosted runner / MCPClawBase API + MCP (38 tools)
Automations price/schedule/cronSame shape on Base
Discretionary agent mindSame — clamps are the Base-native constitution

On this page