Bridge binds message to srcChainId

Babylon Protocol's assessment for RD-F-152 — scored green on the v1.7.0 rubric. The evidence below is the curator's reasoning for this score.

Evidence summary #

Cross-chain messages are implicitly chain-bound: BTC headers include PoW difficulty parameters (Bitcoin-mainnet-specific); covenant PSBT transactions are Bitcoin-mainnet-specific by UTXO script construction; IBC messages include connection_id and channel semantics binding them to sender/receiver chain pair. Cross-chain replay is not possible at the Bitcoin UTXO layer (each UTXO spendable only once).

Sources #

Docs
Babylon x/btclightclient — chain-specific PoW validationx/btclightclient — validates Bitcoin headers by PoW; Bitcoin-specific parameters prevent cross-fork replayretrieved 2026-05-04
Docs
Babylon staking script — UTXO chain bindingStaking script docs — Bitcoin UTXO model is inherently chain-specific; IBC channel semantics provide chain bindingretrieved 2026-05-04

Methodology #

Determine whether the bridge message struct includes `srcChainId` and the verifier enforces per-chain separation.

See the full factor methodology and distribution across all protocols →

rubric_version v1.7.0 protocol babylon-protocol factor RD-F-152 score green collected_at 2026-05-04 19:43:27