EigenLayer Operator Development
EigenLayer operator — a participant who manages infrastructure for Actively Validated Services. Operators receive restaked ETH from stakers in delegation, register in AVS and perform their validation work. This is a business model: operator provides infrastructure and professional management, receiving share of rewards.
Operator Role in Ecosystem
Stakers trust operators with their restaked ETH. If operator breaches — slashing hits stakers who delegated to them. This means operator reputation is critical.
AVS choose operators based on: size of delegated stake (security), historical reliability (uptime), reputation.
Operator bears responsibility: for correct validation work execution for each AVS they participate in.
Operator Technical Infrastructure
EigenLayer Registration
IDelegationManager.OperatorDetails memory operatorDetails = IDelegationManager.OperatorDetails({
earningsReceiver: operatorAddress,
delegationApprover: address(0), // Permissionless delegation
stakerOptOutWindowBlocks: 50400 // ~7 days
});
delegationManager.registerAsOperator(operatorDetails, metadataURI);
metadataURI points to JSON with public operator info: name, website, commission rate. First step of onboarding.
AVS Operator Node
For each AVS operator participates in — need to run separate node software. Requirements vary for different AVS:
EigenDA operator:
- Requires DA chunks storage
- Participation in distributed storage and retrieval
- Minimum stake: varies by quorum
Generic AVS operator:
- Monitoring on-chain tasks
- Off-chain computations
- BLS signature of results
- Submission to aggregator
Key: BLS Keys
Operators use BLS (Boneh-Lynn-Shacham) cryptography for signing. BLS allows aggregating thousands of signatures into one — key for AVS scalability.
BLS key generation (using EigenLayer CLI):
eigenlayer operator keys create --key-type bls my-bls-key
# Save encrypted keystore + password in secure storage
ECDSA key: for on-chain operations (registration, reward claiming).
HSM recommended: in production — BLS and ECDSA keys in HSM (Hardware Security Module). AWS CloudHSM, YubiHSM, or Hashicorp Vault with HSM backend.
Monitoring and Availability
AVS monitor operator availability. Offline operator = missed tasks = potential slashing (depends on AVS).
Required monitoring:
- Node health: process alive, connected to RPC
- Task processing: successful task execution, no misses
- Aggregator connectivity: connection to aggregator service
- BLS signing: successful signing
Geographic redundancy: for high-availability — primary and backup nodes in different datacenters/regions. Failover on primary unavailability.
Operator Economics
Operator commission: operator retains % of rewards received by their stakers. Typical range 5-15%. Competitive market.
AVS reward streams: each AVS pays operators differently. Need to calculate expected APY considering:
- Size of delegated stake (bigger stake = proportionally more rewards)
- Number of AVS participated in
- Slashing risk of each AVS
Slashing risk calculation: if one AVS slashes operator by 1% — hits all stakers who delegated. Reputation and financial damage.
Operator Business Development
Operators compete for delegated stake. Differentiators:
- Transparent track record: public history of uptime, tasks, slashings (all on-chain)
- Security: public security audit of node infrastructure
- Competitive commission: balance between attractiveness to stakers and own margin
- AVS coverage: wide set of AVS = diversified reward stream for stakers
- Community presence: Discord, Twitter, regular updates
Large operators (P2P.org, Figment, Chorus One) compete with dozens of others. Entry barrier — reliable infrastructure and sufficient bootstrap stake.
Development of operator node software for specific AVS — 2-6 weeks. Launch production operator with monitoring and security — 2-3 months.