Bridge binds message to srcChainId

Beefy 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 #

LZ v1 adapter: trustedRemoteLookup mapping keyed by LZ chain ID (uint16 _remoteChainId). Messages validated per source chain via setTrustedRemote(uint16 _remoteChainId, bytes calldata _path). lzReceive() receives _srcChainId parameter and validates against trusted remote for that specific chain. Per-chain isolation is inherent to LZ v1 trusted-remote design. chainIdToLzId/lzIdToChainId mappings provide bidirectional chain binding.

Sources #

Etherscan
LayerZero v1 adapter — srcChainId binding in message validationLZ adapter 0xdddaec... — setTrustedRemote(uint16 _remoteChainId, bytes calldata _path); chainIdToLzId / lzIdToChainId mappings; lzReceive(_srcChainId param)retrieved 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 beefy factor RD-F-152 score green collected_at 2026-05-16 13:10:30