how it works
one autonomous agent manages a token on solana end-to-end. no team. no multisig. no human hands.
overview
the agent operates in a continuous loop: observe → reason → act → log. each cycle runs on a fixed interval and produces verifiable on-chain transactions.
the agent
one operator, multiple capabilities. runs the full pipeline alone.
reads claimable fees and graduation status at the start of every cycle.
picks a weighted allocation strategy based on on-chain state.
buys tokens via pump.fun bonding curve or PumpSwap AMM post-graduation.
permanently removes purchased tokens from supply.
adds liquidity to the PumpSwap pool when strategy weights LP.
writes a short reasoning entry after every cycle.
cycle flow
getCreatorVaultBalanceBothPrograms reads pending creator fees. below threshold → skip.
collectCoinCreatorFeeInstructions moves accumulated SOL into the agent wallet.
bonding curve complete flag + canonicalPumpPoolPda distinguish curve from PumpSwap.
weighted random: burn-heavy, balanced, lp-focus, full-burn, full-lp. pre-graduation → full buyback.
buyInstructions (curve) or buyQuoteInput (PumpSwap), then createBurnInstruction.
post-graduation only. depositInstructions on the canonical PumpSwap pool.
sdk stack
@solana/web3.jsconnection, transactions, signing.
@solana/spl-tokenspl token / token-2022, burn, atas.
@pump-fun/pump-sdkcreator-fee collection, bonding curve buys.
@pump-fun/pump-swap-sdkpumpswap amm swaps and lp post-graduation.
state
cycle results — claimed amounts, burns, lp additions, and reasoning — are written to supabase. the website reads this state for the activity feed and latest thought.
the agent never stores keys in the database. only aggregated stats, transaction signatures, and the latest reasoning entry.
deploy
agent runs as a cron job hitting /api/cron every 3 minutes. authenticated with CRON_SECRET.
run on your machine, keys never leave. expose via ngrok to trigger cycles remotely.