package churner

Get desktop application:
View/edit binary Protocol Buffers messages

The Churner is a service that handles churn requests from new operators trying to join the EigenDA network. When the EigenDA network reaches the maximum number of operators, any new operator trying to join will have to make a churn request to this Churner, which acts as the sole decision maker to decide whether this new operator could join, and if so, which existing operator will be churned out (so the max number of operators won't be exceeded). The max number of operators, as well as the rules to make churn decisions, are defined onchain, see details in OperatorSetParam at: https://github.com/Layr-Labs/eigenlayer-middleware/blob/master/src/interfaces/IBLSRegistryCoordinatorWithIndices.sol#L24.

• rpc Churn (ChurnRequest, ChurnReply)

  churner.proto:17

  message ChurnRequest

  churner.proto:20

  • string operator_address = 1

    The Ethereum address (in hex like "0x123abcdef...") of the operator.

  • bytes operator_to_register_pubkey_g1 = 2

    The operator making the churn request.

  • bytes operator_to_register_pubkey_g2 = 3

  • bytes operator_request_signature = 4

    The operator's BLS signature signed on the keccak256 hash of concat("ChurnRequest", operator address, g1, g2, salt).

  • bytes salt = 5

    The salt used as part of the message to sign on for operator_request_signature.

  • repeated uint32 quorum_ids = 6

    The quorums to register for. Note: - If any of the quorum here has already been registered, this entire request will fail to proceed. - If any of the quorum fails to register, this entire request will fail. - Regardless of whether the specified quorums are full or not, the Churner will return parameters for all quorums specified here. The smart contract will determine whether it needs to churn out existing operators based on whether the quorums have available space. The IDs must be in range [0, 254].

  message ChurnReply

  churner.proto:44

  • optional SignatureWithSaltAndExpiry signature_with_salt_and_expiry = 1

    The signature signed by the Churner.

  • repeated OperatorToChurn operators_to_churn = 2

    A list of existing operators that get churned out. This list will contain all quorums specified in the ChurnRequest even if some quorums may not have any churned out operators. If a quorum has available space, OperatorToChurn object will contain the quorum ID and empty operator and pubkey. The smart contract should only churn out the operators for quorums that are full. For example, if the ChurnRequest specifies quorums 0 and 1 where quorum 0 is full and quorum 1 has available space, the ChurnReply will contain two OperatorToChurn objects with the respective quorums. OperatorToChurn for quorum 0 will contain the operator to churn out and OperatorToChurn for quorum 1 will contain empty operator (zero address) and pubkey. The smart contract should only churn out the operators for quorum 0 because quorum 1 has available space without having any operators churned. Note: it's possible an operator gets churned out just for one or more quorums (rather than entirely churned out for all quorums).

This describes an operator to churn out for a quorum.

Used in: ChurnReply

• uint32 quorum_id = 1

  The ID of the quorum of the operator to churn out.

• bytes operator = 2

  The address of the operator.

• bytes pubkey = 3

  BLS pubkey (G1 point) of the operator.

Used in: ChurnReply

• bytes signature = 1

  Churner's signature on the Operator's attributes.

• bytes salt = 2

  Salt is the keccak256 hash of concat("churn", time.Now(), operatorToChurn's OperatorID, Churner's ECDSA private key)

• int64 expiry = 3

  When this churn decision will expire.