The Kitchen Manual

Everything you need to run whale-sized strategies from a small wallet. Short on ceremony, long on broth.

Quickstart

The whole workflow is one file and one command. Write a recipe, hand it to the kitchen, and go do something else with your evening.

> cook init
wrote cook.yaml with sane defaults ok
> cook --config cook.yaml
chain: robinhood 4663 connected
ladle streaming: enabled
position cooked. bon appetit.

No dashboards, no bridges, no SSH into anything. If a step needs a decision, the kitchen makes the boring one for you and records that it did.

cook.yaml reference

One recipe describes one strategy. Every key has a default, so the smallest valid recipe is the empty one.

baseThe chain the pot lives on. robinhood-chain/4663 is the only supported value, on purpose.
taskWhat to do with the recipe. cook runs it. There is no uncook.
pot.pairThe pair your strategy trades. Defaults to FORK/WETH.
pot.brothpermanent-liquidity. The broth is the locked pool. It does not drain and it does not leave.
ingredientsYour allocation split, in percent. Conviction, patience, degeneracy. It must add up to one whole meal.
cooking.heatauto reads your wallet and sizes positions itself. Manual heat exists for people who like burning things.
cooking.ladlestreaming runs whale-class strategies through a small wallet, one ladle at a time.
cooking.bites4bit quarters every entry. Same nutrition, less risk per spoon.

Ladle streaming

The trick that makes the kitchen work. 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.

8 ETH class

The size of strategy the pot can carry on your behalf.

0.33 ETH peak

The most your wallet ever holds mid-stream on a laptop run.

119.6 ladles per second

Measured throughput on a laptop wallet. Phones run slower and crack their screens.

Bit exact

The streamed run matches the whale-resident run result for result.

The pot & fees

Liquidity goes into the pot at genesis and never leaves it. The tax is 3/3, and every point of it locks in the pot and gets cooked straight back into the broth, which is $FORK. No wallet collects. No one skims. The soup thickens with every trade.

The dev keeps one percent and stirs. Ownership is renounced, so nobody owns the stove, nobody can pause the burner, and nobody can unplug anything. The stove has no knobs by design.

Honest records

Runs are published as written, including failures, assumptions that turned out wrong, and numbers we measured and then threw out. If run three says gas would not matter and gas mattered, run three stays on the card, crossed out, where everyone can see it.

run 01  laptop wallet, ladle streaming   119.6 l/s, 0.33 ETH peak  kept
run 02  phone wallet, ladle streaming    41.2 l/s, screen cracked   kept
run 03  assumed gas would not matter     gas mattered               discarded
run 04  whale-resident baseline          bit-exact match with run 01 kept

FAQ

Can I withdraw the broth?

No. The pot has no drain and the locker has no withdraw function. That is the whole point of a pot.

Who controls the kitchen?

Nobody. Ownership is renounced. The dev holds one percent and a spoon, and the spoon does not come with admin keys.

What happens to fees?

They lock in the pot and get cooked back into $FORK. Every trade feeds the broth it swims in.

Why a kitchen?

Because the tech underneath, layer streaming, was built to run huge models on tiny machines. We point the same idea at wallets and renamed the layers ladles. The recipe metaphor followed us home.