DOCUMENTATION
cast key-authorization encode
RLP-encode an unsigned Tempo key authorization
$ cast key-authorization encode --helpUsage: cast key-authorization encode [OPTIONS] --chain-id <CHAIN_ID> <KEY_ADDRESS>
Arguments:
<KEY_ADDRESS>
Key address to authorize
Options:
--chain-id <CHAIN_ID>
Chain ID for replay protection
--key-type <KEY_TYPE>
Type of access key being authorized: secp256k1, p256, or webauthn. The
root signature type is determined by the configured signer
[default: secp256k1]
--expiry <EXPIRY>
Expiry timestamp (unix seconds). Omit for no expiry
--enforce-limits
Enforce spending limits for this key. With no --limit entries, this
means no spending
--limit <LIMITS>
Spending limit in `TOKEN:AMOUNT[:PERIOD]` format. Can be specified
multiple times
--scope <SCOPE>
Call scope restriction in `TARGET[:SELECTORS[@RECIPIENTS]]` format.
TARGET alone allows all calls to that target
--scopes <SCOPES_JSON>
Call scope restrictions as a JSON array
--witness <WITNESS>
Optional TIP-1053 witness to include in the authorization signing
hash.
`0x000...000` is a valid present witness and is distinct from omitting
the flag.
-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
[aliases: --jobs]
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
--machine
Activate the agent contract: disables color and wraps CLI-runtime
exits (parse / usage / help / version) in a structured envelope.
Per-command machine output (declared `output_mode`, progress and
prompt suppression, canonical exit codes) is adopted incrementally —
see `docs/agents/spec` §10. Mutually exclusive with `--json` and
`--md` to keep machine-mode output unambiguous
--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.