Eigen layer AVS types set integration and slashing limits

EigenLayer lets an AVS secure services with operators’ restaked stake, while its contracts limit slashing to an operator’s active allocation to that service’s set. The eigen layer model is not one service type: each AVS defines work for operators, rules for checking it and any economic penalty for failing.

What types of AVS can eigen layer secure?

EigenLayer’s materials describe services including data availability, oracles, bridges, rollups and compute networks. These are practical categories, not separate security guarantees: a data availability service checks that data can be retrieved, while an oracle reports external information and a bridge verifies cross-chain messages.

The work determines what operators must run and what counts as a fault. The label eigen layer is useful shorthand for the shared staking layer; it does not mean every AVS asks operators to perform the same task. A service that needs continuous data delivery has different operating demands from one that checks discrete proofs.

How does an AVS integrate with operators?

EigenLayer’s AllocationManager documentation describes the current operator set model: an AVS creates one or more sets, selects the strategies each set can use, and operators register and allocate stake to them. Operators also run the service’s off-chain software; the contracts handle registration, allocations and, where configured, slashing.

For a service builder, the integration choice starts with the task and evidence. Specify what operators must do, how the service detects a violation, which operators and stake are eligible, and how rewards or penalties follow. Separate operator sets can define different participation requirements and risk exposure for one AVS.

What limits EigenLayer slashing?

EigenLayer’s contracts make slashing opt-in at the operator-set level. An operator must register for the set and have a nonzero active allocation in a strategy included by that set; a service cannot slash stake merely because it exists in EigenLayer.

• Slashing applies to the operator’s allocation for the relevant set, not automatically to all restaked stake.
• Unique stake allocation prevents the same slashable amount from backing multiple operator sets at once.
• Reducing a slashable allocation has a delay, so stake stays exposed during the exit window.
• The AVS needs an authorized slasher and a contract-defined basis for the penalty.

EigenLayer’s AllocationManager documentation lists a 14-day mainnet deallocation delay, while allocation changes have a separate 17.5-day configuration delay. These are protocol timing limits, not a cap on the percentage an AVS may slash from an eligible allocation; each service’s rules and the operator’s allocation determine its exposure.

For operators and delegators, the practical next step is to check the operator’s active sets, strategies and allocation before choosing where to stake. Which AVSs will adopt slashing, and how each will define faults and penalties, remains service-specific.