> ## 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 tx > Print the unsigned cook transaction, or the plan that deploys the Pot first, for any wallet to sign `sauce tx` compiles a program and prints the unsigned transaction that runs it on a Pot, for a wallet or signer of your choice to sign. ## Synopsis ```bash theme={null} sauce tx --chain (--owner
| --pot
) [options] sauce tx --chain solana --owner [--account NAME=]… [options] ``` ## Description `sauce tx` compiles the file (a `.sauce.ts` program or an [actions document](https://docs.eco.com/sauce-sdk/cli/actions.md)) and prints the [cook](https://docs.eco.com/sauce/cook.md) unsigned, as JSON: `{ chainId, to, data, value }`, where `to` is the Pot and `data` is `Pot.cook(engine, program ++ arguments)`. It never takes a key and signs nothing. The value is `--value`, else the Kitchen's execution fee read from the chain. Reading the fee also reads the Pot. * **A Pot with no code yet.** The command prints a plan instead, `{ chainId, pot, transactions }`: `Kitchen.deployPot` first (marked `deploysPot`; any account may send it), then the cook. Send them in that order. * **Gas.** Each transaction of a plan carries a `gas` limit the command simulated: the cook's is estimated as if the transactions before it had landed, with 30% room. When the cook would revert on the chain as it is (an unfunded Pot), the transactions carry no `gas`, and stderr says why. * **Batches.** Each transaction is in the shape a wallet's send call takes (`value` and `gas` in hex), and `sendCalls` holds all of them as one batch, for a wallet that sends a batch. * **`--fund TOKEN:amount`** plans a plain transfer of each token from the owner into the Pot before the cook. With an endpoint, an EVM Pot that has no code yet is deployed first, so the transfer comes after the deployment. With `--offline` the command cannot check whether the Pot is deployed, and the plan has no deployment step: deploy the Pot first. `ETH:` adds to the cook's value instead. Sent as one batch, a smart wallet deploys, funds and cooks with one approval, or nothing happens. [Funding a Pot](https://docs.eco.com/sauce-sdk/cli/funding.md) covers the amount syntax. * **`--format cast`** prints each transaction as a `cast send` line with placeholders. What must hold for the transaction to land goes to stderr: on an EVM chain, the Pot funded after its deployment, and the cook sent from its owner (`cook()` is `onlyOwner`). On Arc and Arc Testnet, stderr also says that a transaction is included only with a `maxFeePerGas` of at least 20 gwei, the chain's minimum base fee; the printed transactions carry no fee fields. **On Solana** it prints `{ chain, via, feePayer, pot, fee, maxExecutionFee, createsPot, transaction }`: the Kitchen's cook as a base64 transaction signed by no one, for `--owner` to sign, or with `--via engine` the engine's own paid cook, with no Pot. A Pot not created yet is created by the same transaction, ahead of the cook (`createsPot`). The command reads the cluster for the blockhash and the fee. [Solana](https://docs.eco.com/sauce-sdk/cli/solana.md) covers the account forms and the plan a cook too large for one transaction becomes. `sauce tx` prints a transaction 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, with a message that names the supported chains and how to request the refused one. ## Prerequisites On an EVM chain, the release's engine must be deployed on the chain for the cook to run. `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