Bridge rate-limiter / chain-pause as positive mitigant
Yearn Finance's assessment for RD-F-185 — scored not_applicable on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Yearn Finance is not a bridge operator (has_bridge_surface=false, is_a_bridge=false per briefing §7 and profile §7). Cat 10 entirely not applicable. Katana deployment is a native per-chain vault instance, not a bridge surface. F185 (bridge rate-limiter/chain-pause) not applicable by architecture.
Sources #
- Curator noteYearn Finance bridge surface assessment — not applicablePhase 2 briefing §7: has_bridge_surface=false, is_a_bridge=false; profile §7: 'Yearn does not operate a cross-chain message relay, bridge endpoint, or canonical bridge contract'retrieved 2026-05-16
Methodology #
Determine whether the bridge implements a per-window outflow rate-limiter (and at what cap), and whether the protocol team can trigger a chain-level or validator-set emergency pause.
See the full factor methodology and distribution across all protocols →
rubric_version v1.7.0 protocol yearn-finance factor RD-F-185 score not_applicable collected_at 2026-05-16 08:34:32