Starting a Node

Starting an Operator Node.

Please make sure you are running Telemetry

Start

When running the following command, make sure you replace:

• OPERATOR with your operator name, in lowercase

• RPC with a Holesky RPC URL

OPERATOR=operatorname
NETWORK=dev
ECDSA=ecdsa.operator
RPC=https://mainnet.infura.io/v3/API-KEY

fermah-operator start \
--network $NETWORK \
--profile $OPERATOR \
--key $ECDSA \
--chain-rpc $RPC \
--telemetry otlp

This command will connect you to our network using the provided key and listen for Proof Requests on port 8888 by default.

Daemonization

Systemd

If you already run other systemd services, there are no specifics for Fermah AVS binary. Keep in mind that you can use logrotate for logs:

/var/log/operator.log {
    su root adm
    daily
    missingok
    rotate 30
    maxsize 1G
    compress
    notifempty
    postrotate
        /usr/lib/rsyslog/rsyslog-rotate
    endscript
}

Additionally, you may set the absolute path to a custom Fermah config folder using FERMAH_CONFIG env var.

Docker

Docker setup is under development.

Kubernetes

Kubernetes helm chart is under development.

Headless Password

If you are using a password for your ECDSA keystore file, you can start the process headless with no prompts, by using the env var FERMAH_KEYSTORE_PW_FILE and setting it to the absolute path to the file containing the password.

Keep in mind these security considerations:

• Set password file permissions to 600

• Keystore file should already be set to perms 600

• Run the systemd service with a non root user and owning both keystore file and password file