Operator onboarding

K3 AVS Operator Configuration Guide

1. Pull the docker image from the Docker Hub.

docker pull k3official/k3-labs-avs-operator:latest

1. Populate the .env file with all the required information. Copy the below template.

L1_RPC= // Your ETH Mainnet RPC
L2_RPC= // Your Base Mainet RPC

OPERATOR_NAME=
OPERATOR_WEBSITE=
OPERATOR_DESCRIPTION=
OPERATOR_LOGO=
OPERATOR_TWITTER=
OPERATOR_EMAIL=

PRIVATE_KEY= // Private key of the address you have assigned to run the AVS on behalf of your Operator. 
OPERATOR_ADDRESS= // Public address of the operator that has the assets staked on EigenLayer and/or Symbiotic. 

L1_CHAIN=1
L2_CHAIN=8453

PINATA_API_KEY=c852ce6f177548614e4f
PINATA_SECRET_API_KEY=acbbdf0edf2650b9740f0f2bd3807c14661099a375144a160a5f324631b7b3e3

ATTESTATION_CENTER_ADDRESS=0xdA68305019701D9346E1960b4187E428D1024906
OTHENTIC_REGISTRY_ADDRESS=0x7e39183cDa5AF65E6A18aF8C3bf0c523127f83bF
AVS_GOVERNANCE_ADDRESS=0x83742C346E9f305dcA94e20915aB49A483d33f3E

IPFS_HOST=https://gateway.pinata.cloud/ipfs/
IPFS_API=https://api.pinata.cloud
IPFS_JWT=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VySW5mb3JtYXRpb24iOnsiaWQiOiJjZmYzYmE2Yy1mMGZmLTQ3MGUtOTc5Ni0xYmI5ZjZhNzlmNDAiLCJlbWFpbCI6Iml2YW4ucmVpZkBrMy1sYWJzLmNvbSIsImVtYWlsX3ZlcmlmaWVkIjp0cnVlLCJwaW5fcG9saWN5Ijp7InJlZ2lvbnMiOlt7ImlkIjoiRlJBMSIsImRlc2lyZWRSZXBsaWNhdGlvbkNvdW50IjoxfSx7ImlkIjoiTllDMSIsImRlc2lyZWRSZXBsaWNhdGlvbkNvdW50IjoxfV0sInZlcnNpb24iOjF9LCJtZmFfZW5hYmxlZCI6ZmFsc2UsInN0YXR1cyI6IkFDVElWRSJ9LCJhdXRoZW50aWNhdGlvblR5cGUiOiJzY29wZWRLZXkiLCJzY29wZWRLZXlLZXkiOiJjODUyY2U2ZjE3NzU0ODYxNGU0ZiIsInNjb3BlZEtleVNlY3JldCI6ImFjYmJkZjBlZGYyNjUwYjk3NDBmMGYyYmQzODA3YzE0NjYxMDk5YTM3NTE0NGExNjBhNWYzMjQ2MzFiN2IzZTMiLCJpYXQiOjE3MTc0MzM5MjZ9.z-wkmQoOb4U7VBDmY6mFQztpIYxafhbif8stNJBir5Q


OTHENTIC_BOOTSTRAP_ID=12D3KooWBNFG1QjuF3UKAKvqhdXcxh9iBmj88cM5eU2EK5Pa91KB
OTHENTIC_BOOTSTRAP_SEED=97a64de0fb18532d4ce56fb35b730aedec993032b533f783b04c9175d465d9bf
OTHENTIC_JSON_RPC_PORT=4001
OTHENTIC_CLIENT_RPC_ADDRESS=https://avs.k3-labs.com
OTHENTIC_CLIENT_IP=104.197.167.201
OTHENTIC_AGGREGATOR_P2P_PORT=9876

PERFORMER_PORT=3000

Warning:

• Ensure no .env variables are encapsulated in double quotes (“ “)

1. Before you can run the docker image, you have to first register yourself as an operator on the K3-Labs AVS. To register to the AVS Please add the following .env variable to your .env file.

   OPERATOR_PRIVATE_KEY=// Private key of the address that has the assets staked on EigenLayer and/or Symbiotic. To register via Eigenlayer run the following command

docker run --env-file .env k3official/k3-labs-avs-operator register eigenlayer

If you wish to register via Symbiotic, run the following command

docker run --env-file .env k3official/k3-labs-avs-operator register symbiotic

⚠️ After running the registration command, please remove the OPERATOR_PRIVATE_KEY variable from your .env file. After running this command, please wait 15-20 minutes minutes for the registration information to propagate from our Layer 1 contracts to our Layer 2 contracts, before running the performer.

1. After step 3 is completed, you are ready to run your K3 node:

docker run --env-file .env --network host -d k3official/k3-labs-avs-operator performer

5. Join our telegram chat and ask to be whitelisted (valid only during testnet phase 1): https://t.me/k3labscoms/436 KEY UPDATE PROCEDURE If you wish to update the address you have assigned to run the AVS on your Operators behalf. Please add in the following .env variables.

OPERATOR_PRIVATE_KEY=// Private key of the address that has assets staked on EigenLayer and/or Symbiotic. PRIVATE_KEY= Private key of the new address you have assigned to run the AVS on behalf of your Operator.

Then proceed to run the following command

docker run --env-file .env k3official/k3-labs-avs-operator update-bls

After running the update command, please remove the OPERATOR_PRIVATE_KEY variable from your .env file. And proceed to restart your AVS node.