---
description: "Set the caller's storage credit spend budget, which also selects `direct` mode. The budget only applies within the transaction that sets it; batch it with the storage operations it should govern."
---

_Generated from `cast storage-credits set-budget --help`; see [CLI reference versions](/reference/versions). Regenerate this page instead of editing it directly._

## cast storage-credits set-budget

Set the caller's storage credit spend budget, which also selects `direct` mode.

The budget only applies within the transaction that sets it; batch it with the
storage operations it should govern.

:::terminal

```bash
$ cast storage-credits set-budget --help
```

```txt
Usage: cast storage-credits set-budget [OPTIONS] <CREDITS>

Arguments:
  <CREDITS>
          Maximum number of credits the caller may spend in `direct` mode this
          transaction

Options:
      --async
          Only print the transaction hash and exit immediately
          
          [env: CAST_ASYNC=]

      --sync
          Wait for transaction receipt synchronously instead of polling. Note:
          uses `eth_sendTransactionSync` which may not be supported by all
          clients

      --confirmations <CONFIRMATIONS>
          The number of confirmations until the receipt is fetched
          
          [default: 1]

      --timeout <TIMEOUT>
          Timeout for sending the transaction
          
          [env: ETH_TIMEOUT=]

      --poll-interval <POLL_INTERVAL>
          Polling interval for transaction receipts (in seconds)
          
          [env: ETH_POLL_INTERVAL=]

  -h, --help
          Print help (see a summary with '-h')

  -j, --threads <THREADS>
          Number of threads to use. Specifying 0 defaults to the number of
          logical cores
          
          [alias: --jobs]

      --profile <PROFILE>
          The configuration profile to use

Rpc options:
  -r, --rpc-url <URL>
          The RPC endpoint
          
          [alias: --fork-url]

  -k, --insecure
          Allow insecure RPC connections (accept invalid HTTPS certificates).
          
          When the provider's inner runtime transport variant is HTTP, this
          configures the reqwest client to accept invalid certificates.

      --rpc-timeout <RPC_TIMEOUT>
          Timeout for the RPC request in seconds.
          
          The specified timeout will be used to override the default timeout for
          RPC requests.
          
          Default value: 45
          
          [env: ETH_RPC_TIMEOUT=]

      --no-proxy
          Disable automatic proxy detection.
          
          Use this in sandboxed environments (e.g., Cursor IDE sandbox, macOS
          App Sandbox) where system proxy detection causes crashes. When
          enabled, HTTP_PROXY/HTTPS_PROXY environment variables and system proxy
          settings will be ignored.

      --compute-units-per-second <CUPS>
          Sets the number of assumed available compute units per second for this
          provider.
          
          default value: 330
          
          See also
          [https://docs.alchemy.com/reference/compute-units#what-are-cups-compute-units-per-second](https://docs.alchemy.com/reference/compute-units#what-are-cups-compute-units-per-second)

      --no-rpc-rate-limit
          Disables rate limiting for this node's provider.
          
          See also
          [https://docs.alchemy.com/reference/compute-units#what-are-cups-compute-units-per-second](https://docs.alchemy.com/reference/compute-units#what-are-cups-compute-units-per-second)
          
          [alias: --no-rate-limit]

      --flashbots
          Use the Flashbots RPC URL with fast mode
          ([https://rpc.flashbots.net/fast](https://rpc.flashbots.net/fast)).
          
          This shares the transaction privately with all registered builders.
          
          See:
          [https://docs.flashbots.net/flashbots-protect/quick-start#faster-transactions](https://docs.flashbots.net/flashbots-protect/quick-start#faster-transactions)

      --jwt-secret <JWT_SECRET>
          JWT Secret for the RPC endpoint.
          
          The JWT secret will be used to create a JWT for an RPC. For example,
          the following can be used to simulate a CL `engine_forkchoiceUpdated`
          call:
          
          cast rpc --jwt-secret <JWT_SECRET> engine_forkchoiceUpdatedV2
          '["0x6bb38c26db65749ab6e472080a3d20a2f35776494e72016d1e339593f21c59bc",
          "0x6bb38c26db65749ab6e472080a3d20a2f35776494e72016d1e339593f21c59bc",
          "0x6bb38c26db65749ab6e472080a3d20a2f35776494e72016d1e339593f21c59bc"]'
          
          [env: ETH_RPC_JWT_SECRET=]

      --rpc-headers <RPC_HEADERS>
          Specify custom headers for RPC requests
          
          [env: ETH_RPC_HEADERS=]

      --curl
          Print the equivalent curl command instead of making the RPC request

  -e, --etherscan-api-key <KEY>
          The Etherscan (or equivalent) API key
          
          [env: ETHERSCAN_API_KEY=]

  -c, --chain <CHAIN>
          The chain name or EIP-155 chain ID
          
          [env: CHAIN=]

Wallet options - raw:
  -f, --from <ADDRESS>
          The sender account
          
          [env: ETH_FROM=]

  -i, --interactive
          Open an interactive prompt to enter your private key

      --private-key <RAW_PRIVATE_KEY>
          Use the provided private key

      --mnemonic <MNEMONIC>
          Use the mnemonic phrase of mnemonic file at the specified path

      --mnemonic-passphrase <PASSPHRASE>
          Use a BIP39 passphrase for the mnemonic

      --mnemonic-derivation-path <PATH>
          The wallet derivation path.
          
          Works with both --mnemonic-path and hardware wallets.

      --mnemonic-index <INDEX>
          Use the private key from the given mnemonic index.
          
          Used with --mnemonic-path.
          
          [default: 0]

Wallet options - keystore:
      --keystore <PATH>
          Use the keystore in the given folder or file
          
          [env: ETH_KEYSTORE=]

      --account <ACCOUNT_NAME>
          Use a keystore from the default keystores folder
          (~/.foundry/keystores) by its filename
          
          [env: ETH_KEYSTORE_ACCOUNT=]

      --password <PASSWORD>
          The keystore password.
          
          Used with --keystore.

      --password-file <PASSWORD_FILE>
          The keystore password file path.
          
          Used with --keystore.
          
          [env: ETH_PASSWORD=]

Wallet options - hardware wallet:
  -l, --ledger
          Use a Ledger hardware wallet

  -t, --trezor
          Use a Trezor hardware wallet

Wallet options - remote:
      --aws
          Use AWS Key Management Service.
          
          Ensure the AWS_KMS_KEY_ID environment variable is set.

      --gcp
          Use Google Cloud Key Management Service.
          
          Ensure the following environment variables are set: GCP_PROJECT_ID,
          GCP_LOCATION, GCP_KEY_RING, GCP_KEY_NAME, GCP_KEY_VERSION.
          
          See: [https://cloud.google.com/kms/docs](https://cloud.google.com/kms/docs)

      --turnkey
          Use Turnkey.
          
          Ensure the following environment variables are set:
          TURNKEY_API_PRIVATE_KEY, TURNKEY_ORGANIZATION_ID, TURNKEY_ADDRESS.
          
          See: [https://docs.turnkey.com/getting-started/quickstart](https://docs.turnkey.com/getting-started/quickstart)

Wallet options - Tempo:
      --tempo.access-key <PRIVATE_KEY>
          Tempo access key private key.
          
          When set, the transaction is signed with this access key on behalf of
          `--tempo.root-account`.
          
          [env: TEMPO_ACCESS_KEY=]

      --tempo.root-account <ADDRESS>
          Tempo root account address (the `from` address for keychain
          transactions).
          
          Required when `--tempo.access-key` is set.
          
          [env: TEMPO_ROOT_ACCOUNT=]

Wallet options - browser wallet:
      --browser
          Use a browser wallet

      --browser-port <PORT>
          Port for the browser wallet server
          
          [default: 9545]

      --browser-disable-open
          Whether to open the browser for wallet connection

Transaction options:
      --gas-limit <GAS_LIMIT>
          Gas limit for the transaction
          
          [env: ETH_GAS_LIMIT=]

      --gas-price <GAS_PRICE>
          Gas price for legacy transactions, or max fee per gas for EIP1559
          transactions
          
          [env: ETH_GAS_PRICE=]

      --priority-gas-price <PRIORITY_GAS_PRICE>
          Max priority fee per gas for EIP1559 transactions
          
          [env: ETH_PRIORITY_GAS_PRICE=]

      --nonce <NONCE>
          Nonce for the transaction

Tempo:
      --tempo.session <SESSION_ID>
          Use a live Tempo wallet session for signing.
          
          When set, Foundry resolves the session from
          `$TEMPO_HOME/wallet/sessions.toml` and signs Tempo transactions with
          the session's temporary access key on behalf of its root account.

      --tempo.fee-token <FEE_TOKEN>
          Fee token address, numeric TIP-20 token id, or known symbol for Tempo
          transactions.
          
          When set, builds a Tempo (type 0x76) transaction that pays gas fees in
          the specified token. Known symbols are PathUSD, AlphaUSD, BetaUSD, and
          ThetaUSD.
          
          If this is not set, the fee token is chosen according to network
          rules. See the Tempo docs for more information.

      --tempo.expires <SECONDS>
          Opt into TIP-1009 expiring-nonce mode with a validity window.
          
          Convenience flag that combines `--tempo.expiring-nonce` with a
          relative `--tempo.valid-before`. Sets nonce_key = U256::MAX, nonce =
          0, and valid_before = now + seconds.
          
          Maximum value is 30 seconds. The transaction must be mined before the
          deadline or it becomes permanently invalid, giving safe retry
          semantics: retries produce a fresh tx hash and the old tx can never
          land late.

      --tempo.nonce-key <NONCE_KEY>
          Nonce key for Tempo parallelizable nonces.
          
          When set, builds a Tempo (type 0x76) transaction with the specified
          nonce key, allowing multiple transactions with the same nonce but
          different keys to be executed in parallel. If not set, the protocol
          nonce key (0) will be used.
          
          For more information see
          [https://docs.tempo.xyz/protocol/transactions/spec-tempo-transaction#parallelizable-nonces](https://docs.tempo.xyz/protocol/transactions/spec-tempo-transaction#parallelizable-nonces).

      --tempo.lane <NAME>
          Named nonce lane for Tempo parallelizable nonces.
          
          Resolves a friendly lane name (e.g. `deploy`, `payments`) to a
          `nonce_key` via a shared lanes file (default: `tempo.lanes.toml` at
          the project root). The lanes file is a TOML map of `name = <U256>`
          entries, e.g.:
          
          ```toml deploy   = 1 ops      = 2 payments = 3 ```
          
          Mutually exclusive with `--tempo.nonce-key`.

      --tempo.lanes-file <PATH>
          Path to the Tempo lanes file used by `--tempo.lane`.
          
          Defaults to `tempo.lanes.toml` at the project root.

      --tempo.sponsor <ADDRESS>
          Sponsor (fee payer) address for Tempo sponsored transactions

      --tempo.sponsor-signer <SIGNER>
          Sign Tempo sponsor digests in-band with the given signer URI.
          
          Supported forms include `env://VAR`, `keystore://PATH`,
          `account://NAME`, `ledger://`, `trezor://`, `aws://`, `gcp://`,
          `turnkey://`, and `private-key://KEY`.

      --tempo.sponsor-sig <SPONSOR_SIG>
          Sponsor (fee payer) signature for Tempo sponsored transactions.
          
          The sponsor signs the `fee_payer_signature_hash` to commit to paying
          gas fees on behalf of the sender. Provide as a hex-encoded signature.

      --sponsor-url <URL>
          Remote sponsor (fee payer) service URL.
          
          When set, the user-signed transaction is forwarded to this URL via
          `eth_signRawTransaction`. The service adds its fee payer signature and
          returns the fully-sponsored transaction, which is then submitted via
          the regular RPC. No local sponsor key is required.
          
          Example: `cast send 0x... --sponsor-url
          https://sponsor.tempo.xyz/tp_abc123`
          
          [env: TEMPO_SPONSOR_URL=]

      --tempo.print-sponsor-hash
          Print the sponsor signature hash and exit.
          
          Computes the `fee_payer_signature_hash` for the transaction so that a
          sponsor knows what hash to sign. The transaction is not sent.

      --tempo.key-id <KEY_ID>
          Access key ID for Tempo Keychain signature transactions.
          
          Used during gas estimation to override the key_id that would normally
          be recovered from the signature.

      --tempo.expiring-nonce
          Enable expiring nonce mode for Tempo transactions.
          
          Sets nonce to 0 and nonce_key to U256::MAX, enabling time-bounded
          transaction validity via `--tempo.valid-before` and
          `--tempo.valid-after`.

      --tempo.valid-before <VALID_BEFORE>
          Upper bound timestamp for Tempo expiring nonce transactions.
          
          The transaction is only valid before this unix timestamp. Requires
          `--tempo.expiring-nonce`.

      --tempo.valid-after <VALID_AFTER>
          Lower bound timestamp for Tempo expiring nonce transactions.
          
          The transaction is only valid after this unix timestamp. Requires
          `--tempo.expiring-nonce`.

Display options:
      --color <COLOR>
          The color of the log messages

          Possible values:
          - auto:   Intelligently guess whether to use color output (default)
          - always: Force color output
          - never:  Force disable color output

      --json
          Format log messages as JSON

      --md
          Format log messages as Markdown

  -q, --quiet
          Do not print log messages

  -v, --verbosity...
          Verbosity level of the log messages.
          
          Pass multiple times to increase the verbosity (e.g. -v, -vv, -vvv).
          
          Depending on the context the verbosity levels have different meanings.
          
          For example, the verbosity levels of the EVM are:
          - 2 (-vv): Print logs for all tests.
          - 3 (-vvv): Print execution traces for failing tests.
          - 4 (-vvvv): Print execution traces for all tests, and setup traces
          for failing tests.
          - 5 (-vvvvv): Print execution and setup traces for all tests,
          including storage changes and
            backtraces with line numbers.
```

:::