Run an Aggregator Node

The Othentic CLI includes built-in node software that AVS Operators run to participate in consensus.

Read More

• Node Operators: Aggregator

• CLI Command Reference

Prerequisites

1. Othentic Node Software installed

2. Registered Operator on EigenLayer and AVS

3. Non zero Voting Power in the AVS Attestation center contract

4. AVS Contract addresses

1

Environment Setup

Create or edit a .env file with your configuration:

• Specify L1_CHAIN and L2_CHAIN variables; See Supported Networks page for chain names

• Specify L1_RPC and L2_RPC, ensure you are using paid, reliable RPC endpoints

• Specify the

  • PRIVATE_KEY: Set this to the Consensus Key

  • OPERATOR_ADDRESS: Set this to the public address of the Controller Key. the public address of the account that has signed up with the shared security protocol - the address to which stakers delegate their staked assets

# Network Configuration
BOOTSTRAP_NODE_ID=12D3KooW... # Bootstrap Peer ID

# Chain Configuration
L1_CHAIN=holesky              # Single L1 chain
L2_CHAIN=amoy,base-sepolia    # Comma-separated L2 chains

# RPC Endpoints
L1_RPC=<HOLESKY_RPC_URL>
L2_RPC=amoy@<AMOY_RPC_URL>,base-sepolia@<BASE_SEPOLIA_RPC_URL> # Comma-separated L2 names@RPCs

# Operator Configuration
OPERATOR_ADDRESS=0x...        # Operator public address
PRIVATE_KEY=0x...             # Consensus Key if separating operator keys

2

Running Aggregator Nodes

Basic Command

otnode run aggregator \
  --json-rpc \
  --l1-chain holesky \
  --l2-chain amoy,base-sepolia \
  --internal-tasks \
  --metrics \
  --delay 1500

Production Command

3

Health Check

When running the node with the --json-rpc flag, the RPC server starts and provides a /healthcheck endpoint to verify its status. For example:

curl -X GET http://localhost:8545/healthcheck

This endpoint should return OK if the node is functioning properly, indicating the RPC service is active. For more detailed monitoring, use Metrics or Logging.

Advanced Features

Custom P2P Messaging

Use --json-rpc.custom-message-enabled flag to enable custom p2p messaging if required by the AVS.

otnode run aggregator \
    --json-rpc \
    --json-rpc.custom-message-enabled

For more information, see the Custom Messaging page.

Operator Status Throttling

Use --status-check-interval to enable throttling mechanism to reduce idle RPC usage, with a default of 5000 milliseconds.

otnode run aggregator \
  --json-rpc \
  --status-check-interval 8000 

The following configurations are mandatory for production AVSs.

Metric Collection & Monitoring

Enable performance metrics collection:

otnode run aggregator \
  --json-rpc \
  --metrics

For more information, see the Metrics and Monitoring page.

Persistent Storage

Enable P2P layer data caching and peerStore usage:

otnode run aggregator \
  --json-rpc \
  --p2p.datadir ./data

For more information, see the Persistent Storage page.

Announced Addresses (NAT/Load Balancer Support)

The announce option in libp2p allows nodes to explicitly define which addresses they advertise to peers, overriding any automatically detected addresses. This is particularly useful when running behind a load balancer or NAT, where the external address needs to be manually set.

Use the following flags to configure how your node builds its announced addresses:

--p2p.public-ip

e.g., --p2p.public-ip 203.0.113.1

--p2p.dns-url

e.g., --p2p.dns-url aggregator.example.com

The node will automatically generate multiaddresses in the following format:

othentic-cli node aggregator \
--json-rpc \
--p2p.public-ip 203.0.113.1 \
--p2p.dns-url aggregator.example.com

---

1. Get Peer ID using following command

othentic-cli node get-id --node-type aggregator

1. Add the Peer ID from above step in the below option

othentic-cli node aggregator \
  --json-rpc \
  --announced-addresses "/dnsaddr/my-node.example.com/tcp/9876/p2p/{Peer ID},/ip4/203.0.113.1/tcp/9876/p2p/{Peer ID}"

Here is a link to the docker file to run an Aggregator node

Next Steps :

Refer to the AVS-specific documentation for detailed instructions on running an Operator.