Comparisons
This section compares Lyrasing’s build-time methodology with adjacent protocol primitives. The goal is to separate what each system owns, which risk surface it exposes, what a future Lyrasing market would consume from that surface, and what Lyrasing would not replace.
The comparisons are not rankings, live integration claims, market recommendations, or launch parameter disclosures. They are a way to test whether Lyrasing’s documentation can describe a downstream restaking-aware money-market policy without borrowing another protocol’s assumptions too loosely.
Comparison axes
| Page | Primitive owned | Risk surface owned | Lyrasing method consumes |
|---|---|---|---|
| Aave | Generalized reserve-based money markets. | Reserve parameters, health factor, liquidation depth, and collateral enablement. | A contrast for LTV, liquidation threshold, and risk-parameter discipline. |
| Morpho | Isolated lending markets and vault-based lending exposure. | Immutable market tuples, LLTV, oracle/IRM choice, vault caps, queues, and manager roles. | A contrast for market isolation, curation, and collateral-policy ownership. |
| Symbiotic | Shared-security vault and network middleware. | Vault epochs, operator/vault/network opt-ins, slashing, VetoSlasher review, and Burner routing. | Direct inputs for AVS exposure, slashing-insurance, and loop-policy review. |
| EigenLayer / EigenCloud | Restaking infrastructure for AVSs and Operator Sets. | Unique Stake allocation, strategy magnitudes, slashable stake, burn or redistribution, and safety delays. | Direct inputs for AVS-risk methodology and LRT collateral review. |
Reading order
Read the comparisons after the methodology sections they depend on:
- AVS-risk methodology, for the exposure, timing, and stale-input vocabulary.
- LRT collateral framework, for candidate collateral review and supported-list boundaries.
- Slashing-insurance design, for the capacity and claim-language used when slash surfaces are mapped to reserves.
- Looping / leverage, for recursive exposure policy.
- The four comparison pages in the order listed above.
Build-time boundary
These docs describe methodology and positioning. They do not describe live product behavior, deployed markets, active integrations, supported collateral, working app flows, oracle implementation, insurance reserves, exact caps, fees, LTVs, liquidation thresholds, or token/governance design.
Every protocol-specific claim in the child pages is backed by current primary documentation. If a source does not support a claim, the comparison phrases it as a Lyrasing review question rather than as an external protocol fact.