Skip to main content
Operators on Mainnet are essential to the functioning of the actual decentralized AI infrastructure and are compensated accordingly.

​
Key considerations for Mainnet registration:

  • Full stake requirement must be met
  • Production-grade hardware is necessary
  • Higher uptime and reliability expectations
  • Real economic incentives and rewards
  • Participation in network consensus
  • Reputation building within the ecosystem
Mainnet operators who consistently maintain high-quality service become eligible for additional incentives and may receive priority for new feature testing.

​
Mainnet Registration Steps

​
Capx Cloud Network Dashboard- here.

Capx Cloud is using Othentic stack to host it’s AVS network with Symbiotic.
  • Private Key Wallets
  • Multi-Sig (EIP-1271) Wallets

​
Install the Othentic CLI

  1. Make sure you are running Node version 22.6 and not the latest. The latest node version has issues that are widely know and will cause issues with the running of the othentic-cli
  2. othentic-cli should not be run inside the folder that has the .env file. If you do, it will throw errors.
Installing Othentic CLI with npm:
npm i -g @othentic/othentic-cli
Verify installation by the command:
othentic-cli -v
The outcome should be similar to (version can be higher than the below):
othentic-cli version 1.3.0
CLI installation is completed.

​
Configure ENV Variables

Configure the below env variables :
L1_RPC=https://eth-mainnet.g.alchemy.com/v2/cfbG2jJdddQ1A64OaB3C0uV60A9qM_KD
L2_RPC=https://arb-mainnet.g.alchemy.com/v2/cfbG2jJdddQ1A64OaB3C0uV60A9qM_KD
L1_CHAIN=1
L2_CHAIN=42161
These environment variables are used to configure the network:
  • L1_RPC: The RPC endpoint URL for the Ethereum network
  • L2_RPC: The RPC endpoint URL for the Arbitrum network
  • L1_CHAIN: The chain identifier for the Ethereum network
  • L2_CHAIN: The chain identifier for the Arbitrum network
These variables need to be properly configured before proceeding with the operator registration process.

​
Register as an Operator

The Othentic CLI allows you to easily register your Operators.
Capx Cloud Network address - 0x476Ceb36F6f250297Bb59d45f00bdB053445E9CB
Then, run the following command:
othentic-cli operator register --l1-chain mainnet
This will start up the process of registering as an Operator on both Symbiotic and your Othentic AVS.
  1. Controller key:
    • Used to sign up with the shared security protocol.
    • Represents the account to which restakers delegate their staked assets.
  2. Consensus key:
    • Used by the operator to sign the consensus messages.
Enter your private key: <Operator Private Key / Controller Key>AVS Governance address - 0xAD12e74847d6D1487A6a3A6b75D1f509f3F627e8Rewards Receiver address (default: msg.sender): <Enter to go with default or enter an alternate account address to receive rewards>Choose shared security provider(s) - <Choose Symbiotic>Example :RegistrationIf you Choose to use a different private-key for Consensus :RegistrationYou are now registered and ready to operate.
Please contact Capx Cloud team in-case you need any additional assistance in registrations.

​
Verify Registration

  • NETWORK_ADDRESS - address of the Capx Cloud network.
  • OPERATOR_ADDRESS - an address of the operator to check an opt-in status of

​
Using Etherscan to check:

Registration
  • Put OPERATOR_ADDRESS in who parameter, NETWORK_ADDRESS in where, and click “Query”
  • It should return true
⌘I