Keys

This step collects your ECDSA and BLS keys for whitelisting and for registration into Fermah AVS through EigenLayer smart contracts, respectively.

We are going to need an ECDSA key imported, and a BLS key generated.

A passphrase will be prompted from the user to securely store the keys. Keys are saved using a user-provided name, which will be used to refer to them in other CLI commands.

ECDSA Keypair

Import a private key matching the ECDSA key provided in the form, using either a path to an existing private key file, or the hex-encoded private key string itself, 0x hex prefix is optional.

NAME=ecdsa.operator
KEY=hex_ecdsa_private_key

fermah-operator key import --key-type ecdsa --name $NAME --private-key $KEY

We are temporarily not able to import EigenLayer's ECDSA keyfile format, this feature is under development.

BLS Keypair

Operators should generate a unique BLS key for every AVS they onboard to. You can generate a key using our CLI by running this command:

NAME=bls.operator

fermah-operator key gen --name $NAME --key-type bls

For both ECDSA and BLS, output will include the public key. This will be used as the identifier to to get you whitelisted. Private key will be saved to ~/.fermah/keys/name.jsonaccording to the Web3 Secret Storage Definition.

Reference

Applies to both ECDSA and BLS

Argument	Description	Required
--name	unique name for key	yes
--key-type	ecdsa or bls	yes
--password-stdin	read password from stdin	no
--no-pw-confirm	do not ask for password confirmation	no
--no-password	force no password for keystore	no

Whitelist Keys

Please provide the ECDSA and BLS public keys through our form atFermah AVS - Operator Application Form - For Devnet on Holesky. We will notify you once your key has been registered, upon which you can continue with the remaining steps.