zkSync Era

Preview chain. Sauce supports transactions on Ethereum, Base, Arc and Solana, and the testnets Arc Testnet, Base Sepolia, Ethereum Sepolia, Solana Devnet and Solana Testnet only. On zkSync Era a program compiles (sauce compile) and the reads work (sauce globals, sauce price, sauce pools), and sauce simulate runs wherever the release is deployed on the chain, but the sauce command and the MCP server build and send no transaction: sauce tx, sauce run and sauce pot --deploy are refused, naming this chain and the supported chains: the last section shows the refusal and how to request this chain.

Fact	Value
Support	preview: compile and read; no transaction is built or sent
Slug (`--chain`)	`zksync`
Chain id	324
Kind	EVM
Name in a program	`Zksync`
In TypeScript	`import { Zksync } from "@eco-incorp/sauce"`: its tokens and protocol namespaces are properties of it
Native coin	ETH (Ether), 18 decimals
Sauce	the engine, Kitchen and Routers, at the same addresses on every EVM chain: Deployments

In a program

Compiled with --chain zksync, a program names zkSync Era’s tokens and contracts with no import; the same file compiled for another chain resolves each name there, or fails where the chain does not have it.

function main() {
  // `Across.SpokePool` is zkSync Era's spokePool: `0xE0B015E54d54fc84a6cB9B666099c46adE9335FF`.
  require(Across.SpokePool != 0);
  // The same contract, qualified by the chain's name, from a program on any chain.
  require(Zksync.Across.SpokePool == Across.SpokePool);
}

Tokens

The registry names no token on this chain: a program uses Token(<address>).

Protocols

Every protocol the registry records here, each contract with how a program names it: its namespace contract, or its ABI imported from ./protocols/<slug>/<Export>.json and bound to the address.

Protocol	Contract	Address	In a program
Across	spokePool	`0xE0B015E54d54fc84a6cB9B666099c46adE9335FF`	`Across.SpokePool`
KyberSwap Aggregator	metaAggregationRouter	`0x3F95eF3f2eAca871858dbE20A93c01daF6C2e923`	`KyberswapAggregator.MetaAggregationRouter`
LayerZero	endpointV2	`0xd07C30aF3Ff30D96BDc9c6044958230Eb797DDBF`	`Layerzero.EndpointV2`
SyncSwap	router	`0x2da10A1e27bF85cEdD8FFb1AbBe97e53391C0295`	`Syncswap.Router`
ZeroLend	pool	`0x4d9429246EA989C9CeE203B43F6d1C7D83e3B8F8`	`Zerolend.Pool`
zkSync Native Bridge	l2Bridge	`0x11f943b2c77b743AB90f4A0Ae7d5A4e7FCA3E102`	`ZksyncBridge.L2Bridge`

Requesting support

On zkSync Era, sauce tx, sauce run and sauce pot --deploy exit with status 1 before they reach an endpoint or read a key. The first line sauce tx prints is:

sauce tx: building the cook transaction is refused: it involves zksync (zkSync Era, chain id 324), a preview chain. The sauce command and its MCP server build and send transactions only on Ethereum, Base, Arc and Solana, and the testnets Arc Testnet, Base Sepolia, Ethereum Sepolia, Solana Devnet and Solana Testnet. On a preview chain they build and send none. A program still compiles there and globals, price, pools and pot's prediction still read; simulate runs wherever the release is deployed on the chain, and says so where it is not.

To request zkSync Era, contact Eco through Support and community, naming the chain and its id (zkSync Era, 324) and what you want to run there.

Next steps

Chains: every other chain, with its support.
Names and registries: how a name in a program becomes an address on the chain it is compiled for.
Glossary: the words these pages use, in plain terms.

Start here

Integration guides

Language reference

SauceScript libraries

Runtime and security

Troubleshooting and production

Chains and protocols

@eco-incorp/sauce

@eco-incorp/sauce-compiler

In a program

Tokens

Protocols

Requesting support

Next steps

​In a program

​Tokens

​Protocols

​Requesting support

​Next steps

In a program

Tokens

Protocols

Requesting support

Next steps