Pooling several liquid staking tokens into one restaked asset means every holder shares exposure to every underlying LST. Eigenpie's answer is isolation: deposit stETH and receive mstETH, deposit swETH and receive mswETH, with each vault segregated from the others.
Why isolation is right in principle
If one underlying LST suffers a depeg or an exploit, only holders of that specific vault's token are affected. In a pooled design, they all are. For a category built on layered dependencies, containing failure at each layer is the correct instinct.
Why it does not work commercially
Liquidity follows concentration. Splitting deposits across a dozen tokens produces a dozen thin markets, none of which supports a meaningful exit. Holders end up dependent on the redemption queue in exactly the scenario where speed matters, which partially undoes the benefit of isolation.
Backing and record
Part of the Magpie ecosystem, audited, with no incidents since its 2024 launch. That is a short record in a category where nothing is old.
Who should use it
Holders who want their restaking exposure isolated to a specific LST and who intend to hold to redemption rather than trade. Anyone who might need to exit quickly should hold a token with real secondary depth.