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.
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:
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
.json
according to the Web3 Secret Storage Definition.
Reference
Applies to both ECDSA and BLS
Argument | Description | Required |
---|---|---|
| unique name for key | yes |
| ecdsa or bls | yes |
| read password from stdin | no |
| do not ask for password confirmation | no |
| 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.
Last updated