Bridge tracks nonce-consumed mapping
Maple Finance'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 assigns unique messageId to each message. MapleCCIPReceiver maintains getMessage mapping tracking processed message IDs and FailedMessage records for replay resistance. LayerZero V2 uses ordered nonce delivery at endpoint layer.
Detail #
MapleCCIPReceiver source: getMessage mapping tracks message IDs. FailedMessage records with error codes provide deduplication. CCIP messageId uniqueness is guaranteed at the protocol layer. LayerZero V2 endpoint maintains ordered nonce delivery per pathway. Replay protection is present for both bridge surfaces.
Sources #
- EtherscanMaple CCIP Receiver — replay protectionMapleCCIPReceiver impl — getMessage mapping and FailedMessageretrieved 2026-04-27
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 →