Bridge binds message to srcChainId
Midas'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 #
LayerZero V2 OFT: the protocol enforces per-pathway configuration using Endpoint IDs (EID) — each pathway is {srcEid, dstEid}; packets are structurally bound to source chain EID. This is a structural property of LayerZero V2, not adapter-specific config. Axelar ITS: Axelar messages include source chain ID in the Axelar message struct by design. Both mechanisms bind messages to source chain. Midas-specific configuration cannot be verified without OFT adapter address, but the underlying frameworks enforce srcChainId binding.
Sources #
- URLAxelar ITS DocumentationAxelar ITS documentation: messages include source chain ID in Axelar message structretrieved 2026-05-16
- LayerZero V2 OFT QuickstartLayerZero V2 documentation: OApp pathway config uses srcEid/dstEid — packets bound to source endpoint IDretrieved 2026-05-16
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 →