Bridge tracks nonce-consumed mapping
Cap (cUSD / stcUSD)'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 tracks nonce consumption via nextNonce(srcEid, sender, dstEid) mechanism and rejects replayed packets. This is a core protocol invariant in LZ v2 — nonce ordering is enforced at the endpoint level.
Sources #
- GitHubLZ v2 deployments confirming v2 nonce mechanism appliesconfig/layerzero-v2-deployments.json: confirms LZ v2 deployment on Ethereum and MegaETH — inherits v2 nonce trackingretrieved 2026-05-17
- LayerZero v2 EndpointV2.sol — nonce-consumed mappingLayerZero v2 EndpointV2.sol: nonce tracking and anti-replay protection is a core EndpointV2 invariantretrieved 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 →
rubric_version v1.7.0 protocol cap factor RD-F-153 score green collected_at 2026-05-17 10:56:24