0.x SDK version a breaking change is a minor bump; the compiler follows semver.
@eco-incorp/sauce 0.99.4
@eco-incorp/sauce 0.99.2 (2026-09-24), 0.99.3 and 0.99.4 (2026-09-25). Requires Node 24 or later and pins compiler 2.3.0. Adds the chain-global intent syntax Base(body, options).reward(...) with token and protocol globals (USDC.approve(Uniswap.UniversalRouter, amount)), .nest(...) for child intents, the compact-argument codec under /compiler, and a Markdown manual with checked examples under docs/. The settle program pin moves to compiler 2.3.0 and 356 bytes; pass the historical { hash, bytes: 362 } pin to validateSettleProgram for older payloads. The SDK’s SVM route helpers are documented as incompatible with the released engine; Solana execution uses the Kitchen client. See the SDK reference.Solana engine 1.2.0
Engine 1.2.0 (program
HB8b1oD5PB2ptkLH6EV56Rr9RHevutEfvG2YdA7an6rK) pins staged code on direct paid execution, following 1.1.0 (2026-09-24), which added direct paid cook entrypoints. Deployed to Solana mainnet; the SDK clients continue to use Kitchen-mediated cooks. See Architecture and deployments.Mainnet rollout: 16 EVM chains and Solana
EVM engine 1.0.1 and Kitchen 1.0.0 deployed on Ethereum, Base, Arbitrum, Optimism, BSC, Polygon, Celo, Ink, Sonic, Plasma, Unichain, World Chain, Monad, Arc, Robinhood Chain and HyperEVM; Solana engine 1.0.1 and Kitchen 1.0.0 on Solana mainnet. Kitchen fees were initialized at about one US dollar in each chain’s native token. Engine 1.0.0 remains deployed on the eight chains that received it on 2026-09-18. See Deployments.
@eco-incorp/sauce-compiler 2.3.0
Fixes silent data loss in EVM
abi.encode of scalar arrays present in compilers 0.3.0 through 2.2.1: an element whose bits 72 to 79 equalled 0x90, 0x92 or 0x94 was mis-encoded without reverting. Only values below 2^80 with those exact bits are affected, and the SVM target is unaffected. Upgrade and recompile EVM programs built with an affected version. The same misread in the scalar fields of a tuple, which covers external call argument lists and multi-value abi.encode, is not fixed by this release and needs a future compiler and engine. Also adds Account.dataLen on the SVM (needs engine 1.0.1), captured scalar results for .catch, and several optimizations; CompileResult now reports isaRevision, entryEncoding and entrySchema. See the compiler API.EVM engine 1.0.1 and Solana engine 1.0.1
EVM engine 1.0.1 (
0x9745fdfaB1be84a0003f0472A842A0b91E5A323c) dispatches from a cursor the handler already holds, reducing engine bytecode and gas; scalar-array behaviour is unchanged. Solana engine 1.0.1 (8Sgwi8N7JykC3K19ReY8aZzYXmWxKcDTedtQ6r1y6iwH) adds the ACCOUNT_DATA_LEN opcode behind Account.dataLen and recovers compute efficiency in hot stack operations. Engine addresses derive per version, so a release deploys at a new address and nothing in place moves.Engines and Kitchens 1.0.0
Both engines and both Kitchens moved from the unstable
0.x policy to the v1 compatibility contract (2026-09-17 tags): the EVM engine commits to its opcode set and semantics, the SVM engine to its wire contract. Engine 1.0.0 and Kitchen 1.0.0 deployed on Base, Optimism, BSC, Celo, Ink, Sonic and Plasma, and Solana engine 1.0.0 (DnR2g6w9gVhqcR68QEpuw7Wm7MuoKxRVEtKZDXGes3Nj) with the Solana Kitchen on Solana mainnet.@eco-incorp/sauce 0.99.1 and compiler 2.2.1
@eco-incorp/sauce 0.99.0 and 0.99.1 published, succeeding the @eco-incorp/sauce-sdk package name (last published as 0.13.1 on 2026-09-15). Compiler 2.2.1 published the same day.@eco-incorp/sauce-compiler 1.0.0 to 2.2.0
First stable compiler release 1.0.0 on 2026-09-11; 2.0.0 and 2.1.0 on 2026-09-15; 2.2.0 on 2026-09-16. Earlier
0.x versions: 0.3.0 (2026-08-18), 0.4.0 and 0.4.1 (2026-08-20), 0.5.0 (2026-08-31), 0.6.0 (2026-09-02), 0.7.0 (2026-09-09).