@eco-incorp/sauce 0.99.3 → 0.99.4

package/README.md

@@ -8,8 +8,8 @@ tokens, and builds the calls that execute your program.
 npm install @eco-incorp/sauce
 ```
 
-[Documentation](https://unpkg.com/@eco-incorp/sauce@0.99.3/docs/README.md) · [Quick start](https://unpkg.com/@eco-incorp/sauce@0.99.3/docs/guides/quick-start.md) ·
-[Examples](https://unpkg.com/@eco-incorp/sauce@0.99.3/docs/examples/README.md) · [API reference](https://unpkg.com/@eco-incorp/sauce@0.99.3/docs/api/README.md)
+[Documentation](https://unpkg.com/@eco-incorp/sauce@0.99.4/docs/README.md) · [Quick start](https://unpkg.com/@eco-incorp/sauce@0.99.4/docs/guides/quick-start.md) ·
+[Examples](https://unpkg.com/@eco-incorp/sauce@0.99.4/docs/examples/README.md) · [API reference](https://unpkg.com/@eco-incorp/sauce@0.99.4/docs/api/README.md)
 
 Use Node.js **24 or newer**. The links open the Markdown manual and examples included in this package version. After installation, you can also open `node_modules/@eco-incorp/sauce/docs/README.md` locally.
 
@@ -48,14 +48,14 @@ const built = Base(() => {
 console.log(built.hash().intentHash);
 ```
 
-The [quick start](https://unpkg.com/@eco-incorp/sauce@0.99.3/docs/guides/quick-start.md) explains the setup, and the [examples](https://unpkg.com/@eco-incorp/sauce@0.99.3/docs/examples/README.md) are checked
+The [quick start](https://unpkg.com/@eco-incorp/sauce@0.99.4/docs/guides/quick-start.md) explains the setup, and the [examples](https://unpkg.com/@eco-incorp/sauce@0.99.4/docs/examples/README.md) are checked
 against the SDK. The callback is compiled as source. Token and protocol names resolve on Base;
 values from surrounding JavaScript must be supplied through compile-time `defines`.
 
 Use `USDC.transfer(...)`, `USDC.balanceOf(...)`, `Token(address).approve(...)`, and linked protocol
 methods in the same program. `Uniswap.UniversalRouter` is the family alias for
 `UniswapV4.UniversalRouter`; available contracts and methods come from the
-[accessor registry](https://unpkg.com/@eco-incorp/sauce@0.99.3/docs/api/coverage.md). The compiler checks chain availability and ABI fidelity.
+[accessor registry](https://unpkg.com/@eco-incorp/sauce@0.99.4/docs/api/coverage.md). The compiler checks chain availability and ABI fidelity.
 
 ## From a program to an intent
 
@@ -66,31 +66,31 @@ submits those requests. Direct Portal execution requires an Executor-owned Pot a
 Use the direct Kitchen client for Solana execution. The legacy SVM intent helper is incompatible
 with the released gated engine; the Solana guide below describes this boundary.
 
-- [Create and fund an intent](https://unpkg.com/@eco-incorp/sauce@0.99.3/docs/guides/intents.md)
-- [Compose nested intents](https://unpkg.com/@eco-incorp/sauce@0.99.3/docs/guides/nested-intents.md)
-- [Build programs with token, swap, deposit, and action helpers](https://unpkg.com/@eco-incorp/sauce@0.99.3/docs/guides/builders-and-actions.md)
-- [Execute on Solana](https://unpkg.com/@eco-incorp/sauce@0.99.3/docs/guides/solana.md)
-- [Verify settlement programs](https://unpkg.com/@eco-incorp/sauce@0.99.3/docs/guides/verification.md)
+- [Create and fund an intent](https://unpkg.com/@eco-incorp/sauce@0.99.4/docs/guides/intents.md)
+- [Compose nested intents](https://unpkg.com/@eco-incorp/sauce@0.99.4/docs/guides/nested-intents.md)
+- [Build programs with token, swap, deposit, and action helpers](https://unpkg.com/@eco-incorp/sauce@0.99.4/docs/guides/builders-and-actions.md)
+- [Execute on Solana](https://unpkg.com/@eco-incorp/sauce@0.99.4/docs/guides/solana.md)
+- [Verify settlement programs](https://unpkg.com/@eco-incorp/sauce@0.99.4/docs/guides/verification.md)
 
 ## Compiler and runtime
 
 The SDK includes **`@eco-incorp/sauce-compiler`**, the Rust/WebAssembly SauceScript compiler, and
 exposes it through `@eco-incorp/sauce/compiler`. Compile directly when you need entry arguments,
-custom module resolution, or SVM account manifests. See the [compiler guide](https://unpkg.com/@eco-incorp/sauce@0.99.3/docs/guides/compiling.md)
-and [compiler API](https://unpkg.com/@eco-incorp/sauce@0.99.3/docs/api/compiler.md).
+custom module resolution, or SVM account manifests. See the [compiler guide](https://unpkg.com/@eco-incorp/sauce@0.99.4/docs/guides/compiling.md)
+and [compiler API](https://unpkg.com/@eco-incorp/sauce@0.99.4/docs/api/compiler.md).
 
 SauceScript supports contract calls, arithmetic, control flow, and composition within the
-[compiler's language subset](https://unpkg.com/@eco-incorp/sauce@0.99.3/docs/concepts/saucescript.md). A program executes atomically in one
+[compiler's language subset](https://unpkg.com/@eco-incorp/sauce@0.99.4/docs/concepts/saucescript.md). A program executes atomically in one
 transaction on its target chain. Cross-chain intents coordinate separate transactions.
 
 The root SDK and its compiler integration require Node.js **24 or newer**. The compiler dependency also has its
-own browser entry point. See [architecture](https://unpkg.com/@eco-incorp/sauce@0.99.3/docs/concepts/architecture.md) for how the SDK,
+own browser entry point. See [architecture](https://unpkg.com/@eco-incorp/sauce@0.99.4/docs/concepts/architecture.md) for how the SDK,
 compiler, and deployed runtime work together.
 
-Current release pins: compiler **2.3.0**, EVM engine **1.0.1**, SVM engine **1.1.0**, both Kitchens
+Current release pins: compiler **2.3.0**, EVM engine **1.0.1**, SVM engine **1.2.0**, both Kitchens
 **1.0.0**. Release addresses do not establish on-chain deployment status.
 
 The EVM settle program compiles to **356 bytes** with a new verification hash. Recompile and
 invalidate cached programs when upgrading; to verify existing 362-byte payloads, pass their
 historical `{ hash, bytes: 362 }` pin to `validateSettleProgram` (see
-[verification](https://unpkg.com/@eco-incorp/sauce@0.99.3/docs/guides/verification.md)).
+[verification](https://unpkg.com/@eco-incorp/sauce@0.99.4/docs/guides/verification.md)).

package/dev-tools/README.md

@@ -6,11 +6,11 @@ To build an application with Sauce, install the SDK:
 pnpm add @eco-incorp/sauce
 ```
 
-Follow the [quick start](https://unpkg.com/@eco-incorp/sauce@0.99.3/docs/guides/quick-start.md)
-and [executable examples](https://unpkg.com/@eco-incorp/sauce@0.99.3/docs/examples/README.md)
+Follow the [quick start](https://unpkg.com/@eco-incorp/sauce@0.99.4/docs/guides/quick-start.md)
+and [executable examples](https://unpkg.com/@eco-incorp/sauce@0.99.4/docs/examples/README.md)
 for compiling programs and constructing Eco intents in your own project. You can also open the installed manual at `node_modules/@eco-incorp/sauce/docs/README.md`.
 
 The `sauce-dev-tools` scaffold contains older local deployment and execution scripts. Those scripts
 target an earlier EVM contract interface and are incompatible with current Kitchen/Pot deployments.
-Use the SDK's [execution guides](https://unpkg.com/@eco-incorp/sauce@0.99.3/docs/guides/compiling.md)
+Use the SDK's [execution guides](https://unpkg.com/@eco-incorp/sauce@0.99.4/docs/guides/compiling.md)
 for current programs.

package/docs/api/routes.md

@@ -79,7 +79,7 @@ The route wrapper has no runtime argument-payload parameter. Use compile-time de
 
 `sauceEvmDeployPotCall({ owner, salt, kitchen })` encodes Pot deployment through the supplied Kitchen; direct intent routes use the destination `Portal.executor()` as owner. Its `chainId` alternative selects the pinned release Kitchen only for chains in the historical successful-deployment roster. `v12Deployment` and `requireV12Deployment` also return current release addresses under that historical filter; none of these helpers verifies current on-chain deployment. Prefer explicit `v12KitchenAddress()` after checking the target chain. `V12_EVM_CONTRACTS` and `v12SvmProgramId` are legacy addresses; use the current `/deployments` address functions. [evm-execution.ts](../examples/evm-execution.ts) demonstrates prediction, deployment, and owner/Kitchen checks.
 
-`buildSauceSvmCall` and the SVM route path emit a legacy 8-byte staged-engine instruction, which is **incompatible with engine 1.1.0** even when supplied a code account and the current engine ID. They do not construct the required Kitchen call. Use the direct Kitchen client for Solana execution; see [the SVM intent limitation](../guides/solana.md#svm-destinations-in-eco-intents).
+`buildSauceSvmCall` and the SVM route path emit a legacy 8-byte staged-engine instruction, which is **incompatible with engine 1.2.0** even when supplied a code account and the current engine ID. They do not construct the required Kitchen call. Use the direct Kitchen client for Solana execution; see [the SVM intent limitation](../guides/solana.md#svm-destinations-in-eco-intents).
 
 ## Built intents
 

package/docs/guides/solana.md

@@ -71,10 +71,11 @@ After successful simulation, `client.execute(bytecode, manifest, resolution, { c
 
 ### Select the released programs and quote the fee
 
-The pinned SVM engine **1.1.0** is `7MetdnWSaEsowvUmVyvwrbAeUW9xXFpVWXUXw4MxZ5CG`;
+The pinned SVM engine **1.2.0** is `HB8b1oD5PB2ptkLH6EV56Rr9RHevutEfvG2YdA7an6rK`;
 Kitchen **1.0.0** is `SauceYLdWyabKFwtevSAgsSDoMjCoTKtx1HTb63eJot`.
 These are release addresses; confirm deployment on your cluster before use.
-Engine 1.1.0 adds direct paid calls. The SDK clients use Kitchen-mediated cooks;
+Engine 1.2.0 adds a code-hash-pinned staged variant of the direct paid calls introduced
+in 1.1.0. The SDK clients use Kitchen-mediated cooks;
 builders for the direct paid instructions are not yet exposed.
 Use the deployment helpers and read the Kitchen's fee configuration on the selected
 cluster. This example checks a caller-selected lamport budget before signing:
@@ -152,7 +153,7 @@ The low-level instruction builders return instructions; the application groups,
 For an SVM destination, `Solana(body, { execution, ... }).reward(...)`,
 `routes.compileSauceRoute()`, `buildSauceSvmCall()`, and `buildSauceSvmCalls()` emit
 a legacy `execute_from_account` instruction containing only its 8-byte
-discriminator. Engine 1.1.0 still requires another 65 bytes of Pot derivation material
+discriminator. Engine 1.2.0 still requires another 65 bytes of Pot derivation material
 and a trailing Pot signer supplied by the Kitchen.
 
 The [SVM Portal fulfillment implementation](https://github.com/eco/eco-routes-svm/blob/5e544b72d368d9d1f0ee5269e2a1a5d2a9f8c2f2/programs/portal/src/instructions/fulfill.rs#L139-L192)

package/docs/guides/verification.md

@@ -182,7 +182,7 @@ instruction are the ones the application expects.
 
 `decodeSvmSettleExecution({ instructionData, accounts })` resolves accounts
 positionally against the canonical settlement refs. The default `wireFormat: "gated-v1"` accepts raw **engine CPI instructions** produced by Kitchen 1.0.0 for
-engine 1.1.0:
+engine 1.2.0:
 
 | Instruction            | Data                                                               | Full CPI account list                  |
 | ---------------------- | ------------------------------------------------------------------ | -------------------------------------- |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@eco-incorp/sauce",
-  "version": "0.99.3",
+  "version": "0.99.4",
   "description": "Sauce protocol tooling: SDK, action primitives, and a local dev environment.",
   "type": "module",
   "repository": {

package/sdk/dist/artifacts/V12Deployments.json

@@ -11,8 +11,8 @@
       "commit": "f2f6dfbe38809304d83ca755eb7975c19d35ceab"
     },
     "v12-svm": {
-      "version": "1.1.0",
-      "commit": "5c809b3d001583c0fad81f23271eadb5265cd747"
+      "version": "1.2.0",
+      "commit": "a65ede3f42149bfe35ff22d8765e878e849914ae"
     },
     "kitchen-svm": {
       "version": "1.0.0",
@@ -67,8 +67,8 @@
     "clusterIndependent": true,
     "programs": {
       "engine": {
-        "programId": "7MetdnWSaEsowvUmVyvwrbAeUW9xXFpVWXUXw4MxZ5CG",
-        "label": "engine@1.1.0",
+        "programId": "HB8b1oD5PB2ptkLH6EV56Rr9RHevutEfvG2YdA7an6rK",
+        "label": "engine@1.2.0",
         "derivation": "ed25519 keypair from sha256(SOLANA_PROGRAM_KEY_SEED, label)",
         "upgradeAuthority": "none — deployed --final, so this program can never be upgraded or closed"
       },

package/sdk/dist/artifacts/svm/engine-wire-devnet.json

@@ -9,6 +9,7 @@
     "AccountNotSigner": 66,
     "AccountNotWritable": 62,
     "BytecodeOutOfBounds": 12,
+    "CodeHashMismatch": 72,
     "DataTooLarge": 41,
     "DivisionByZero": 50,
     "ExecutionFeeExceedsMaximum": 84,
@@ -51,6 +52,11 @@
       "bytecode": "account 0's data verbatim; instruction data is discriminator(8), max_execution_fee(u64 LE, 8), with no trailing bytes",
       "discriminator": "44d5e0657b813006"
     },
+    "cookAndPayFromAccountPinned": {
+      "accounts": "account 0 is the code; the caller's tail follows, then writable signer fee payer, executable System Program, canonical Kitchen ExecutionFeeConfig PDA (writable for a positive fee); code and payment accounts are excluded from the interpreter tail; SHA-256 of all code account data must equal the mandatory expected_sha256 before fee validation, payment or bytecode; holds the checked data borrow through execution; requires execution_fee <= max_execution_fee and validates config and payer even at zero fee; no Pot signing or code-buffer metadata validation",
+      "bytecode": "account 0's entire data verbatim, including appended arguments; instruction data is discriminator(8), max_execution_fee(u64 LE, 8), expected_sha256(32), with no trailing bytes",
+      "discriminator": "8dea491aee52402f"
+    },
     "execute": {
       "accounts": "the caller's tail at its natural indices, followed by the kitchen-signed acting Pot; the engine strips the acting Pot before execution",
       "bytecode": "instruction data, after discriminator(8), owner(32), salt(32), bump(1)",

package/sdk/dist/artifacts/svm/engine-wire-mainnet.json

@@ -9,6 +9,7 @@
     "AccountNotSigner": 66,
     "AccountNotWritable": 62,
     "BytecodeOutOfBounds": 12,
+    "CodeHashMismatch": 72,
     "DataTooLarge": 41,
     "DivisionByZero": 50,
     "ExecutionFeeExceedsMaximum": 84,
@@ -51,6 +52,11 @@
       "bytecode": "account 0's data verbatim; instruction data is discriminator(8), max_execution_fee(u64 LE, 8), with no trailing bytes",
       "discriminator": "44d5e0657b813006"
     },
+    "cookAndPayFromAccountPinned": {
+      "accounts": "account 0 is the code; the caller's tail follows, then writable signer fee payer, executable System Program, canonical Kitchen ExecutionFeeConfig PDA (writable for a positive fee); code and payment accounts are excluded from the interpreter tail; SHA-256 of all code account data must equal the mandatory expected_sha256 before fee validation, payment or bytecode; holds the checked data borrow through execution; requires execution_fee <= max_execution_fee and validates config and payer even at zero fee; no Pot signing or code-buffer metadata validation",
+      "bytecode": "account 0's entire data verbatim, including appended arguments; instruction data is discriminator(8), max_execution_fee(u64 LE, 8), expected_sha256(32), with no trailing bytes",
+      "discriminator": "8dea491aee52402f"
+    },
     "execute": {
       "accounts": "the caller's tail at its natural indices, followed by the kitchen-signed acting Pot; the engine strips the acting Pot before execution",
       "bytecode": "instruction data, after discriminator(8), owner(32), salt(32), bump(1)",