Symbiotic

Symbiotic is the reference comparison for shared-security vaults, networks, operators, slashers, and middleware. Lyrasing’s interest is downstream: a future money-market methodology would consume Symbiotic-style risk surfaces when reviewing candidate collateral, insurance capacity, and loop policy. It would not become the shared-security system itself.

Primitive boundary

Axis	Symbiotic	Lyrasing methodology
Primitive owned	Vaults connect collateral to networks through delegation and slashing modules.	A collateral and risk-policy layer that would review what those surfaces mean for a future money market.
Network scope	Networks define services, middleware, operator sets, voting power, thresholds, epochs, and dispute inputs.	AVS-risk methodology would classify the service, timing, operator, and slash exposure as collateral inputs.
Vault scope	Vaults hold one collateral token, track deposits and withdrawals, and expose delegation/slashing policy.	LRT collateral review would ask whether the vault route makes the candidate asset slashable, reusable, delayed, or correlated.
Slashing scope	Slasher or VetoSlasher modules validate and apply penalties against captured guarantees.	Slashing-insurance review would map covered, excluded, delayed, and unresolved surfaces to capacity policy.

Risk inputs Lyrasing would consume

Symbiotic surface	Why it matters downstream
Network, subnetwork, and middleware	Defines which service can request stake, validate work, and raise slash requests.
Operator and vault opt-ins	Determines whether an operator was actually eligible for stake and penalties at a capture timestamp.
Vault epoch duration	Controls withdrawal claim timing and the maximum freshness window for captured slash guarantees.
Withdrawal slashability	Requested withdrawals remain slashable until the relevant epoch boundary, so exits are not instant risk removal.
Capture timestamp	Slashing is checked against a snapshot, not only live state, which matters for collateral timing and insurance claims.
VetoSlasher and resolver posture	Adds a review window and resolver-change timing that can make or break the execution window.
Burner routing	Decides whether penalized collateral is burned, redistributed, routed to a treasury, routed to an insurance pool, or handled by another contract.
Restaking topology	Multi-network or multi-operator reuse can create correlated losses even when each slash is checked against its captured guarantee.

Collateral, insurance, and looping posture

Lyrasing would use Symbiotic-style inputs as follows:

AVS-risk methodology would classify the network, operator, vault, capture, veto, and burner surfaces.
LRT collateral framework would decide whether the candidate collateral has reviewable backing, redemption, liquidity, and slashability evidence.
Slashing-insurance design would ask whether insurance capacity is mapped to the exact network, operator, vault, and capture window.
Looping / leverage would compress recursive exposure if vault epochs, veto windows, withdrawal timing, or burner routing make stressed unwind ambiguous.

This comparison does not claim Lyrasing is a Symbiotic network, vault, middleware, slasher, resolver, Burner, LRT, or replacement. It also does not claim direct integration or supported collateral.

Primary sources

Symbiotic LLMs documentation , for networks, vaults, operators, opt-ins, vault epochs, withdrawal slashability, capture timestamps, VetoSlasher behavior, and Burner routing.