PepeBotPEPEBOT
online
pepebot // onlinemode: simulationsolana

A PHYSICAL
SOLANA WALLET
POWERED BY ITS
OWN TRADING FEES.

FEES IN.→ASSETS OUT.→HOLDERS.→REPEAT.

$PEPEBOT trading fees flow into a treasury. An automated router splits each cycle between PEPE purchases, buybacks and burns, and rotating asset pairings — then pays holders pro-rata. A rusty green robot on spring legs reacts to every step.

Live chart Source codeThe loop
$PEPEBOT contract address2Su1mp2yxnWqUagnGAbMkF76as8wi6NZs41pPXScpump
unit 01 // pepebotoptics hot
PepeBot: a rusty green and blue robot on spring legs with two glowing red eyes
price
mcap
24h vol
24h
telemetry offline // dexscreenert --:--:--
terminal // stdoutsim
$ _
01 // market feed

LIVE $PEPEBOT TELEMETRY

Every readout below is fetched from DexScreener's public API at load time, plus token supply straight from a Solana RPC node. Nothing on this panel is hardcoded — if a source can't answer, the field reads UNAVAILABLE.

feedpepebot / sol
live
price
market cap
liquidity
24h volume
24h change
pair
fdv
total supply
solana rpc
price in sol
1h
24h buys
24h sells
chartprice history // dexscreener embed
open
linking chart…
Trade on JupiterDexScreener
02 // schematic

THE LOOP

Fees come in. The treasury buys PEPE and rotating assets. Holders receive it. Repeat. Each stage below carries its real implementation status from the repo — nothing is dressed up as finished.

loop machine // cycle diagram signal traveling
cycle
repeat
stage detail04
CORE
in repo

Cycle scheduler, guardrails and event bus. Emits every state change.

payout sequence
SNAPSHOT → EXCLUDE → MIN BALANCE → PRO-RATA → MIN PAYOUT → BATCH → SEND

Rounding and dust carry to the next cycle. No amount, schedule or return is promised.

03 // router + asset bay

MODULES PLUGGED INTO THE CORE

One config file decides where a cycle's budget goes. Allocation is expressed in basis points and must sum to 10000. Statuses are taken from the repo, not from ambition.

busallocation bus
config/allocation.yaml
allocation:
  pepe_bps:   8000
  assets_bps: 2000
guardrails:
  max_sol_per_cycle: 25
  max_slippage_bps:  100
  kill_switch_file:  ./KILL
split
80% pepe20% assets
PEPE REWARDS
pepe_bps 8000
partial

The majority of each cycle budget is quoted SOL → PEPE through an aggregator, then queued for holder distribution.

PEPEBOT BUYBACKS
treasury op
planned

The treasury can route part of a cycle back into $PEPEBOT itself, tightening supply on the open market.

BURNS
treasury op
planned

Bought-back supply can be sent to a burn address. Burn transactions are verifiable onchain when they happen.

ROTATING ASSET PAIRINGS
assets_bps 2000
planned

PepeBot is not married to one asset. The asset bay accepts modules over time — memecoins today, other supported tokenized assets where technically and legally possible. Each module carries its own eligibility gate, and a gated module never spends: its share stays in the treasury.

HOLDER DISTRIBUTIONS
pro-rata
partial

Snapshot of eligible holders, LP/burn/treasury/program accounts excluded, minimum balance and minimum payout floors applied, 50 transfers per batch.

04 // the body

PEPEBOT IS NOT JUST SOFTWARE

The robot is the visual body of the onchain system. It holds no keys and signs nothing — the backend observes the event bus and animates hardware. Pick an event to drive the unit.

unit 01state // PAYOUT
dist.completed
PepeBot hardware unit
Full eyes, green chase, arms wave, one hop on the spring legs.
baysreaction bays // event → emote
hardware notes
  • — ESP32 bridge receives emote frames over a one-way channel.
  • — Status lamp blinks on simulated frames, solid on live ones.
  • — The robot cannot be fooled into looking live.
  • — No private keys ever reach the hardware.
05 // open source

BUILT IN PUBLIC.

Repositories, commits and languages below are read live from the public GitHub API. If GitHub rate-limits the request, this panel says so instead of inventing development activity.

loggit log // ThePepeBot/ThePepeBot
reading
Open GitHub organisation
reposrepositories
langlanguage composition
06 // transparency

VERIFY, DON'T TRUST

Everything that exists onchain is linked to an explorer. Everything that does not exist yet is marked pending instead of being simulated as live.

registryaddresses + routes
live execution off
token mint2Su1mp2yxnWqUagnGAbMkF76as8wi6NZs41pPXScpumpverifiable
market pairnot indexedunavailable
source codegithub.com/ThePepeBot/ThePepeBotpublic
treasury multisignot published yetpending
distribution transactionslive execution not implementednot live
burn addressnot published yetpending
Solscan DexScreener pump.fun
$PEPEBOT contract address2Su1mp2yxnWqUagnGAbMkF76as8wi6NZs41pPXScpump

$PEPEBOT is a memecoin experiment. Nothing here is an offer, investment advice or a promise of returns. A cycle can distribute nothing. Gated asset modules never spend. Read the code before participating.