Autonomous meme-coin execution.
Your rules. No emotions.
AutoBlocks is a self-hosted agent built on Hermes Agent, wired into GMGN’s on-chain API. It snipes new pools, mirrors tracked wallets and runs take-profit / stop-loss automation on Solana, BSC and Base — unattended, inside an isolated VM, under hard limits it cannot cross.
// open personal build · self-hosted · not a hosted service, not a fund
[01] // the_problem
Manual is a losing race.
Meme-coin markets are adversarial, automated and awake 24/7. A human with a swap page is none of those things.
ERR_TOO_SLOW
Blocks don’t wait
By the time you’ve found the pool, checked the contract and clicked confirm, the bots that matter are already in — and often already out.
ERR_EMOTIONAL
You are the exploit
FOMO buys the top. Panic sells the bottom. A rule you hold in your head is a suggestion; a rule in code is a policy.
ERR_OFFLINE
Markets don’t sleep
Three chains, every timezone, no weekends. The window that matters will open while you’re asleep, at work, or looking at the other chain.
[02] // execution_loop
Four stages. No discretion.
The agent runs one loop, forever. Nothing happens outside it, and no stage improvises.
01
Define rules
Entry filters, position size, slippage, TP/SL, chain scope — declared in config, versioned like code.
rules.yaml02
Watch signals
The agent streams GMGN on-chain data: new pools, smart-money moves, holder spread, rug indicators.
gmgn://stream03
Execute in limits
A matching rule fires the swap — only inside hard caps on size, slippage and open positions.
tx: confirmed04
Log + report
Every decision, fill and rejection is written to an audit trail and reported back to you.
audit.log[03] // capabilities
Built like infrastructure,
not like a casino.
Every capability exists to make behavior predictable — before, during and after a trade.
Rule-based execution
Deterministic triggers. The agent never makes discretionary “AI decisions” with funds — it executes the strategy you wrote, exactly.
VM / sandbox isolation
Runs unattended in a throwaway VM or VPS with nothing else on it. Your daily machine and main keys stay out of the loop.
Hard position limits
Max per-trade size, max concurrent positions, daily spend ceiling — enforced in the execution path, before anything is signed.
Dedicated hot wallet
One purpose-made wallet with a deliberately small balance. Main funds are never connected — by architecture, not by promise.
Smart-money + rug filters
GMGN signal feeds screen every candidate in real time: wallet reputation, holder concentration, LP status, honeypot checks.
Multi-chain
One rule set across Solana, BSC and Base. Same limits, same filters, same audit log — whichever chain the signal comes from.
[04] // security_&_risk
Containment by design.
Risk by nature.
Read this section as written. It is the part of the page that is not marketing.
[+]what the design contains
- Isolated execution. The agent lives in its own VM/VPS with a minimal surface — no browser sessions, no personal data, nothing else on the box.
- Dedicated low-balance wallet. Worst case is capped at what you deliberately funded. Your main stack is never reachable.
- No custody, no pooling. Self-hosted means your keys, your infrastructure. Nothing is handed to anyone to “manage.”
- Limits before signatures. Position caps and spend ceilings are checked in code before any transaction is signed — not in a dashboard setting.
[!]what remains true anyway
- On-chain trades are irreversible. A confirmed transaction cannot be cancelled, disputed or refunded. Ever.
- Filters reduce noise, not risk. A token can pass every check and still go to zero minutes later.
- This is experimental software. Bugs, RPC outages and chain congestion are real failure modes. Expect them.
- Assume the hot wallet can go to zero. Fund it only with an amount that makes that assumption acceptable.
You’ll find no APY figures, projected returns or profit curves on this page. The agent enforces rules; it does not promise outcomes.
[05] // stack
Boring pieces, wired carefully.
No proprietary magic — an open agent framework, a data/execution API and two chain runtimes.