The Chaincode Podcast

Josibake joins us to talk about his work on the Bitcoin Core wallet, bitcoin data and onboarding to bitcoin development. We discussed: - Analyzing historical transaction data (1:25)   - Creating a publicly available dataset (4:12)   - What could it be used for? (7:30) - Bitcoin Core wallet (9:00)   - Why have a wallet in Bitcoin Core? (10:00)   - Separation of GUI from wallet (12:35)   - Only use one input type when building transaction (13:40)     - PR #24584 in Bitcoin Core   - How is working on the wallet? (17:15) - Cross-input signature aggregation (19:48)   - Catching up on history (20:40)   - Writing the BIP with Hackspec (22:05)   - Thoughts on shipping cross-input signature aggregation separately (22:50) - Onboarding to Bitcoin development (28:35)   - Running the seminar with friends (29:55)   - Giving back to open source (31:20)

Our topics: - Lightning Dev Kit (1:04)   - Zeroconf Channels (2:22)   - Rapid Gossip Sync (3:46)   - How does LDK pick priorities? (8:55)   - LDK Lite (10:12)   - Will LSPs be needed forever? (12:25) - Validated Lightning Signer (15:20)   - A Lightning Node's Problem with Hats  - VLS code base - FROST and ROAST (23:00)   - Recovering a FROST wallet (24:00) - Taproot adoption (26:18) - Future of the Lightning Network (30:48) - Stratum V2 (34:25)   - OFAC and mining (37:57)   - Other benefits over Stratum (39:59) Thanks to Gurwinder Sahota for the sound engineering.

We catch up with 0xB10C about monitoring pools and tracing code execution in nodes. Our topics: - What he's been up to since the residency (1:05) - Monitoring the mempool (2:52)   - Mempool Observer - Monitoring Mining pools (4:27)   - MiningPool Observer   - Mining pools not mining P2TR at Taproot activation (5:24)   - Why monitor the network? (8:20)   - Template discrepancies between pools and monitor (9:25) - User-space Statically Defined Tracing (USDT) (11:07)   - Tracing Readme   - Using tracepoints to simulate coin selection (13:36)   - Why are tracepoints in production code? (14:38)   - Using tracepoints for P2P monitoring (17:05)   - Using tracepoints to review PRs (22:00)   - Benchmarking Erlay with USDT (22:42) Other resources:   - TransactionFee.info Thanks to Emily Kee for the sound engineering.

Gloria Zhao sits down with us to discuss her package relay proposal and what it is like as a relative newcomer to propose a big change. - What's package relay? (1:04)   - Mailing List: Package Relay Proposal - Why do people care about package relay? (3:12) - What are these "contracting protocols" package relay matters for? (5:03)   - Pinning attacks (6:28) - Why do you work on package relay? (6:55) - What's special about the mempool? (10:18) - How do you approach the security considerations? (12:07) - Synthesizing information for the ones coming after you (15:27) - What's next for package relay? (17:50) - Bridging protocol development with L2 (20:55) Additional resources: - Mailing List: Package Mempool Accept and Package RBF - Brink Podcast: Ep1 Mempool Policy - Censorship and DoS Attacks: An intro to Mempool Policy - Transaction Relay Policy for L2 Developers - Mempool Garden Thanks to Emily Kee for the sound engineering.

Martin Zumsande joins us to tell us about the address spam in the summer of 2021 and his interests in AddrRelay and Bitcoin Core development. We discuss with Martin: - His background (1:38) - Getting interested in Bitcoin (2:45) - How to approach P2P (3:55) - The network is changing (7:30) - What's the purpose of the Address Manager (AddrMan)? (9:33)Peering differences to LN nodes (11:00)   - Ethan Heilman's talk on Network Partitioning Attacks (12:10)   - Addrman and eclipse attacks (12:27) - AddrRelay and the role of node addresses (12:55)Getting connected to the network (13:37) - Self-announcements (14:25) - Address spam in summer 2021 and peer distribution (15:05) - Correction: The peer would not get addresses-divided-by-peers addresses, but 2×addresses-divided-by-peers addresses as the addresses get forwarded to two peers each. (18:00) - Estimating the Node Degree of Public Peers and Detecting Sybil Peers Based on Address Messages in the Bitcoin P2P Network by Matthias Grundmann (19:30) - Simulating the network (20:15) - Requesting addresses from peers (21:45) - Walking through first connection of a node (25:25)Coinscope paper (27:10) - Being a Bitcoin Core contributor (27:50) Thanks to Emily Kee for the sound engineering.

Postdoc Researcher Sergei joins Murch and Jonas to talk about channel balance probing in Lightning, privacy concerns in general, and the importance of researcher-developer collaboration. We discuss: - Sergei's background (1:50)    - Sergei's homepage with links to all prior research - Lightning basics (2:50) - Why LN payments fail (3:40) - Why privacy is important (5:30) - Privacy potential of Lightning vs L1 Bitcoin (6:40) - How probing works (8:40) - Why is balance discovery bad? (11:30) - Persistent identities in Lightning (13:00) - Multi-vector security model and trade-offs (17:45) - "Twitter for your bank account" meme (20:20) - The danger of overestimating Bitcoin's privacy (21:00) - Lightning integrations and walled gardens (22:00) - Lightning Service Providers and LN's centralized topology (23:05) - LNBIG booth in El Salvador (25:30) - Potential oligopoly of large nodes (27:15) - Probing parallel channels (28:30)   - Analysis and Probing of Parallel Channels paper - Combining probing with jamming (33:00) - The limit on in-flight payments (36:00)   - StackExchange answer about transaction size limit - Bad and good probing (41:20) - Countermeasures and reputation (44:00)Overview of anti-jamming measures - Hub-and-spoke terminology and aviation analogy (49:00) - Doing research in Bitcoin and Lightning (53:10) - Why Bitcoin is unique (55:10) - Researcher-developer collaboration (58:00) Related research: - On the Difficulty... -- the first paper about LN balance probing - An Empirical Analysis paper about three LN attack vectors including probing - Counting Down Thunder paper about timing attacks - Congestion Attacks paper about jamming - Cross-layer Deanonymization paper about linking L1 and L2 - Flood & Loot paper about malicious fee negotiation strategies - Hijacking Routes paper about adversarial fee undercutting Thanks to Justin for the sound engineering.

Postdoc Researcher Clara joins Murch to discuss their block building research. They cover their proposal, which outlines suggested improvements to the current Bitcoin Core block building algorithm using candidate sets. Murch and Clara discuss: - Building a valid block 101 (5:45) - The current getblocktemplate algorithm (11:35) - Child pays for parent (13:40) - Is there something better? (15:45) - How easy would it be to guess the next block? (27:25) - Do we have a better idea than initially mining an empty block? (29:25) - Empty blocks and SegWit (33:45) - How to improve on the candidate set algorithm e.g., linear programming (35:00) - Why should Bitcoin Core have better block building? (37:00) - How to compare different block building techniques (38:55) Thanks to Caralie for the sound engineering.

Sanket describes to Murch his work on Miniscript. We explore uses for Miniscript, learn about intersections with PSBTs, Output Descriptors, and Taproot, and suss out the difference between Miniscript and Miniscript Policy. Note: This episode was recorded in the context of travel for Bitcoin 2021. We apologize for the less polished than usual audio quality due to the different equipment and recording environment. We discuss: - What's Miniscript? (1:54) - Partially Signed Bitcoin Transactions (PSBTs) (5:13)   - Analyzing PSBTs with Miniscript (7:22) - How do Output Descriptors relate to Miniscript (10:16) - Implementations of Miniscript (13:36) - Semantic analysis of Scripts (14:54)   - Non-malleability of miniscript (22:47) - Miniscript Policy (25:15)   - Rediscovering HTLCs (29:41) - Miniscript uses (33:11)   - Removing script limitations with Taproot (34:42)   - Generic signing (35:53)   - Future work (37:34)   - The role of policy (40:24) Related links: - Miniscript website - Rust Miniscript - Miniscript C++ implementation - Gramtropy - ##miniscript on Libera Chat Thanks to Caralie for the sound engineering, and thanks to Matthew Zipkin for assistance with squashing reverb artifacts.

P2P experts Pieter and Amiti chat about the P2P network. In this episode they cover: - AddrRelay high-level goals and constraints (1:15)   - Very different than the goals of blocks and transactions   - Marginal fee rate (4:35) - Should we consider different transport layers? (5:40) - FIBRE Episode with Matt Corallo (7:40) - The introduction of Addrman in 2012, PR #787 (8:55) - What existed before AddrMan and the evolution of DoS resistance. - Eclipse Attack paper (14:55)   - Sybil attack   - Addrman and eclipse attacks wiki page   - Anchors connections - PR #17428 - Connection exhaustion issue (19:50) - Erlay (paper, BIP) (20:55) - AddrRelay (23:15)   - Limiting addr black holes - PR #21528   - Rate limiting on address gossip in 22.0 - Leaky bucket rate limiter (27:00) - Address Spam (29:20)   - Estimating the Node Degree of Public Peers and Detecting Sybil Peers Based on Address Messages in the Bitcoin P2P Network by Matthias Grundmann (31:35)  - Coinscope paper (31:45)  - TxProbe (32:00) - Separate network stack (37:20) - Fingerprint attacks (37:15) - ASMAP (39:00) Thanks to Caralie for the sound engineering.

Amiti returns to the Chaincode office to discuss all things p2p. We discuss: Why Amiti works on P2P (1:50) A framework for p2p design (4:25) How do we systemize Bitcoin Core knowledge? (6:20) Searchable #bitcoin-core IRC logs (8:35) Forward compatibility and upgradability (15:00) Partition resisitence (16:10) Eclipse Attacks (17:00) Altnet (20:40) Messages sent across the wire (20:55) AddrRelay and AddrMan (24:35) Bootstrapping, DNS seeds and address announcements (25:25) DoS issues (27:35) Address Manager (29:00) New table and tried table (30:00) The Bitcoin network “dance” (31:25) Transaction download on Bitcoin’s p2p network comic (32:25) Addresses and proof of work (32:45) Inbound and outbound connections (34:00) Block relay only connections and full connections (35:35) Thanks to Caralie for the sound engineering.