Restaking and EigenLayer: The Next Infrastructure Layer

In traditional staking, your ETH secures the Ethereum network and only the Ethereum network. Restaking allows you to opt in to securing additional protocols—called Actively Validated Services (AVS)—using the same staked ETH. In return, you earn additional rewards from each AVS you support.

The economic logic is compelling: instead of earning 3.5% from Ethereum staking alone, a validator running three AVS might earn 3.5% + 1% + 0.5% + 0.8% = 5.8% on the same capital. The marginal cost of running an additional AVS is primarily computational, not capital.

As of early 2026, the AVS ecosystem has grown to include:

01node operates as an AVS operator on EigenLayer, supporting over 14 actively validated services. Each AVS requires its own node software, monitoring, and upgrade management—effectively multiplying the operational complexity of validator operations.

Restaking is not free compute. Each AVS runs its own node process with specific hardware requirements. A validator operator running 10 AVS alongside their Ethereum beacon chain validator needs:

- Significantly more CPU cores (each AVS process consumes 2–8 cores) - More RAM (some AVS require dedicated memory pools) - Additional storage for AVS-specific state - More network bandwidth for AVS-specific peer-to-peer communication

This is where bare metal infrastructure provides a decisive advantage. Cloud operators pay per-resource premiums that make multi-AVS operations prohibitively expensive. On owned hardware, the marginal cost of running an additional AVS is essentially the electricity to power the extra compute—a fraction of cloud pricing.

Restaking introduces compounded slashing risk. If an AVS detects misbehavior from an operator, it can slash not just the AVS-specific stake, but the underlying ETH. This means a bug in an AVS’s slashing logic—or even a misconfiguration—could affect your Ethereum staking position.

This risk is real and non-trivial. Responsible operators must: - Carefully evaluate each AVS’s slashing conditions before opting in - Maintain isolated infrastructure for each AVS to prevent cross-contamination - Monitor each AVS with the same rigor as the base Ethereum validator - Set conservative exposure limits per AVS relative to total staked ETH

Our approach to restaking follows the same principles as our base validator operations: owned hardware, defense in depth, and conservative risk management.

Each AVS runs on isolated infrastructure with its own monitoring and alerting. We evaluate every AVS against our five-dimensional network selection criteria before opting in. And we maintain strict exposure limits—no single AVS receives more than 15% of our total restaking allocation.

The result: additional yield for our delegators without compromising the operational integrity that defines 01node’s infrastructure.

Restaking is still in its early innings. As the AVS ecosystem matures, we expect to see:

- Standardized AVS interfaces that reduce operator integration overhead - Insurance protocols that hedge against AVS-specific slashing risk - Delegation marketplaces where restakers can choose specific AVS portfolios - Cross-chain restaking extending beyond Ethereum to other PoS networks

For validator operators, restaking represents the most significant expansion of scope since the transition from Proof of Work to Proof of Stake. It demands more infrastructure, more monitoring, and more operational expertise. At 01node, we see this as an opportunity—because operational excellence at scale is exactly what bare metal infrastructure was built for.