Skip to content

cast wallet verify

Verify the signature of a message

$ cast wallet verify --help
Usage: cast wallet verify [OPTIONS] --address <ADDRESS> <MESSAGE> <SIGNATURE>

Arguments:
  <MESSAGE>
          The original message.
          
          Treats 0x-prefixed strings as hex encoded bytes. Non 0x-prefixed
          strings are treated as raw input message.
          
          The message will be prefixed with the Ethereum Signed Message header
          and hashed before signing, unless `--no-hash` is provided.
          
          Typed data can be provided as a json string or a file name. Use --data
          flag to denote the message is a string of typed data. Use --data
          --from-file to denote the message is a file name containing typed
          data. The data will be combined and hashed using the EIP712
          specification before signing. The data should be formatted as JSON.

  <SIGNATURE>
          The signature to verify

Options:
  -a, --address <ADDRESS>
          The address of the message signer

      --data
          Treat the message as JSON typed data

      --from-file
          Treat the message as a file containing JSON typed data. Requires
          `--data`

      --no-hash
          Treat the message as a raw 32-byte hash and sign it directly without
          hashing it again

  -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

      --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.