Lyrasing - pre-launch
Restaking-native money market.
LRTs as first-class collateral. LTV derived from per-LRT AVS exposure - not an opaque ETH-derivative peg. Slashing covered by a protocol-funded insurance pool.
“Launch app” is a placeholder. Wallet flow lands once contracts ship.
Why Lyrasing
Restaking changes the math of collateral.
LRTs carry the slashing exposure of their full operator set. A money market that treats them as plain ETH ignores the risk surface that actually drives losses.
LRT collateral, first-class
eETH, ezETH, rsETH, pufETH — each LRT is its own market with its own risk surface, not folded into a generic ETH-derivative bucket.
ReadLTV from the operator set
LTV is derived from real AVS exposure of the deposited LRT. New high-risk AVS in the operator set tightens the next loop iteration automatically — no governance proposal.
ReadInsurance pool, by construction
Borrower fees and a slice of supply yield route into a per-LRT insurance sub-account. Confirmed slashing drains the pool before supplier principal.
ReadBounded leverage looping
Recursive borrow → swap → re-supply loops capped by the same AVS-derived LTV. ~3.33× theoretical ceiling at a 70% LTV floor, lower under high-risk AVS composition.
ReadPublic parameters
Pool size, funding rate, drawdown ledger, wind-down triggers — declared up front, visible on-chain, no implied emergency carve-outs.
ReadGlossary, comparisons
AVS, LRT, slashing, restaking — terms cross-checked against EigenLayer and Symbiotic source docs. Side-by-side vs Aave / Morpho / Symbiotic / EigenLayer.
Read04 — Comparisons
How we compare
Restaking-native collateral with AVS-aware LTV, built-in leverage looping, and a slashing-insurance layer — absent from existing money markets and restaking protocols alike.
Per-LRT AVS composition → dynamic LTV with insurance backstop
No AVS layer — flat ETH-derivative price treatment
Per-market configuration — no protocol-level AVS risk model
Network opt-in per operator · vault-level slashing bounds
AVS opt-in per operator · on-chain slashing conditions per AVS
Data reflects protocol design at publication. Verify against latest documentation before relying on comparisons.
Resources
For builders.
Docs
Concept overview, AVS-risk methodology, slashing-insurance design, glossary.
Comparisons
Side-by-side vs Aave, Morpho, Symbiotic, EigenLayer. Where Lyrasing differs.
Roadmap
Phases, exit criteria, what ships when. Contracts post-launch in a separate repository.
Contributors
What to expect from a pre-launch contributor pipeline.
Get early-builder access.
Waitlist for the launch cohort. Documentation, AVS-risk methodology, and audit-grade specs land first.
Join the waitlist