Neutrino, Good and Bad
summary
Compares BIP37 to Neutrino and shows Neutrino computes a universal deterministic per-block filter so servers do one filter per block instead of per client, cutting CPU and removing the TXindex requirement; a measured client filter is about 20 KB per 1.4 MB block so bandwidth increases but privacy and DoS resilience improve. Remaining risks: servers can serve malicious filters unless there is a filter commitment (coinbase OP_RETURN proposal), and light clients still can’t fully validate consensus or prevent bad‑block isolation, so full nodes remain necessary for large funds.
AI-written summary · about
chapters (8)
- 0:00Intro
- 1:15Current Situation
- 3:25How it Works
- 7:26What Neutrino Does
- 12:23Lie of Omission
- 14:03Bad Block Attack
- 15:45Alternatives
- 17:53Summary
related talks
43mCompact Block Filters for Users and Wallet Developers
09mThe Need for Decentralized Indexers
01h 02mThe Bitcoin Privacy Debate
35mWhy Privacy Matters
54mDistributed Trust: Is “Blockchain” the answer?
16mBitcoin Privacy 101
14mThe Bitcoin Meta Problem
40mSilent Payments and Alternatives to Bitcoin Privacy