Bridge tracks nonce-consumed mapping
Midas'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 #
LayerZero V2: the LayerZero endpoint tracks nonce/packet ordering — packets are ordered per pathway and cannot be re-submitted (nonce-consumed tracking at endpoint level). This is a structural property of the LayerZero V2 protocol. Axelar gateway: command IDs on the Axelar gateway are tracked via an executed mapping and cannot be re-executed (replay protection at gateway contract level). Both mechanisms provide replay protection at the infrastructure layer.
Sources #
- URLAxelar Send Tokens DocumentationAxelar gateway: command IDs tracked in executed mapping — replay protection at protocol levelretrieved 2026-05-16
- LayerZero V2 OFT — Nonce/OrderingLayerZero V2 documentation: ordered packet delivery, nonce tracking at endpoint level prevents replayretrieved 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 →