ethereum, base, arc, solana, arc-testnet, base-sepolia, sepolia, solana-devnet, solana-testnet); every other chain is a preview chain, as the last
section says.
Supported and preview chains
Every chain but Ethereum, Base, Arc and Solana, and the testnets Arc Testnet, Base Sepolia, Ethereum Sepolia, Solana Devnet and Solana Testnet is a preview chain: a program compiles and the reads work there, andsauce simulate runs wherever the release is
deployed on the chain, but the sauce command and the MCP server build and
send no transaction, and say so, naming the chain and the supported chains. To
request one, contact Eco through Support and community, naming
the chain and its id; each preview chain’s page ends with the refusal it prints.
On a preview chain the sauce command and the MCP server still compile and read: sauce compile, sauce globals, sauce price, sauce pools and sauce pot’s prediction. sauce simulate does not depend on the label: it runs wherever the release is deployed on the
chain, and says so where it is not. What they refuse there, before any endpoint is reached or any
key is read, is building or sending a transaction;
the command’s and
the server’s lists name each one. Every
refusal names the supported chains, and the MCP server’s sauce_chains gives each chain’s
support.
The TypeScript SDK is not gated: its builders take every chain on this page and build its
transactions, and an integrator who submits one on a preview chain does so at their own risk.
A request for a chain names the chain and its id, what you want to run there, the protocols
and tokens it needs, and the volume you expect and from when.
Next steps
- Tokens: every chain’s tokens, by the symbol a program writes.
- Protocols: every protocol a program can call by name.
- 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.