the forking starts soon: $FORK is live, CA below

Cook your bag.
Eat it with a fork.

Cook Protocol is the strategy kitchen of Robinhood Chain. One recipe file streams whale-sized strategies into small wallets.

chef@robinhood:~/cook

Cooking on-chain is still painful.

Even experienced degens spend 30 to 50 percent of their time fighting infrastructure instead of improving their edge. Cook Protocol keeps the infrastructure in the pot, so the only thing you ever tune is the recipe.

Ladle streaming

Whale strategy.
Shrimp wallet.

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.

119.6ladles per second
0.33 ETHpeak wallet footprint
bit-exactvs whale-resident runs

Second helpings.

Stay at the table and the kitchen notices. A fork that holds through a full service gets served first at the next one, and served more. Leave mid-service and your ladle resets to one.

No forms, no claim button, no snapshot games. The pot counts services, your fork counts as long as it is still at the table.

Service ledger
service one
one ladle
service two
bigger ladle
service three
second helping
fork held through three services served first

One file. Whole meal.

No dashboards, no twelve-step setup, no bridging to a chain you will never visit again. You write cook.yaml, the kitchen cooks it.

# cook.yaml
base: robinhood-chain/4663
task: cook

pot:
  pair: FORK/WETH
  broth: permanent-liquidity

fork:
  of: COOK            # the starter, first attempt
  ticker: FORK        # the main course
  resident: block-one # no switch, live when it lands
  seat: saved         # first attempt holders keep a seat

ingredients:
  conviction: 40%
  patience: 35%
  degeneracy: 25%

cooking:
  heat: auto        # the kitchen reads your wallet
  ladle: streaming   # whale strategy, shrimp wallet
  bites: 4bit        # quarter-sized entries
  helpings: auto    # stay through a service, get served more
>cook --config cook.yamland that is the entire workflow.

Everything in the pot.

Preference losses

Tune on your own trade history with the loss function that matches how you actually behave. JEET is supported but discouraged.

APEFOMOHODLDCAJEET

Auto heat

The kitchen reads your wallet and sets position size itself. It is batch_size auto, but for money.

4bit bites

Quarter-sized entries for small stomachs. Same nutrition, less risk per spoon.

Export your bags

Merge a finished position and export it as WETH, stables, or a heavier bag.

Cooks while you sleep

The pot simmers on-chain. No cloud, no CEX, no SSH into anything.

status: simmering
uptime: since genesis

Honest numbers.

Records are published as written, including failures, assumptions that turned out wrong, and numbers we measured and then threw out.

119.6 l/sladle throughput, laptop wallet
0.33 ETHpeak footprint while streaming
8 ETHstrategy class it can carry
bit-exactresults vs whale-resident runs
run 01laptop wallet, ladle streaming119.6 l/s, 0.33 ETH peakkept
run 02phone wallet, ladle streaming41.2 l/s, screen cracked mid-runkept
run 03assumed gas would not mattergas mattereddiscarded
run 048 ETH whale-resident baselinebit-exact match with run 01kept

The pot token.

$COOK was the starter. $FORK is the main course, and it is on the table. Same pot, same 3/3 reinvested straight back into the broth, same stirrer at 1%. Nobody unplugs the stove.

chef@robinhood:~/token