Bridge binds message to srcChainId

Compound V3 (Comet)'s assessment for RD-F-152 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

Canonical L2 bridges bind messages to source chain by design. Compound inherits this protection. Local Timelock queuedTransactions mapping provides secondary replay barrier.

Detail #

Arbitrum Inbox, OP Stack CrossDomainMessenger, and Polygon fx-portal all enforce chain-ID binding on messages. Cross-chain replay is prevented at the bridge layer before BridgeReceiver processes the message.

Sources #

Audit
OpenZeppelin Bridge Receiver Audit — governance relay architectureOpenZeppelin Compound Polygon Bridge Receiver Auditretrieved 2026-04-27

Methodology #

Determine whether the bridge message struct includes `srcChainId` and the verifier enforces per-chain separation.

See the full factor methodology and distribution across all protocols →

rubric_version v1.7.0 protocol compound-v3 factor RD-F-152 score green collected_at 2026-04-28 00:20:50