Everyone would be aware of that, in the default setting, both ECSDA and BLS keys are used to operate an AVS.

As an LRT protocol, we are going to own the ECSDA key and approve the BLS key of the designated operator so that we can control the on-chain "operator" entity. This is to reduce the massive gas cost for rebalancing with multiple EigenPods & enhanced security.

Proposal

1. LRT owns the ECDSA keys and set contract as the on-chain operator entities which can be used without repeating {undelegate, delegate}
   • EtherFiAvsOperator contract: ‣
2. Delegated AVS operators will own the BLS keys, which LRT will approve (by signing with the ECDSA key) to delegate the AVS node operation

Deployed Contracts

EtherFiAvsOperatorsManager: 0x2093Bbb221f1d8C7c932c32ee28Be6dEe4a37A6a

• one EtherFiAvsOperator contract is shown here https://app.eigenlayer.xyz/operator/0xfb487f216ca24162119c0c6ae015d680d7569c2f

Node Operator OnBoarding Process

Pre-requisite

• Delegated node operator
  • BLS key for each AVS (dedicated for ether.fi nodes)
  • EOA or Contract wallet (this is not the EL operator)
• ether.fi
  • ECDSA key

the below two steps are involved:

1. the node operator submits their {BLS key, socket, quorumNumbers}
2. the ether.fi signs on it, submits the signature, and triggers registerOperator on the target AVS contract