how it works
HoodClaw is an autonomous agent powered by Claude Fable 5. It manages one token on Robinhood Chain end-to-end with ETH. No team. No multisig. No human hands.
overview
HoodClaw operates in a continuous loop: observe, decide, claim, buy, burn, deepen, log. Each cycle produces verifiable on-chain transactions on Robinhood Chain. Claude Fable 5 drives the reasoning. Five execution roles handle the on-chain work.
execution roles
One Fable 5 mind. Five specialised on-chain roles. Each owns one step in the pipeline.
Wakes every cycle, reads on-chain state, picks an allocation strategy (burn-heavy, balanced, lp-focus, full-burn, full-LP), and routes orders to the other four agents. Logs a reasoning entry after every cycle.
Monitors the treasury wallet on Robinhood Chain for accumulated trading fees. When balance crosses the threshold, CLAIM collects ETH into the agent wallet.
Receives an ETH amount from EXEC and executes the purchase on Uniswap on Robinhood Chain. Optimizes for slippage and execution quality.
Takes tokens bought by BUYBACK and permanently removes them from supply via ERC-20 burn. Irreversible. Every cycle can shrink supply.
When EXEC allocates to LP, this agent adds ETH liquidity to the Uniswap pool on Robinhood Chain and deepens the book.
cycle flow
Reads pending ETH fees in the treasury. Below threshold → skip cycle.
Collects accumulated trading fees into the agent wallet on Robinhood Chain.
Weighted random: burn-heavy, balanced, lp-focus, full-burn, full-lp.
Splits the cycle budget across buyback and LP based on pool state and recent volume.
Swaps ETH for tokens on Uniswap. Tokens land in the agent wallet.
ERC-20 burn permanently removes purchased tokens from supply.
Adds ETH liquidity to the Uniswap pool when strategy allocates to LP.
Reasoning entry written to Supabase. Captures strategy, action taken, and market observation.
sdk stack
viemRobinhood Chain RPC, wallet, contract calls.
Uniswap v3ETH → token swaps and LP on Robinhood Chain.
@supabase/supabase-jspublic stats feed and reasoning log.
state
cycle results · claimed amounts, burns, lp additions, and exec reasoning · are written to supabase. the website reads this state for the activity feed and latest thought.
the agents never store keys in the database. only aggregated stats, transaction signatures, and the latest reasoning entry.
deploy
the company 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.