Registration and Aliasing

This page documents the operator registration process for EigenLayer AVS and the key aliasing mechanism.

This page documents the operator registration process for EigenLayer AVS and the key aliasing mechanism. It explains how operators register with the AVS system and manage alias keys to separate their operational and staking identities. For information about the operator worker loop and task execution, see Worker Loop. For information about trigger mechanisms, see Trigger Engines.

1. Overview#

In the EigenLayer-AVS system, operators must register with the AVS Registry Coordinator contract to participate in the network. Operators also have the option to declare alias keys, which provide a separation between the staking address and operational address, enhancing security by allowing operators to keep their main key with staked ETH in cold storage while using alias keys for day-to-day operations.

Diagram: Registration and Aliasing System Overview

Sources:

2. Operator Registration#

Registration is the process by which an operator joins the EigenLayer AVS system. This involves registering the operator's cryptographic keys and information with the AVS Registry Coordinator contract.

2.1 Registration Process#

The registration process connects an operator's address to the AVS system, enabling the operator to participate in consensus and task execution. The process requires both ECDSA and BLS keys to establish the operator's identity within the system.

Diagram: Operator Registration Process Flow

The main registration function is RegisterOperatorWithAvs() in the operator package, which:

  1. Creates a random salt for the registration signature
  2. Calculates an expiry time for the signature
  3. Registers the operator with the AVS Registry Coordinator
  4. Associates the operator with specific quorums (currently hardcoded to quorum 0)

Sources:

2.2 Deregistration Process#

Operators can leave the AVS system through the deregistration process. This removes the operator from active participation in the quorums they were part of.

The deregistration is handled by DeregisterOperatorFromAvs() function, which:

  1. Identifies the quorum numbers the operator is registered with
  2. Calls the AVS Writer's DeregisterOperator method
  3. Submits a transaction to update the Registry Coordinator contract

Sources:

2.3 Checking Operator Status#

Operators can verify their registration status using the ReportOperatorStatus() function, which returns information including:

  • ECDSA address
  • Whether BLS public keys are registered
  • G1 and G2 public keys (BLS keys)
  • Whether the operator is registered with the AVS
  • Operator ID assigned by the system

Sources:

3. Alias Key Management#

Alias keys allow operators to use separate addresses for daily operations versus their main staking/registration address. This provides enhanced security by allowing operators to keep their main private key (with staked ETH) in cold storage.

3.1 Creating or Importing an Alias Key#

The first step in using an alias is to create or import an alias key pair. This is handled by the CreateOrImportAliasKey() function, which either generates a new ECDSA key pair or imports an existing private key.

Diagram: Alias Key Creation/Import Process

The generated or imported key is encrypted with a password and stored in a file specified by the user.

Sources:

3.2 Declaring an Alias#

After creating an alias key, operators must declare it to associate it with their main operator address. This is done through the DeclareAlias() function, which:

  1. Loads the alias key from file
  2. Creates a transaction to the APConfig contract's DeclareAlias method
  3. Sends the transaction to the blockchain

Diagram: Alias Declaration Process

The declaration links the alias address (derived from the alias key's public key) to the operator's main address in the APConfig contract.

Sources:

3.3 Removing an Alias#

Operators can remove their alias association using the RemoveAlias() function, which:

  1. Verifies that the operator is currently using an alias
  2. Creates a transaction to the APConfig contract's Undeclare method
  3. Sends the transaction to the blockchain

Sources:

4. Smart Contract Integration#

The registration and aliasing mechanisms integrate with the EigenLayer smart contracts and the AVS-specific contracts.

4.1 Registry Coordinator Integration#

The Registry Coordinator contract serves as the main entry point for operator registration. It coordinates with:

  • BLS APK Registry: Stores the BLS public keys for operators
  • Index Registry: Maintains mapping of operators to quorum indices
  • Stake Registry: Tracks operator stakes

This integration enables the AVS to verify operator identity and stake when processing tasks.

4.2 APConfig Contract Integration#

The APConfig contract manages alias declarations through:

  • DeclareAlias: Associates an alias address with an operator's main address
  • Undeclare: Removes the association between an alias and operator

The contract is deployed on multiple networks with the same address (0x5327443cF04e6E8c3B86BDBbfaE16fcB965b7564) to maintain consistency across deployments.

Diagram: Contract Integration for Registration and Aliasing

Sources:

5. Security Considerations#

Using alias keys provides several security benefits:

  1. Key Separation: Operators can keep their main address (with staked ETH) in cold storage while using alias keys for daily operations
  2. Risk Mitigation: If an alias key is compromised, the operator's main funds and stake remain secure
  3. Operational Flexibility: Operators can rotate alias keys without affecting their registration or stake

However, operators should ensure proper key management practices:

  • Use strong passwords for encrypting alias key files
  • Keep backup copies of key files in secure locations
  • Regularly verify the status of their registration and aliases

Sources:

6. Summary#

The registration and aliasing system in EigenLayer-AVS provides a robust framework for operator identity management:

  1. Registration establishes the operator's identity in the AVS system via the Registry Coordinator contract
  2. Alias keys enable operators to separate their staking address from their operational address
  3. The APConfig contract manages the association between operator addresses and alias addresses
  4. This system enhances security while providing operational flexibility for AVS operators

Operators should follow the documented procedures for registration and alias management to properly configure their participation in the EigenLayer-AVS system.

Feature this wiki to auto refresh weekly

Try DeepWiki on your private codebase with Devin