Bridge rate-limiter / chain-pause as positive mitigant
stHYPE (Valantis Labs)'s assessment for RD-F-185 — scored yellow on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
No protocol-level rate-limiter on stHYPE deposit/withdrawal outflow. PAUSER_ROLE (held by Safe) can pause but is manual action. Hyperliquid's HyperCore L1 has a chain-level validator halt capability as an upstream structural control, but this is not owned or controllable by Valantis and is not an stHYPE-specific mitigant. No bridge surface means bridge rate-limiter dimension is N/A.
Sources #
- InternalPipeline data cache00-data-cache.json coverage_flags.layerzero_bridge: false — no bridge surface; bridge rate-limiter dimension not applicableretrieved 2026-05-17
- stHYPE Transparency and Risksdocs.valantis.xyz/stakedhype/transparency-and-risks — no rate-limiter documented; pause capability via PAUSER_ROLE notedretrieved 2026-05-17
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 →