Bridge tracks nonce-consumed mapping

Babylon Protocol'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 #

Replay protection: Bitcoin UTXO model is inherently replay-resistant (each UTXO can only be spent once); x/btcstaking tracks delegation state (Active/Unbonding/Withdrawn) preventing re-registration of processed transactions; IBC packets use sequence numbers (incrementing counter per channel). Staking script docs confirm each staking output is a unique UTXO with unique outpoint.

Sources #

GitHub
Babylon x/btcstaking — delegation state machinex/btcstaking — delegation state tracking (Active/Unbonding/Withdrawn) prevents replayretrieved 2026-05-04
Docs
Babylon staking script — UTXO replay protectionStaking script docs — each stake is a distinct UTXO, inherently non-replayableretrieved 2026-05-04

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 babylon-protocol factor RD-F-153 score green collected_at 2026-05-04 19:43:27