BitVM3, Binohash vs soft forks
summary
BitVM3 cuts disprove/assert transaction sizes from megabytes to kilobytes, lowering operator collateral and making hundreds or thousands of operators economically feasible, but the bridge safety remains one-of-n signer pre-signing so trust assumptions don't change. Binohash enables transaction introspection inside BitVM proofs yet requires rollup publish transactions to include per-operator publish outputs, creating huge UTXOs and limiting operator scaling. Built prototypes work, but neither reduces signer trust; soft-fork covenants (input-commit, OP_CAT/txhash) actually move security.
AI-written summary · about
chapters (12)
- 0:00BitVM3 intro and bridge security
- 1:51BitVM3 trust assumptions
- 3:36BitVM3 transaction size
- 5:26BitVM3 collateral incentives
- 6:30Bitcoin state with light clients
- 7:34Binohash vs long chain proofs
- 9:20Binohash rollup limits
- 10:48Binohash scaling challenges
- 11:51Bridge signing bottlenecks
- 12:36Soft forks for bridge trust
- 13:41Trustless Bitcoin rollup
- 14:28Q&A
