Bridge tracks nonce-consumed mapping
Wormhole's assessment for RD-F-153 — scored gray on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.
Evidence summary #
Bridge tracks nonce-consumed mapping | YES — Implemented differently per chain but replay protection is present across the architecture: On Ethereum, Token Bridge maintains `completedTransfers` mapping of processed VAA hashes — any attempt to replay a VAA hash is rejected. On Solana, `Claim` PDA accounts are created at `["Claim", emitter, sequence]` ensuring each `(emitter_address, emitter_chain, sequence)` tuple can only be processed once. The Core Bridge delegates nonce/replay responsibilit...
Sources #
- Curator noteExtracted from 03-oracle-deps.md — RD-F-153; no URL citedretrieved 2026-04-28
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 →