FAQ
This page provides debugging assistance and answers to frequently asked questions.
Last updated
This page provides debugging assistance and answers to frequently asked questions.
Last updated
Here are preliminary steps to ensure everything is set up correctly:
Set the L1_RPC and L2_RPC environment variables using private, reliable RPC endpoints to avoid any errors.
Make sure you are using the latest version of Othentic-cli.
Use npm update othentic-cli command or docker-compose build --no-cache to directly update inside docker images.
Make sure all your containers for operators, attesters, execution service and validation service are up and running.
Make sure Operators have enough funds on L1 and staked tokens on Eigen layer as per the funds requirements mentioned in .
Verify that .env file contains all required environment variables, and ensure private keys are not prefixed with 0x .
Run othentic-cli network contracts in the root directory and cross-check all the contract addresses in your .env file.
Verify that attesters, aggregator, and performers are registered as operators with the AVS. Did you run the command for each operator?
Make sure that attesters in the p2p networks have more than 66% of the voting power. You can check the total voting power and individual voting power of the attesters and verify, if necessary, additional funds to help them reach the 66% threshold.
Make sure you are using the correct taskDefinitionId and the corresponding task definitions are created.
In principle, each node can perform any single role or combination of roles. Initially, the AVS developers choose to bootstrap the network with Performers and Aggregators maintained internally, with Attester nodes run by external Operators. Over time, the developer may choose to open up the Performer and Aggregator roles for external Operators as well.
AVS may configure a policy of requirements to be eligible for a specific role; for example, an AVS may choose to grant a Performer role only to nodes with a certain reputation score or ones that staked a certain amount of the AVS native token.
Run othentic-cli network contracts in the avs-samples (root) directory.
To enable debug mode, set DEBUG=* in your .env file or directly in the terminal before running commands. For example:
For tasks to be successfully submitted, operators holding at least 66% of the voting power within the AVS must act as attesters. Please ensure that this condition is met.
Yes. The "Signing Key" can be the same as the "Delegate" key that you used for registering with the shared security provider.
Verify the voting power of the operator using the votingPower method on the Attestation center contract. This message usually appears when the operator has zero voting power. To resolve:
Check Voting Power Sync: If the deposit has been made but voting power is still not reflected, the Voting power sync may not be working. Look for any relevant logs in the Aggregator related to Internal tasks.
Check If Operator is using the correct chain with --l2-chain parameter and the rpc.
Manually Sync Voting Power: If internal tasks are functioning correctly but voting power is still not synced, you may need to manually sync it.
Please avoid using sudo when working with the Othentic CLI. Reinstall the CLI without sudo to ensure proper permissions.
This indicates you are not passing the proper --l2-chain flag when running the node.
The Operator registration function is using cross-chain capabilities. Please make sure that the L1MessageHandler smart contract holds enough funds, for the cross-chain messaging fees.
This error indicates one or more of AVS_GOVERNANCE_ADDRESS or ATTESTATION_CENTER_ADDRESS is missing from your .env file
This error could have several causes:
Your AttestationCenter address is incorrect
You are passing the wrong --l2-chain flag
You are using an L2_RPC in your .env which is pointing to the wrong chain
You've either input an address in an incorrect format, or either of AVS_GOVERNANCE_ADDRESS or ATTESTATION_CENTER_ADDRESS in your .env file are in an incorrect format
You can query the method in the Attestation Center contract using the operator's address. Alternatively, you can use the method in the OBLS contract by querying with the operator ID. The Attestation Center contract is your go-to for details about operators and task definitions.
Use method in the AttestationCenter contract.
Query the method on the OBLS contract. Check each attester's individual voting power and ensure they have 66% of the total voting power.
Create a simple document for operators with instructions like . To make your AVS visible on eigen UI, create a JSON file like this:
Execute the command with above details. Once completed, your AVS will be visible on
Operators can use the to remove themselves from the AVS. When this happens, the operator exits the system, which results in a reduction of the total voting power of the AVS by the amount of that individual operator’ voting power.
Refer to the for this.
You can any flow using the cli by running othentic-cli network pause-flow command. It shows the list of all the flows. You can also use the and contract functions in the AVS governance contract. You can find the exact byte code of the flows by using the .
The Othentic Stack enables developers to create an contract, which includes pre and post-execution hooks. For more details, refer to the .
Refer to the repository on github.
Check Internal Tasks: Ensure that internal tasks are running. If not, start them according to the configuration .
Verify Operator's Deposit: Confirm that the operator has deposited funds into the Eigen strategy as outlined in the of the Quickstart guide.
You can verify this by checking the Operator transactions for deposit Into Strategy transactions, similar to this .
Please make sure to use Node v22.6.0⚠️,