DOCUMENTATION

Generated from cast tempo import-access-key --help; see CLI reference versions. Regenerate this page instead of editing it directly.

cast tempo import-access-key

Import a signed secp256k1 access key into the Tempo Accounts store.

The signed authorization may be pending or already provisioned. The access-key private key is persisted to store.json; the authorizing root key is never stored.

$ cast tempo import-access-key --help
Usage: cast tempo import-access-key [OPTIONS] --account <ACCOUNT> --access-key <ACCESS_KEY> --authorization <AUTHORIZATION>

Options:
      --account <ACCOUNT>
          Root Tempo account controlled by the access key

      --access-key <ACCESS_KEY>
          Access-key private key to persist

          [env: TEMPO_ACCESS_KEY]

      --authorization <AUTHORIZATION>
          Signed key authorization encoded as RLP hex

  -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

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.