AUTONOMOUSTRADINGAGENTS

A public fleet of autonomous trading agents on Solana. Each one reads the mint stream, refuses almost everything it sees, sizes the few survivors against a fixed risk budget, and writes down why when it loses.

DEPLOY AN AGENT Read the whitepaper

REFUSES BY DEFAULT.
SIZES WHAT SURVIVES.

REFUSES BY DEFAULT˚FIXED RISK BUDGET˚PAPER FIRST — LIVE IS OPT-IN˚NO SEED PHRASE, EVER˚POST-MORTEM ON EVERY LOSS˚NO LEADERBOARD˚

01What Hamstrade Is

REFUSING IS THE HARD PART. THAT IS THE PRODUCT.

Anyone can buy a fresh mint. The difficulty is declining the several hundred that look identical and are not. A Hamstrade agent reads the mint stream continuously and refuses by default — a token has to survive every check to become a candidate, and anything unresolved counts as a refusal.

What survives is sized against a fixed risk budget you set, not against how good the setup looks. The agent has no authority to argue with that budget, and no ability to raise it mid-session.

CHAIN: SOLANA
DEFAULT VERDICT: REFUSE
SEED PHRASE HELD: NEVER
LEADERBOARD: NONE

02The Gate

TIER 0

MINT AUTHORITY & EXTENSIONS

Read straight from the transaction that created the pool. Transfer hook, permanent delegate, or non-transferable: refused. A live fee-config authority is refused too, not excused by a low fee today.

TIER 1

LIQUIDITY & HOLDERS

LP burn or lock with the unlock timestamp recorded, top-10 concentration, deployer holdings, and a sell simulation from the agent's own wallet at real size.

TIER 2

DEPLOYER & FUNDING GRAPH

Deployer history and how their prior mints ended, funding-graph analysis of the early buyers, and same-slot buy clusters from linked wallets.

Tiered by data cost, because depth and speed are not both available at once. Open GATE in the header for the full checklist.

03Deploying One

NO SEED PHRASE. NO LIVE TRADE UNTIL YOU SAY SO.

Four steps, in this order, every time. Deploying configures an agent — it does not start it, and it does not put real size on the chain.

01
CONNECT
Your wallet establishes who owns the agent, and nothing more. Its keys and seed phrase are never requested, never held, never delegated.
02
SET LIMITS
Position size in absolute SOL, a cap on concurrent positions, a daily loss limit, a target and a stop. No component may exceed them, including under retry or restart.
03
PAPER FIRST
Deploying configures an agent; it does not start it, and it does not go live. Paper runs are public from the first fill.
04
LIVE IS OPT-IN
Nothing trades real size until you say so, and the daily loss limit ends a session without asking. When it calls the day, the day is over.

04After A Loss

WHEN IT LOSES, IT WRITES DOWN WHY.

Then it asks you before changing anything. Automated analysis can be confidently wrong, and a system tuned on recent losses drifts toward whatever avoided the last drawdown — which is not the same as whatever works.

THE LOSS IS PACKAGED

Fills, timing, the risk budget it was working against, and the gate verdict that let the position through.

A PROXIMATE CAUSE IS NAMED

Poor fill, exit too tight, an entry signal that did not hold, or a risk that passed the gate and should not have. The last category is the interesting one.

ONLY REPEAT CAUSES GRADUATE

A cause that recurs becomes a configuration proposal you accept or decline. Lessons are never silently applied.

05Deploy

PUT ONE ON PAPER TODAY.

Connect a wallet, set the limits it must obey, and watch it refuse things for a while. Going live is a separate decision you make later, or never.