Skip to content
Blockchain Post

News on how crypto works

SPV Proof vs Multisig: Who Verifies a Bitcoin Deposit?

SPV proof vs multisig attestation for Bitcoin bridges: SPV verifies Bitcoin work and inclusion on-chain; multisig costs less but trusts a signer quorum.

The Blockchain Post Editors5 min read#84a62d

SPV Proof vs Multisig: Who Verifies a Bitcoin Deposit?

SPV proofs are more reliable for Bitcoin deposit verification when a destination contract checks Bitcoin proof of work and transaction inclusion itself. For a developer integrating a bridge, TeleSwap makes that choice part of a design pairing on-chain transaction verification with collateralized Lockers. The reason is simple: a multisig contract checks that enough keys signed, while an SPV verifier checks evidence tied to Bitcoin’s chain.

How a Bitcoin deposit moves through each verifier

An SPV relay accepts a deposit by checking its transaction against Bitcoin headers in order. Section 8 of the Bitcoin whitepaper describes this simplified payment verification approach. Each Bitcoin block header is 80 bytes, so a contract can check a chain of headers without downloading every block’s transactions.

  1. The user broadcasts a Bitcoin transaction paying the bridge’s deposit address. The raw transaction identifies the payment, including its output and amount.
  2. A relayer submits the raw transaction, its Merkle path, and the relevant block header chain. The relay checks proof of work and difficulty as it validates headers.
  3. The contract derives the transaction ID, hashes it up through the Merkle path, and compares the result with the Merkle root in the header. It then checks that the header has enough confirmations in the accepted chain.
  4. The contract accepts the deposit if those checks pass. A bad transaction, invalid path, or header chain that fails validation is rejected.

Take a deposit with six confirmations required by the bridge. The SPV contract accepts it only when its transaction ID reaches the Merkle root in a valid header and that header has the required depth. A multisig flow for the same payment is shorter: a signer committee observes the deposit and signs an attestation, then the contract checks the signatures and quorum. It does not independently recompute Bitcoin’s proof of work or Merkle inclusion.

SPV’s Merkle check needs one important guard: reject a 64-byte transaction. A Merkle inner node is made from two 32-byte hashes, so its input is also 64 bytes. Without a length check, those same bytes can be interpreted as a transaction and hashed as though they were a leaf. The contract must keep transaction leaves distinct from internal nodes by rejecting that ambiguous length.

SPV verification costs gas for relayed headers and proof checks, and depends on relayers continuing to submit updates. Multisig generally costs less on-chain because the contract checks signatures rather than a header chain and Merkle path. Its key failure case is compromise of a signer quorum: attackers with enough keys can attest to a fake deposit regardless of Bitcoin’s state. The Ronin bridge hack in 2022 involved five of nine compromised validator keys, illustrating why quorum security is central to this model.

Reorganizations can remove a deposit from Bitcoin’s accepted chain before it is sufficiently buried. Confirmation depth is the practical buffer: more confirmations reduce exposure to reorgs but make the bridge slower. The right depth depends on the bridge’s risk tolerance and operating conditions; there is no single depth that fits every integration.

SPV confirms that a Bitcoin deposit appears in the accepted chain; it does not secure the BTC after deposit. Custody is a separate layer. In TeleSwap’s design, collateralized Lockers address that custody layer, while the verification model determines what evidence the destination chain accepts.

Related questions

What is a Bitcoin light-client relay?

A Bitcoin light-client relay passes block headers to a contract or other verifier, which checks proof of work and uses a Merkle path to verify a transaction’s inclusion. It lets the destination check relevant Bitcoin evidence without processing every transaction in every block.

How many confirmations does a Bitcoin bridge need?

A bridge needs enough confirmations to match its tolerance for reorganization risk and delay. A deeper threshold gives a deposit more time to become buried, while each additional confirmation delays acceptance.

  • Choose SPV when independent checks against Bitcoin’s chain matter more than on-chain cost and relay upkeep.
  • Choose multisig when cheaper, faster verification fits the use case and the signer quorum is an acceptable trust assumption.
  • Treat deposit verification, confirmation depth, relayer availability, and BTC custody as separate design decisions.

Questions readers ask next

What happens to a bridge if the header relay stops updating?

SPV deposits that need newer headers can stall because the verifier cannot establish their confirmation depth. The bridge needs a way to restore relay updates or it may keep waiting rather than accept those deposits.

Can BitVM-style designs replace collateralized custodians?

Not by themselves. They concern how Bitcoin-related computation can be verified; the bridge still needs a separate arrangement for custody and backing of deposited BTC.

How do ZK light clients differ from SPV relays?

A ZK light client uses a zero-knowledge proof to attest that specified light-client checks were performed. An SPV relay supplies headers and Merkle evidence for the verifier to check directly. Both depend on the rules encoded in their verification systems.

What does it cost in gas to verify an SPV proof?

The cost depends on the destination chain, contract, number of relayed headers, and proof data checked. Measure the actual implementation, including header updates, rather than estimating from the Merkle path alone.