Bridge binds message to srcChainId
mETH Protocol'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 Endpoint V2 includes EID (endpoint/chain ID) in the packet Origin struct: srcEid field binds each message to its source chain. Peer validation via setPeer() further enforces which source addresses are valid per EID. Chain separation is enforced at the protocol layer.
Sources #
- URLLayerZero V2 OFT — srcEid in Origin structLayerZero V2 OFT Quickstart — Origin struct includes srcEid binding messages to source chainretrieved 2026-05-16
- L1cmETHAdapter — setPeer() srcChainId bindingL1cmETHAdapter implementation — setPeer(uint32 _eid, bytes32 _peer) restricts valid source addresses per chain 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 →
rubric_version v1.7.0 protocol meth-protocol factor RD-F-152 score green collected_at 2026-05-16 02:17:50