Machine Secret

You can either import an existing ECDSA private key or generate a new Machine Key using the prover-node binary with the appropriate CLI argument.

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.

Importing a Private Key

To import a private key matching the Machine Secret provided in the form, use either a path to an existing private key file or the hex-encoded private key string itself. The 0x hex prefix is optional.

ECDSA=ecdsa.prover-node
fermah-prover-node store-key -c ~/.fermah/config/prover-node.toml \
                                --key-name $ECDSA \
                                --private-key $OPERATOR_PRIVATE_KEY

Generating a Machine Secret

Prover Nodes should generate a unique Machine Secret for every AVS they onboard to. You can generate a key using our CLI by running this command:

NAME=machine.operator  
prover-node gen-machine-secret -c ~/.fermah/config/prover-node.toml

For Machine Secrets, 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

Argument	Description	Required
--key-name	Unique name for key	yes
--private-key	Private key for authentication	yes
-c	Configuration file	yes

Whitelist Keys

Please provide the Machine Secret public keys through our form at Fermah AVS - Operator Application Form - For Testnet on Holesky. We will notify you once your key has been registered, upon which you can continue with the remaining steps.