Authenticated Input: A Challenge For Bridges
summary
Bridges need authenticated input so onchain fraud proofs use exact bytes; experiments compare Lamport signatures, adapter signatures with 8‑bit wide labels, and a new anti‑chain winternets scheme. Implementation in Rust runs against Bitcoin Core standardness limits: Lamport cannot fit a 128‑byte snark in one standard input (≈62‑byte limit); adapter+wide‑labels cuts onchain cost ≈8× at the expense of thousands to millions of offchain values; anti‑chain winternets sits between (≈4× cheaper than Lamport, ≈4× pricier than optimized adapters) and fits standard limits.
AI-written summary · about
chapters (11)
- 0:00Authenticated input challenges
- 1:57Bitcoin bridges and proof of burn
- 6:36Bitcoin consensus limitations
- 7:39Lamport signatures baseline
- 9:49Adapter signatures for swaps
- 15:25Optimizing adapter signatures
- 20:02Winter signatures issue
- 24:20Anti-chain Winter signatures
- 25:24Signature schemes comparison
- 32:29Choosing the right scheme
- 35:17Q&A
related talks
01h 07mBitcoin Without Controversy
50mScaling Bitcoin On-Chain
15mThis Researcher Has a Plan to Put Privacy in Every Bitcoin Wallet
20mChar: The Infrastructure Bet Underneath Every Bitcoin L2
26mSecure protocols on BIP taproot
44mEmulating Covenants While Minimizing Trust
24mThe Bitcoin Virtual Machine Breakthrough Nobody Saw Coming
38mWhat Features Does Bitcoin Need For Global Adoption?