Slashing Reserve

How it works

A slashing reserve is a dedicated capital pool covering validator penalty losses before they reach depositor principal. Without one, any slashing event directly cuts the net asset value of the LST or LRT, passing the loss straight to token holders who may not have consented to bearing it. The reserve acts as a first-loss tranche, absorbing penalties up to its capacity and only exposing depositors above it.

Reserves are funded a few ways. A mandatory operator bond requires each operator to post collateral above the protocol minimum, at risk before depositor funds. A treasury-funded reserve draws on protocol revenue to hold a target ratio against total value locked. Hybrids combine both: bonds cover small isolated events, the treasury covers correlated or catastrophic ones.

How it is calculated

Sizing means modeling the realistic loss distribution, not just the expected case. For a single-service LST on Ethereum, historical data is the basis: isolated events have been infrequent and small, while the theoretical maximum is large but constrained by Ethereum's correlation penalty design. Size to a plausible severe scenario, not the median incident.

For restaking it gets harder. Each AVS adds an independent vector. If a position is exposed to four AVSs and a correlated failure triggers penalties on all four, the loss per unit of collateral can be a multiple of any single AVS's conditions. The reserve must be sized against the sum of concurrent scenarios, weighted by the chance they fire together, which requires explicit correlation modeling.

Common mistake

The usual failures are launching with no reserve at all, or sizing it against a single-service base case and then expanding AVS exposure without resizing. Either way the backstop falls behind the risk while the headline metrics keep rising, which is the most dangerous version because nothing on the dashboard signals the problem.