Ethereum and EVM Compatible Blockchains (beta) Signers

signer

secret_key

The evm::secret_key signer can be used to synchronously sign a transaction.

Inputs

  • Name
    secret_key
    Required
    optional
    Type
    string
    Description

    The secret key used to sign messages and transactions.

  • Name
    mnemonic
    Required
    optional
    Type
    string
    Description

    The mnemonic phrase used to generate the secret key. This input will not be used if the secret_key input is provided.

  • Name
    derivation_path
    Required
    optional
    Type
    string
    Description

    The derivation path used to generate the secret key. This input will not be used if the secret_key input is provided.

  • Name
    is_encrypted
    Required
    optional
    Type
    bool
    Description

    Coming soon

  • Name
    password
    Required
    optional
    Type
    string
    Description

    Coming soon

Outputs

  • Name
    public_key
    Type
    array[buffer]
    Description

    The public key of the account generated from the secret key.

  • Name
    address
    Type
    array[buffer]
    Description

    The address generated from the secret key.

Example using secret_key

// we can create a secret key signer by providing a mnemonic and computing the secret key
signer "bob" "evm::secret_key" {
    mnemonic = "board list obtain sugar hour worth raven scout denial thunder horse logic fury scorpion fold genuine phrase wealth news aim below celery when cabin"
    derivation_path = "m/44'/5757'/0'/0/0"
}
// or we can create one by providing the secret key directly
signer "bob_again" "evm::secret_key" {
    secret_key = "03b3e0a76b292b2c83fc0ac14ae6160d0438ebe94e14bbb5b7755153628886e08e"
}


signer

web_wallet

The evm::web_wallet signer will route the transaction signing process through wagmi. This allows a Runbook operator to sign the transaction with the browser signer of their choice.

Inputs

  • Name
    expected_address
    Required
    optional
    Type
    string
    Description

    The EVM address that is expected to connect to the Runbook execution. Omitting this field will allow any address to be used for this signer.

  • Name
    chain_id
    Required
    required
    Type
    string
    Description

    The chain id.

  • Name
    rpc_api_url
    Required
    required
    Type
    string
    Description

    The URL of the EVM API used to broadcast the transaction.

Outputs

  • Name
    address
    Type
    array[string]
    Description

    The address of the account generated from the public key.

Example using web_wallet

signer "alice" "evm::web_wallet" {
    expected_address = "0xCe246168E59dd8e28e367BB49b38Dc621768F425"
}


Was this page helpful?