Bridge rate-limiter / chain-pause as positive mitigant
Spiko'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 #
Chainlink CCIP used for EVM cross-chain transfers includes inherent CCIP rate-limiting at the OnRamp level. Spiko's own chain-level pause is full-stop (not rate-limited). CCIP rate-limiter is a third-party positive mitigant but not a Spiko-controlled per-chain flow control. Starknet and Stellar cross-chain mechanisms are separate and do not benefit from CCIP rate-limiting.
Sources #
- GovernanceSpiko USTBL Arbitrum STEP-2 applicationArbitrum STEP-2 application describes CCIP cross-chain architecture for USTBLretrieved 2026-05-16
- Spiko Chainlink CCIP integration blogspiko.io/blog/spiko-chainlink-ccip: CCIP used for compliant cross-chain transfers; rate-limiting is a CCIP architecture featureretrieved 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 →