Anthony Towns and Mikhail Kudinov joined Optech to discuss Newsletter #386: - A notice about the wallet migration bug in Bitcoin Core - Building a vault using blinded co-signers - BIP for Peer feature negotiation - Year 2106 timestamp overflow - BIP54 timestamp restriction for a timestamp overflow soft fork - Mitigating a CTV footgun - CTV activation meeting - OP_CHECKCONSOLIDATION to enable cheaper consolidations - Hash-based signatures post-quantum Bitcoin - And more You can listen on our website: Fountain: Spotify: Apple Podcasts:
Bitcoin Optech newsletter #386 is here: - summarizes a vault-like scheme using blinded MuSig2 - describes a proposal for Bitcoin clients to announce and negotiate support for new P2P features - links to 2106 timestamp overflow discussion and considerations around BIP54 - notes a CTV activation meeting and CTV footgun discussion - summarizes the OP_CHECKCONSOLIDATION proposal - links to a report of hash-based post-quantum signature schemes - Optech Newsletter #386 Podcast Jonathan T. Halseth posted to Delving Bitcoin a prototype of a vault-like scheme using blinded co-signers. Unlike traditional setups using co-signers, this scheme uses a blinded version of MuSig2 to ensure the signers know as little as possible about the funds they are involved in signing... Anthony Towns posted to the Bitcoin-Dev mailing list about a proposal for a new BIP to define a P2P message that would allow peers to announce and negotiate support for new features... Asher Haim posted to the Bitcoin-Dev mailing list asking Bitcoin developers to act promptly to prepare for a migration from uint32 to uint64 block timestamps... Josh Doman posted to the Bitcoin-Dev mailing list and Delving Bitcoin asking whether it’s might be worthwhile to modify the consensus cleanup proposal to be more permissive to odd block timestamp behavior to allow a potential soft fork solution to the 2106 block timestamp overflow issue... Chris Stewart posted to Delving Bitcoin a discussion of a “footgun” with OP_CHECKTEMPLATEVERIFY (CTV)... Developer 1440000bytes hosted a CTV (BIP119) activation meeting... billymcbip proposed an opcode specifically optimized for consolidations. OP_CHECKCONSOLIDATION (CC) would evaluate to 1 if and only if it’s executed on an input with the same scriptPubKey as an earlier input in the same transaction... Mikhail Kudinov and Jonas Nick posted to the Bitcoin-Dev mailing list about their work on evaluating hash-based signatures for use in Bitcoin... Bitcoin Optech will host an audio recap discussion of this newsletter on Tuesday at 17:30 UTC. Join us to discuss or ask questions!
Bastien Teinturier, Rearden Code, and Pieter Wuille joined Optech to discuss Newsletter #385: 2025 Year-in-Review Special. Catch up on Bitcoin developments in 2025. You can listen on our website: Spotify: Apple Podcasts:
Bruno Garcia and Liam Eagen joined Optech to discuss Newsletter #369: News 24:56 Update on differential fuzzing of Bitcoin and LN implementations 0:58 Garbled locks for accountable computing contracts Selected Q&A from Bitcoin Stack Exchange 39:45 Is it possible to recover a private key from an aggregate public key under strong assumptions? 41:24 Are all taproot addresses vulnerable to quantum computing? 45:20 Why cant we set the chainstate obfuscation key? 52:09 Is it possible to revoke a spending branch after a block height? 53:45 Configure Bitcoin Core to use onion nodes in addition to IPv4 and IPv6 nodes? Releases and release candidates 54:22 Bitcoin Core 29.1rc2 56:45 Core Lightning v25.09rc4 Notable code and documentation changes 57:37 Bitcoin Core #31802 1:04:46 LDK #3979 1:06:19 LND #10102 1:07:04 Rust Bitcoin #4907 You can listen on our website: Fountain: Spotify: Apple Podcasts: