Skip to main content
Supported testnet. Sauce supports transactions on Ethereum, Base, Arc and Solana, and the testnets Arc Testnet, Base Sepolia, Ethereum Sepolia, Solana Devnet and Solana Testnet. On Solana Testnet a program compiles and simulates, and the sauce command and the MCP server build its transactions and send them. Solana Testnet is a test network: its coin and tokens have no value.

Notes

Solana’s testnet cluster, a chain of its own. Testnet runs devnet’s engine build, so a program compiled for it reads its chain id as 1399811150, as on devnet; 1399811151 is the SDK’s key for the chain, which names it to the command and the Pot store and which no program reads. Its symbols are testnet’s mints: the wrapped native alone, as Circle publishes no testnet USDC. The release’s engine and Kitchen are deployed on testnet, with zero execution fees. Its endpoint must serve testnet: one of another cluster is refused. The Solana venues are mainnet’s programs and pools, so a venue name is refused here.

In a program

Compiled with --chain solana-testnet, a program names Solana Testnet’s mints with no import: a symbol is the mint’s 32-byte key, a value the @sauce/token functions take. A token account is an Account parameter (Solana).

Tokens

Accounts

The accounts a program writes where it uses them, each added to main, derived when the cook is built (so what it is made of is known then) and checked on chain at the top of main to be the account it names. Each is read-only unless .writable() or .signer() gives it that role.

Protocols

The registry records no protocol deployment on this chain.

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.