LogoLogo
DevnetSeek
  • Introduction
    • Overview
    • Why Fermah?
    • Supported Proof Systems
    • Key Terms and Concepts
    • On Zero-Knowledge Proofs
  • Network
    • Components
  • Testnet
    • Overview
    • For Prover Nodes
      • Installation
      • Provers
      • Configuration
      • Machine Secret
      • Registration
      • Telemetry
      • Starting a Node
  • Resources
    • GPG
    • Support
    • Website
    • Github
    • X
    • Discord
Powered by GitBook
LogoLogo

© 2025 Fermah

On this page
  • Importing a Private Key
  • Using existing Private Key
  • Generating and Adding a Machine Secret Key to the Configuration
  • Whitelist Keys

Was this helpful?

  1. Testnet
  2. For Prover Nodes

Machine Secret

Setting up authentication in prover nodes.

PreviousConfigurationNextRegistration

Last updated 8 days ago

Was this helpful?

Our prover nodes need a machine secret generated and signed using an imported ECDSA key.

Importing a Private Key

To import an ECDSA private key, use the hex-encoded private key string itself in the OPERATOR_PRIVATE_KEY variable. The 0x hex prefix is optional.

KEY_NAME=prover-node
OPERATOR_PRIVATE_KEY=0x**********************************

prover-node store-key -k $KEY_NAME \
              -p $OPERATOR_PRIVATE_KEY

Using existing Private Key

If your current private key file follows the , you may place the file at ~/.fermah/keys/name.json instead of importing it.

Generating and Adding a Machine Secret Key to the Configuration

This command generates a Machine Secret Key from the imported ECDSA key and updates the configuration file accordingly.

prover-node gen-machine-secret

Whitelist Keys

Please provide the Machine Secret public keys through our form at . We will notify you once your key has been registered, upon which you can continue with the remaining steps.

Web3 Secret Storage Definition
Fermah AVS - Operator Application Form - For Testnet