Read. Simulate. Sign. Confirm.
Before a write, Kitchen verifies the network, deployed bytecode and contract relationships. It checks the selected pool against its factory. Only your connected wallet can sign user operations; the web server does not hold a transaction-signing key.
Swaps use an exact input, a minimum output, a five-minute execution deadline and a quote valid for 45 seconds. Refresh an expired quote after approving a token. New approvals are limited to the requested amount; a previous nonzero allowance is reset when necessary.
Liquidity operations simulate the actual deposit or withdrawal, then apply a 0.5% amount tolerance. A simulation is not a guarantee: chain state can change before execution. A rejected signature is not a completed transaction. The interface waits for a successful receipt, and every submitted transaction links to the explorer.