Bridge binds message to srcChainId

Maple Finance'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 #

CCIP messages include sourceChainSelector in Client.Any2EVMMessage struct. MapleCCIPReceiver stores chainType per selector via setChainType() and validates source chain. LayerZero messages include srcEid enforced at endpoint layer.

Detail #

MapleCCIPReceiver source: setChainType() function stores chain types per selector. Message processing validates source chain through CCIP message struct decoding. LayerZero V2 includes srcEid in all messages at the endpoint layer. Per-chain message separation is present.

Sources #

Etherscan
Maple CCIP Receiver — source chain validationMapleCCIPReceiver impl — setChainType and message processingretrieved 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 maple-finance factor RD-F-152 score green collected_at 2026-04-27 05:38:08