Bridge tracks nonce-consumed mapping

Evidence summary #

LayerZero endpoint handles nonce management at the protocol layer (sequential nonce assignment per pathway). OFT V2 uses _blockingLzReceive with nonce tracking at the endpoint level. retryMessage() in BaseXVSProxyOFT uses nonce_ parameter for failed message identification. Replay protection inherited from LayerZero V2 endpoint, not re-implemented in the Venus contract. Confidence: medium — nonce implementation details rely on LayerZero protocol docs, not Venus-specific source.

Sources #

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 →