Bridge tracks nonce-consumed mapping

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

LZ v1 endpoint handles nonce tracking at the infrastructure layer — monotonically increasing nonces per (srcChainId, srcAddress, dstChainId, dstAddress) path prevent replay. Messages delivered out of order or replayed are rejected at the LZ endpoint. The retryMessage() function handles legitimately failed delivery only for packets from trusted remotes. Replay protection is architecturally inherent to LZ v1.

Sources #

Etherscan
LayerZero v1 adapter — nonce and replay protectionLZ adapter source — retryMessage() for failed delivery recovery; NonblockingLzApp inherits LZ endpoint nonce trackingretrieved 2026-05-16

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 →

rubric_version v1.7.0 protocol beefy factor RD-F-153 score green collected_at 2026-05-16 13:10:30