PIPEs V2
summary
An extension to Bitcoin Script uses witness encryption (a Bartušek–Shah variant) to make non‑consensus opcodes practical by encrypting keys rather than signatures, enabling single-transaction ZKP verification and replacing many binary predicates (CTV, op_vault‑style behavior) with caveats: no direct introspection and probabilistic finality. Current implementation produces a 338 terabytes ciphertext for a general verifier and requires about 50 AMD EPYC CPUs to decrypt in ~10 minutes (~$100–200 per decrypt); optimizations aim for 50–100 GB or $10–20 and ongoing cryptanalysis targets nonstandard assumptions.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:45Bitcoin needs new opcodes
- 3:54Witness encryption concept
- 5:39Bitcoin Pipes V1 to V2
- 7:02Performance challenges
- 9:12Witness encryption research
- 10:15Bitcoin Pipes for covenants
- 12:00What V2 supports
- 14:28Non-consensus logic handling
- 15:12Non-interactive ZKPs
- 16:39Faster meta protocol security
- 18:22Deprecating opcodes
- 20:05Future roadmap
- 22:33Applications beyond Bitcoin
- 24:05Q&A
related talks
28mBitVM: Innovation Without a Soft Fork
01h 09mProofs - Practice 1
44mTooling for building zkEVM: PIL and Circom
22mZcash For Every(One|Where): Creating Shielded Transactions on All The Things!
28mEvolution of Optimistic Rollup proofs
33mZKVM: Fast, Confidential Smart Contracts
01h 23mProgram Presentations
26mSecure protocols on BIP taproot