Soup is the strategy kitchen of Robinhood Chain. One recipe file streams whale-sized strategies into small wallets.
Even experienced degens spend 30 to 50 percent of their time fighting infrastructure instead of improving their edge. Soup keeps the infrastructure in the pot, so the only thing you ever tune is the recipe.
The full strategy stays resident in the pot. Your wallet receives it one ladle at a time, executes the bite, and hands the ladle back. Nothing about the trade changes except who can afford to run it.
No dashboards, no twelve-step setup, no bridging to a chain you will never visit again. You write soup.yaml, Soup cooks it.
# soup.yaml base: robinhood-chain/4663 task: cook pot: pair: SOUP/WETH broth: permanent-liquidity ingredients: conviction: 40% patience: 35% degeneracy: 25% cooking: heat: auto # soup reads your wallet ladle: streaming # whale strategy, shrimp wallet bites: 4bit # quarter-sized entries
Tune on your own trade history with the loss function that matches how you actually behave. JEET is supported but discouraged.
Soup reads your wallet and sets position size itself. It is batch_size auto, but for money.
Quarter-sized entries for small stomachs. Same nutrition, less risk per spoon.
Merge a finished position and export it as WETH, stables, or a heavier bag.
The pot simmers on-chain. No cloud, no CEX, no SSH into anything.
Records are published as written, including failures, assumptions that turned out wrong, and numbers we measured and then threw out.
$SOUP is the broth. Liquidity goes into the pot at genesis and never leaves it. Nobody unplugs the stove.