BitVM moves bounded computation offchain and brings a prearranged fraud proof to Bitcoin; it is not a general-purpose virtual machine running directly in Bitcoin Script.
The original BitVM describes a two-party prover–verifier relationship. The prover executes a program offchain, commits to its trace, and the verifier intervenes only when claiming that the result is wrong. [1]
BitVM2 verifies a SNARK with scripts divided into smaller subprograms. The optimistic path does not put the whole computation onchain; in a dispute, an invalid assertion can be challenged through a shortened protocol by a permissionless challenger. [2]
BitVM Bridge aims to move BTC to second layers more safely: during setup it reduces the assumption from an honest majority to at least one honest participant, and anyone—not only a predefined verifier—can challenge an invalid proof. [2]
A permissionless challenge does not mean zero trust. For liveness, the bridge still needs at least one active rational operator; if all fail, funds can become stuck, and the concrete protocol also depends on setup, data availability, incentives, and a correct transaction graph. [3]
The official BitVM Bridge implementation labels itself non-production and explicitly warns against production use. The repository is a prototype SNARK verifier and bridge, not an audited guarantee of safe BTC transfers. [4]
Permissionless challenging does not remove operating costs. The protocol uses large scripts, split proofs, collateral, deadlines, and fees; inactivity or censorship can harm liveness even when an attacker cannot produce a valid proof. [3]
BitVM does not turn Bitcoin Script into a conventional virtual machine for arbitrary onchain programs. The construction is designed without a consensus change: its generality comes from offchain computation, commitments, timelocks, and a presigned dispute that Bitcoin can enforce. [5]
The name BitVM covers several distinct and evolving designs: BitVM1, BitVM2, and particular bridge protocols do not have the same roles or assumptions. Before use, verify the exact version, transaction graph, setup, operator count, challenge path, and emergency exits. [4]
For the clearest picture, read this entry together with Bitcoin Script, Taproot, Covenants, Multisig, Sidechain, Soft Fork.
01Does BitVM run programs directly on Bitcoin?+
No. The program is computed offchain; Bitcoin acts as the judge of a prearranged dispute over cryptographic commitments and a small proof step.
02Is BitVM a finished trustless bridge?+
No. BitVM2 reduces some trust assumptions and allows permissionless challenging, but a concrete bridge still depends on its setup, operators, liveness, and a non-production implementation.