> ## Documentation Index > Fetch the complete documentation index at: https://docs.eco.com/llms.txt > Use this file to discover all available pages before exploring further. # sauce run > Compile a program, sign its cook on your Pot, send it and wait for the receipt `sauce run` compiles a program, builds the cook on the signer's Pot, simulates it, signs it, sends it and waits for the receipt. ## Synopsis ```bash theme={null} sauce run --chain (--keystore | --private-key ) [options] sauce run --chain solana --keypair [--account NAME=]… [options] ``` ## Description `sauce run` compiles the file (a `.sauce.ts` program or an [actions document](https://docs.eco.com/sauce-sdk/cli/actions.md)) and builds the [cook](https://docs.eco.com/sauce/cook.md) on the signer's [Pot](https://docs.eco.com/sauce/pot.md), or on the Pot `--pot` names. The signer is the owner. It simulates the cook first and sends nothing when the simulation fails: it prints the decoded reason and exits `1`. It then signs the cook, sends it, waits for the receipt and prints the transaction hash, status and gas used, the explorer and trace links, what it cost and what moved, or the decoded reason it reverted (exit `1`). The cook's value defaults to the Kitchen's execution fee, read from the chain. When the program also spends native coin, pass `--value` with the fee plus what it spends; a `--value` below the fee is refused. The signer is one of `--wallet` (a wallet made with [`sauce wallet`](https://docs.eco.com/sauce-sdk/cli/wallet)), `--keystore`, `--private-key` or, on Solana, `--keypair`. A wallet's `.policy.json`, when present, limits what each transaction moves ([Wallets and policy](https://docs.eco.com/sauce-sdk/cli/wallets-and-policy.md)). ### What it sends before the cook You do not deploy the Pot as a separate step: a run deploys it when it first needs it, before it moves any `--fund` tokens in. On an EVM chain, if you send tokens to the Pot yourself instead, deploy it first with [`sauce pot --deploy`](https://docs.eco.com/sauce-sdk/cli/pot): until it is deployed, its address follows the Kitchen ([Funding a Pot](https://docs.eco.com/sauce-sdk/cli/funding.md)). Each transaction the run sends before its cook is a transaction of its own, and the run asks you to approve it at the terminal first: * deploying your Pot, when it has no code yet (asked as `[deploy/cancel]`, with its gas); * approving Permit2 for a token `--fund` pulls, the first time (`--fund-mode permit2`); a wallet whose policy limits the token refuses it; * approving the Pot for the amount `--fund` pulls (`--fund-mode allowance`). `-y` (`--yes`, or its older name `--auto-approve`) approves each of them without asking and prints `auto-approved: ` for each. With no terminal to ask on (CI, a pipe, a program read from stdin with no terminal), or with `--json`, the run sends nothing until they are approved: it names each approval it needs and `--yes`, and exits `1`. On Solana a missing Pot is created in the cook's own transaction, with nothing asked, when the two fit in one transaction. Otherwise it is asked for like the rest. On an EVM chain the run holds its whole plan to the [Pot guard](https://docs.eco.com/sauce-sdk/cli/pot.md#the-pot-guard) before it sends the first of these: the Pot must be where the deployed Kitchen puts it, or a deployed Pot the Kitchen created, and a step the guard refuses stops the run before anything is sent. It checks the rest of the plan again before each transaction, since an answer at the terminal can take a while. ### Funding `--fund TOKEN:amount` gets tokens from your wallet into the Pot in the same cook: the program is wrapped so it first pulls each amount, then runs, then, with `--sweep`, returns what is left. [Funding a Pot](https://docs.eco.com/sauce-sdk/cli/funding.md) covers the amount syntax and each `--fund-mode`. ### Solana On Solana the run signs with `--keypair` (or a Solana wallet) and reads the Kitchen's fee from the cluster. A missing Pot, and a `pot:` or `owner:` account the cook names that the cluster does not have yet, are created, the owner paying the rent. A program too large for one transaction is staged in a code buffer first and the buffer is closed after the cook. The cook signs the fee it read as its maximum execution fee; `--max-execution-fee` refuses a higher fee before anything is sent. A failure prints the program logs. [Solana](https://docs.eco.com/sauce-sdk/cli/solana.md) covers `--via engine` and the account forms. ### Supported chains `sauce run` sends only on a supported chain: Ethereum, Base, Arc and Solana, and the testnets Arc Testnet, Base Sepolia, Ethereum Sepolia, Solana Devnet and Solana Testnet. On a preview chain it is refused before anything is read or signed, with a message that names the supported chains and how to request the refused one. `sauce compile` works there, and `sauce simulate` runs wherever the release's engine and Kitchen are deployed. ## Prerequisites * A signer that holds the chain's native coin for gas and the Kitchen's fee. * On an EVM chain, the release's engine deployed on the chain. `sauce pot --chain --owner
` reports whether it is. ## Options | Option | Description | | - | - | | `--chain ` | The chain the program runs on (`base`, `8453`, `solana`) | | `--target ` | Checked against the chain. `svm` with no `--chain` means Solana | | `--source-dir ` | The directory the program's relative imports resolve from. Default: beside the file; for stdin, the current directory | | `--owner
` | The Pot's owner, which derives the Pot with the salt (default salt 0) | | `--salt