EigenLayer / EigenCloud
EigenLayer is the reference comparison for restaking infrastructure: AVSs, Operator Sets, Unique Stake, strategy magnitudes, slashable stake, safety delays, and burn or redistribution paths. Lyrasing’s position is downstream of that primitive. It would read those surfaces as risk inputs for a future money-market methodology, not operate the restaking system.
Primitive boundary
| Axis | EigenLayer / EigenCloud | Lyrasing methodology |
|---|---|---|
| Primitive owned | Restaking infrastructure where AVSs use Operator Sets and allocated stake for cryptoeconomic security. | A future money-market policy method for LRT collateral, AVS exposure, insurance capacity, and loop posture. |
| Stake accounting | Operators allocate Unique Stake to Operator Sets through strategy magnitudes. | Collateral review would ask how much candidate LRT backing is exposed to each AVS and strategy path. |
| Slashability | AVSs can slash allocated Unique Stake according to AVS-defined conditions after applicable delays. | AVS-risk methodology would classify slash conditions, timing, legibility, and downstream collateral impact. |
| Settlement path | Slashed funds may be burned or redistributed depending on Operator Set configuration and asset eligibility. | Insurance design would decide whether the loss path can be covered, excluded, delayed, or left unresolved. |
EigenLayer surfaces that feed Lyrasing review
| Surface | Lyrasing use |
|---|---|
| AVS | Identifies the service that can create restaking risk for candidate collateral. |
| Operator Set | Defines which operators secure a service task and where slashing risk is localized. |
| Unique Stake | Measures stake made slashable exclusively by a single Operator Set. |
| Strategy magnitude | Shows how an operator’s delegated stake is proportionally allocated across strategies and Operator Sets. |
| Slashable stake | Establishes whether delegated stake can be penalized for an AVS and by how much within the allocated surface. |
| Burn or redistribution | Determines whether a slash destroys value, redirects it, or introduces incentive and key-management considerations. |
| Safety delays | Keeps allocation and deallocation from moving faster than AVS slashing and risk-review windows can absorb. |
Downstream policy posture
Lyrasing would not treat an LRT as generic ETH exposure merely because it is price-correlated with ETH. For EigenLayer-related collateral, the review record would need to answer:
- which AVSs and Operator Sets the backing can be exposed to;
- which strategies and magnitudes determine the slashable proportion;
- whether Unique Stake makes the exposure isolated or whether the LRT wrapper adds correlated exposure elsewhere;
- whether safety delays and deallocation windows fit the liquidation and insurance review path;
- whether slashed funds are burned, redistributed, or otherwise delayed before the money-market shortfall can be measured;
- whether recursive looping should be disabled, compressed, or allowed only after the exposure is observable and current.
This page does not claim Lyrasing is an EigenLayer restaking protocol, operator platform, AVS, Operator Set, EigenCloud product, or integration. It describes the risk-language Lyrasing would need before a future market could reason about EigenLayer-connected collateral.
Primary sources
- EigenLayer key terms , for AVS, Operator Set, magnitude, Unique Stake, strategies, slashing, and withdrawal vocabulary.
- Operator Sets overview , for Operator Set role and opt-in risk.
- Strategies and magnitudes , for allocation accounting.
- Unique Stake , for isolated slashable stake.
- Slashing overview , redistribution , and safety delays , for slashing, burn/redistribution, and timing posture.