Skip to main content
Start with Getting started with Sauce to prepare a Pot, read fees and build an intent. This page shows how to use the standalone compiler and find the corresponding API entries.

Prerequisites

  • Node 24 or later.
  • Install the documented SDK version: npm install --save-exact @eco-incorp/sauce@0.99.4.
The example below compiles locally and does not submit a transaction.

Compile a standalone program

The direct compiler returns one reusable program plus its metadata; main arguments are appended per execution. With compactArgs: true the result carries an entrySchema for the compact codec.
The result also reports isaRevision (stack-compact-v2) and, on the svm target, the account manifest. Reference: compiler subpath, compact arguments, @eco-incorp/sauce-compiler.

Read deployments and registries

Release addresses do not establish that a chain has the deployment; check code on the target chain, as the SDK’s prepareDestinationPot example does. The legacy per-chain roster (isV12Live) records an older deployment and does not attest the pinned release. Reference: deployments, chains, protocols.

Next steps

@eco-incorp/sauce/evm/engine exposes the Pot and Kitchen ABIs and call encoders (v12Pot.encodeCook). @eco-incorp/sauce/svm exposes createSauceSvmClient for Solana. Reference: evm/engine, svm client. The steps are on Getting started with Sauce.