Bridge tracks nonce-consumed mapping
Ondo 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 #
LayerZero v2 EndpointV2 maintains an internal nonce-sequencing mechanism per OApp pathway (srcChainId, srcAddress, nonce). Messages are delivered in-order and cannot be replayed. The LayerZero protocol-level nonce tracking is well-documented and the primary replay protection mechanism. The `OndoMintBurnAdapter` does not need an additional nonce mapping — it relies on EndpointV2's enforced delivery guarantees.
Sources #
- DocsLayerZero v2 docs (DVN architecture, OFT spec)https://docs.layerzero.network/v2/retrieved 2026-05-12
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 ondo-finance factor RD-F-153 score green collected_at 2026-05-14 12:01:55