Skip to content
Crypto Record

Crypto news across every chain

2026-11-16 16:59 UTC34945a

How Restaking Operators Choose AVSs to Support: The Trade-Offs

How do restaking operators choose which AVSs to support? They weigh service demands, slashing exposure and operating costs against their capacity and risk limits.

Crypto Record Editorial3 min read

How Restaking Operators Choose AVSs to Support: The Trade-Offs

Restaking operators choose which AVSs to support by matching each service’s technical demands, duties, slashing terms and potential economics to their capabilities and risk limits. Each AVS asks operators to do specific work, and its rules can expose delegated stake to service-specific penalties.

Take an operator considering an oracle AVS, a service that asks operators to submit data reliably. In EigenLayer, an operator can opt into services whose requirements fit its setup. eigen layer as Layer 2 or restaking describes the protocol’s role in that arrangement.

What would make an oracle AVS a good fit?

An oracle AVS is a good fit when the operator can run its software and meet the service’s duties with the hardware, staff and monitoring it already has or can reasonably provide. The operator first checks the AVS’s technical requirements: what software to install, what data work to perform, and how reliably it must respond.

Suppose the operator already runs systems that can collect and submit the oracle’s data, and its team can monitor them. Supporting this AVS may mean adding a service and watching its performance, rather than building a new setup from scratch. The operator still needs to check that it can handle the workload and keep the service running as required.

This is where operating fit changes the economics. A service with attractive headline rewards can cost more to support if it requires new software, extra hardware, more staff attention or unfamiliar monitoring. An AVS that fits the operator’s existing setup may leave more room between its expected fees and its running costs. The operator can use that comparison to judge whether the service is worth the work, rather than treating the advertised reward as the whole return.

How do operators weigh rewards against slashing exposure?

Operators weigh an AVS’s expected fees or rewards against its operating costs, commission arrangements and the stake exposed under its slashing rules. Before opting in, they review both the work the AVS requires and the conditions under which it can penalize an operator.

Delegation makes that review matter to restakers, too. Restakers may delegate stake to an operator, and delegated stake can be exposed to slashing for an AVS that operator supports. So the operator considers how much stake would be subject to the service’s penalties and whether that exposure fits its risk limits. Potential rewards are only one part of the decision.

Now change the oracle case: suppose the AVS requires a new monitoring system and round-the-clock staff coverage. The operator’s costs rise, and the service may no longer fit its capacity or risk limits, even if its potential fees stay the same. The same test still holds: compare the AVS’s duties, costs, rewards and slashing conditions with the operator’s resources and limits. There is no single protocol-wide ranking that chooses AVSs for every operator.

Related

What does an AVS do in EigenLayer?

An AVS provides a service that operators can opt into supporting. It sets the work operators must perform and may define penalties for failing to meet its obligations.

What risks do EigenLayer operators take?

Operators take on the technical and operating demands of each AVS they support, along with potential slashing exposure under that service’s rules. They can decide whether to opt in after reviewing those demands and conditions.

For an operator assessing an AVS, the next step is to read its requirements and penalty conditions, then decide whether the work, costs and exposed stake fit its setup and risk limits.