otcli

Reference documentation for the Othentic CLI tool - otcli

otcli [options] [command]

Options:
  -V, --version      Show othentic-cli version
  -h, --help         display help for command

Commands

  • network: Deploy and manage AVS network

  • operator: Perform actions as AVS Operator

  • wallet: Perform wallet & keys actions


Providing Keys to the CLI

Keys can be provided to the CLI either at runtime via flags or through environment variables.

Using Keystore Files

At Runtime:

otcli [SUB-COMMAND-1] [SUB-COMMAND-2] \
    --keystore <KEYSTORE_PATH> \
    --keystore-password <DECRYPT_PASSWORD>
  • KEYSTORE_PATH: Path to the JSON-formatted Keystore file.

  • DECRYPT_PASSWORD: Password to decrypt the Keystore file. If not supplied, you will be prompted to enter it.

Using Environment Variables:

Set these variables in your .env file:

.env
WALLET_KEYSTORE_PATH=.keystore/your-keystore-file.json
WALLET_KEYSTORE_PASSWORD=your_password
OPERATOR_ADDRESS=0xabc... # Required when using a separate Consensus Key
Using Raw Keys

At Runtime:

otcli [SUB-COMMAND-1] [SUB-COMMAND-2] \
    --private-key <RAW_PRIVATE_KEY>

Using Environment Variables:

Set these variables in your .env file:

.env
PRIVATE_KEY=81da2278784f...
OPERATOR_ADDRESS=0xabc... # Required when using a separate Consensus Key

Browser wallet support

Othentic CLI supports using browser wallets like Metamask, SAFE, wallet connect etc.

  • This feature is particularly useful when using multisig account or scenarios where the private key can not be pasted directly.

  • This feature can be used across all CLI commands seamlessly.

To use this, include the --browser-sign flag when running any CLI command.

For reference, see this guide on deploying an AVS through browser wallet.


Quick Tips

For detailed instructions, examples, and best practices for each command, refer to the corresponding sections in this documentation.

  • Always ensure you are using the latest version of the CLI.

  • Use the --help or -h flag with any command to view usage details.

  • Verify your configurations before deployment to avoid errors.

  • Check your environment variables and .env file contents

Last updated