Bridge tracks nonce-consumed mapping
Frax Finance's assessment for RD-F-153 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
FraxFerry: batch-index model — each batch has a unique index; same batch hash consumed on execution prevents replay. The Captain cannot re-propose an already-executed batch. Fraxtal OP Stack: WithdrawalTransaction hash mapping prevents replay of the same L2-to-L1 message. LayerZero OFT: nonce tracking at the LZ endpoint level per pathway (srcEid + sender + dstEid) prevents message replay. All three surfaces have nonce/hash-consumed replay prevention.
Sources #
- DocsFrax FraxFerry Bridge DocsFraxFerry docs — step-by-step: batch execution consumes the batch; no replay path describedretrieved 2026-05-17
- L2BEAT FraxtalL2BEAT Fraxtal — OP Stack withdrawal mechanism with 7-day challenge window and hash-consumed withdrawalsretrieved 2026-05-17
Methodology #
Determine whether the bridge inbox maintains a nonce-consumed mapping and rejects replay of used nonces.
See the full factor methodology and distribution across all protocols →