Ethereum and EVM Compatible Blockchains (alpha) Signers
secret_key
The evm::secret_key signer can be used to synchronously sign a transaction.
Inputs
- Name
secret_key- Description
The secret key used to sign messages and transactions.
- Name
mnemonic- Description
The mnemonic phrase used to generate the secret key. This input will not be used if the
secret_keyinput is provided.
- Name
derivation_path- Description
The derivation path used to generate the secret key. This input will not be used if the
secret_keyinput is provided.
- Name
is_encrypted- Description
Coming soon
- Name
password- Description
Coming soon
Outputs
When the secret_key action is successfully executed, the following outputs are attached to the action
- Name
public_key- Description
The public key of the account generated from the secret key.
- Name
address- Description
The address generated from the secret key.
Example using 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"
}
web_wallet
The 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- 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.
Outputs
When the web_wallet action is successfully executed, the following outputs are attached to the action
- Name
address- Description
The address of the account generated from the public key.
Example using web_wallet
signer "alice" "evm::web_wallet" {
expected_address = "0xCe246168E59dd8e28e367BB49b38Dc621768F425"
}