Bridge tracks nonce-consumed mapping

Chainlink CCIP's assessment for RD-F-153 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

CCIP uses sequence numbers per source chain (NonceManager contract). OffRamp checks minSeqNr/maxSeqNr intervals; rejects duplicate sequence ranges. Duplicate root rejection: 'we disallow duplicate roots as that would reset the timestamp'. Execution state tracked per message. Three-layer replay protection: (1) root timestamp deduplication, (2) sequence number range enforcement, (3) per-message execution state.

Sources #

GitHub
Chainlink CCIP OffRamp.sol - replay protectionOffRamp.sol commit function: 'we disallow duplicate roots as that would reset the timestamp'; minSeqNr/maxSeqNr staleness checks; s_roots mapping acts as replay guardretrieved 2026-05-16

Methodology #

Determine whether the bridge inbox maintains a nonce-consumed mapping and rejects replay of used nonces.

See the full factor methodology and distribution across all protocols →

rubric_version v1.7.0 protocol chainlink-ccip factor RD-F-153 score green collected_at 2026-05-16 01:55:09