The short answerEigenpie issues a distinct token for each liquid staking asset it accepts, so a problem with one LST cannot contaminate holders of another. The structure is sound and the consequence is severe liquidity fragmentation: each token trades thinly, making exit before the redemption queue expensive.
Best forIsolated per-LST restaking positions
Added slashing riskweight 25%
6.5avg 6.6
Contract securityweight 20%
6.5avg 7.0
Exit liquidityweight 20%
5.0avg 6.0
Operator transparencyweight 20%
6.5avg 7.1
Feesweight 15%
7.5avg 7.8
this service category average across 15Score = Σ mark × weight. Usable, but there are better options for most people. Methodology.
| Criterion | Mark | What we found | Source | Checked |
|---|
| Added slashing risk | 6.5 | not sourced yet | not sourced yet | — |
| Contract security | 6.5 | not sourced yet | not sourced yet | — |
| Exit liquidity | 5.0 | not sourced yet | not sourced yet | — |
| Operator transparency | 6.5 | not sourced yet | not sourced yet | — |
| Fees | 7.5 | not sourced yet | not sourced yet | — |
What we liked, and what fell short
Liked- Per-asset vaults prevent one LST's problems contaminating another
- Backed by the established Magpie ecosystem
- Straightforward deposit mechanics
Fell short- Each isolated token has minimal secondary liquidity
- Short operating history and a modest audit trail
Why the marks landed where they did
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.
FAQ
Why does Eigenpie issue a separate token per LST?+
To isolate risk: a problem with one liquid staking token affects only holders of that vault's restaked token, not everyone in a shared pool.
What is the downside of isolation?+
Liquidity fragments across many small tokens, so none has meaningful secondary depth and exits typically require the redemption queue.
Who is behind Eigenpie?+
The Magpie ecosystem, which operates several DeFi products. Eigenpie launched in 2024 and has no incidents on record.
What does Eigenpie charge?+
Around 10% of rewards, in line with the category norm.
