Breakage analysis per dependency
QuickSwap's assessment for RD-F-052 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Algebra Protocol core failure: V3 pool interactions halt, V3 LP positions locked; V2 unaffected (independent codebase). Gamma Strategies failure: managed LP positions affected, direct LP positions unaffected. No oracle dependency, so no oracle-failure breakage scenario. Polygon chain halt: all Polygon pools halt (~95.4% TVL). Multi-chain deployments are independent — failure on one chain does not propagate to others. Scored yellow because the Algebra dependency is material but not an oracle-specific breakage.
Sources #
- DocsQuickSwap V3/Algebra integration blog postQuickSwap V3 launch on Algebra: V3 swap routing depends entirely on Algebra CL engineretrieved 2026-05-16
- QuickSwap protocol profile §7 — dependency breakage analysis00-profile.md §7: dependency analysis — Algebra Protocol contracts are primary V3 dependency; Gamma Strategies is optional LP management; no bridge dependencyretrieved 2026-05-16
Methodology #
Produce a short per-dependency text describing which protocol functions halt or degrade and impact severity if each declared dependency fails.
See the full factor methodology and distribution across all protocols →