FAQ

Can an operator's "Signing Key" be the same key used for registration?

Yes. The "Signing Key" can be the same as the "Delegate" key that you used for registering with the shared security provider.

Are you having any kind of problem with the othentic-cli?

Please make sure to update the othentic-cli version to the latest.

If running one of the example repos, make sure to rebuild the docker images with docker-compose build --no-cache

The tasks are not being submitted. What should I do?

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.

Can not find module 'nest-commander'

sudo docker compose up
WARN[0000] docker-compose.yml: version is obsolete 
[+] Running 2/0
 ✔️ Container infini-route-attestators-public-avs-webapi-1  Created                                                                                                                                     0.0s 
 ✔️ Container infini-route-attestators-public-attester-1    Created                                                                                                                                     0.0s 
Attaching to attester-1, avs-webapi-1
attester-1    | node:internal/modules/cjs/loader:1251
attester-1    |   throw err;
attester-1    |   ^
attester-1    | 
attester-1    | Error: Cannot find module 'nest-commander'
attester-1    | Require stack:
attester-1    | - /usr/local/bin/othentic-cli
attester-1    |     at Module._resolveFilename (node:internal/modules/cjs/loader:1248:15)
attester-1    |     at Module._load (node:internal/modules/cjs/loader:1074:27)
attester-1    |     at TracingChannel.traceSync (node:diagnostics_channel:315:14)
attester-1    |     at wrapModuleLoad (node:internal/modules/cjs/loader:217:24)
attester-1    |     at Module.require (node:internal/modules/cjs/loader:1339:12)
attester-1    |     at require (node:internal/modules/helpers:125:16)
attester-1    |     at Object.<anonymous> (/usr/local/bin/othentic-cli:57:18)
attester-1    |     at webpack_require (/usr/local/bin/othentic-cli:5198:42)
attester-1    |     at Object.<anonymous> (/usr/local/bin/othentic-cli:20:26)
attester-1    |     at webpack_require (/usr/local/bin/othentic-cli:5198:42) {
attester-1    |   code: 'MODULE_NOT_FOUND',
attester-1    |   requireStack: [ '/usr/local/bin/othentic-cli' ]
attester-1    | }
attester-1    | 
attester-1    | Node.js v22.6.0
avs-webapi-1  | Server started on port: 4002
attester-1 exited with code 1

Please avoid using sudo when working with the Othentic CLI. Reinstall the CLI without sudo to ensure proper permissions.

ERR_BUFFER_OUT_OF_BOUNDS('length')

hrow new ERR_BUFFER_OUT_OF_BOUNDS('length');
            ^
RangeError [ERR_BUFFER_OUT_OF_BOUNDS]: "length" is outside of buffer bounds
    at proto.utf8Write (node:internal/buffer:1066:13)
    at p8e.zAo [as fn] (/usr/local/lib/node_modules/@othentic/othentic-cli/dist/othentic-cli:645:866549)
    at Uq.e [as finish] (/usr/local/lib/node_modules/@othentic/othentic-cli/dist/othentic-cli:645:865725)
    at yWo.sendTask (/usr/local/lib/node_modules/@othentic/othentic-cli/dist/othentic-cli:645:1119964)
    at yWo.handleRpcRequest (/usr/local/lib/node_modules/@othentic/othentic-cli/dist/othentic-cli:645:1118981)
    at /usr/local/lib/node_modules/@othentic/othentic-cli/dist/othentic-cli:645:1118528
    at Array.map (<anonymous>)
    at /usr/local/lib/node_modules/@othentic/othentic-cli/dist/othentic-cli:645:1118516
    at O_e.e [as handle_request] (/usr/local/lib/node_modules/@othentic/othentic-cli/dist/othentic-cli:120:874618)
    at f (/usr/local/lib/node_modules/@othentic/othentic-cli/dist/othentic-cli:120:876800) {
  code: 'ERR_BUFFER_OUT_OF_BOUNDS'
}

Node.js v22.7.0

Please make sure to use Node v22.6.0⚠️, via NVM

TypeError: invalid value for Contract target (when running nodes)

TypeError: invalid value for Contract target (argument="target", value=null, code=INVALID_ARGUMENT, version=6.8.1)
    at l$r (/Users/user/.nvm/versions/node/v22.6.0/lib/node_modules/@othentic/othentic-cli/dist/othentic-cli:644:253521)
    at Eye (/Users/user/.nvm/versions/node/v22.6.0/lib/node_modules/@othentic/othentic-cli/dist/othentic-cli:644:253827)
    at mno (/Users/user/.nvm/versions/node/v22.6.0/lib/node_modules/@othentic/othentic-cli/dist/othentic-cli:644:253875)
    at new e (/Users/user/.nvm/versions/node/v22.6.0/lib/node_modules/@othentic/othentic-cli/dist/othentic-cli:644:513082)
    at new kFt (/Users/user/.nvm/versions/node/v22.6.0/lib/node_modules/@othentic/othentic-cli/dist/othentic-cli:644:518004)
    at b$o.setObls (/Users/user/.nvm/versions/node/v22.6.0/lib/node_modules/@othentic/othentic-cli/dist/othentic-cli:647:1905)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async b$o.onModuleInit (/Users/user/.nvm/versions/node/v22.6.0/lib/node_modules/@othentic/othentic-cli/dist/othentic-cli:645:1033488)
    at async Promise.all (index 0)
    at async D6i (/Users/user/.nvm/versions/node/v22.6.0/lib/node_modules/@othentic/othentic-cli/dist/othentic-cli:119:23099) {
  code: 'INVALID_ARGUMENT',
  argument: 'target',
  value: undefined,
  shortMessage: 'invalid value for Contract target'
}

Node.js v22.6.0

This indicates you are not passing the proper --l2-chain flag when running the node.

Operator registration is not working

othentic-cli operator register

Unknown error occurred
ERROR [AvsService] Error: missing revert data (action="estimateGas", data=null, reason=null, transaction={ "data": "0x226...)

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.

Cannot read properties of undefined (reading 'connect')

This error indicates one or more of AVS_GOVERNANCE_ADDRESS or ATTESTATION_CENTER_ADDRESS is missing from your .env file

Error: could not decode result data (value="0x", info={ "method": "obls", "signature": "obls()" }

This error could have several causes:

  1. Your AttestationCenter address is incorrect

  2. You are passing the wrong --l2-chain flag

  3. You are using an L2_RPC in your .env which is pointing to the wrong chain

Error: network does not support ENS

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

Last updated