Bridge binds message to srcChainId
Frax 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 #
FraxFerry: transaction hashes include source chain context (amounts, recipients, source chain implicit in deployment). Fraxtal OP Stack: L2-to-L1 messages are chain-ID bound per OP Stack standard (withdrawal transactions include chainId in the message hash). LayerZero OFT: LZ endpoint binds messages to srcEid (source endpoint ID = source chain ID); messages from chain A cannot be replayed as if from chain B. All three bridge surfaces include source chain binding in message validation.
Sources #
- DocsLayerZero DVN AddressesLayerZero V2 DVN addresses docs — srcEid binding in OFT message structureretrieved 2026-05-17
- Frax FraxFerry Bridge DocsFraxFerry docs — one-hour age requirement on source chain before processing to avoid reorg replayretrieved 2026-05-17
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 →