Skip to main content
Helpers for the EVM engine contracts: viem ABIs and ready-to-use handles with calldata encoders. cook is owner-only and names the engine per call.
This page covers sdk/dist/evm/engine.d.ts.
Generated from the type declarations shipped in @eco-incorp/sauce 0.99.4. Each entry shows the package authors’ JSDoc and declaration for this SDK version. For runtime compatibility and deployed addresses, see architecture and deployments.

v12PotAbi

Variable · sdk/dist/evm/engine.d.ts V12Pot - cook() is onlyOwner. The engine is named per cook. A Pot holds no engine: cook(address engine, bytes program) takes the interpreter as an argument, and inFlightEngine() reports the engine of the cook currently executing - it is address(0) outside one. The SVM kitchen takes an engine_program account per call for the same reason: which interpreter runs is the caller’s choice at call time. A cook runs exactly ONE program.

v12KitchenAbi

Variable · sdk/dist/evm/engine.d.ts V12Kitchen - CREATE2 Pot factory. deployPot bakes owner into the Pot’s CREATE2 address.

v12Pot

Variable · sdk/dist/evm/engine.d.ts Ready-to-use V12Pot handle: the viem ABI plus calldata encoders for route/batch legs.

v12Kitchen

Variable · sdk/dist/evm/engine.d.ts Ready-to-use V12Kitchen handle: the viem ABI plus calldata encoders.