verify-auth
Verify signed challenge message with BLS public key
Verify signed challenge message with BLS public key
Usage
otcli operator bls verify-auth [options]Options
--l1-chain required
string
The name of the L1 chain where the AVS contracts will be deployed.
--l2-chain required
string
The name of the L2 chain where the AVS contracts will be deployed.
--browser-sign optional
flag
Allows signing using wallets like MetaMask, SAFE, or other browser-based smart accounts. Ideal for multisig operations and smart contract wallets, especially when users prefer not to expose private keys directly in the CLI.
--message-hash required
string
Hashed message to be verified
--operator-id required
number
Operator ID to get BLS public key
--bls-pub-key optional
strings separated by commas
BLS public key to verify the signature.
3313774884859600093202284755250120611302559342900540155834822938915623235276, 19323499523068246353604256948937214304026062895362699699699828462410555730397, 20805148564023499964198050869066382519440651355534198138904557570979576439400, 667560223069330502241381992651659266584386740595030223650793730414961433006--signature required
string '{"x":"….","y":"…"}'
Signature to be verified
--keystore optional
file path
The path to the keystore file used for signing the transaction.
--keystore-password optional
file path
The path to the file containing the keystore password.
--silent, --s, --no-prompt optional
flag
Run in non-interactive mode using .env and provided arguments, without user prompts.
-h, --help optional
flag
Display help information for this command.
Last updated