@@ -27,7 +27,7 @@ software.
2727 implementations has not only revealed bugs but has also driven
2828 clarifications to the LN specification. Developers of Bitcoin
2929 projects are encouraged to investigate making their software a
30- supported target for bitcoinfuzz.
30+ supported target for bitcoinfuzz. {% assign timestamp="24:56" %}
3131
3232- ** Garbled locks for accountable computing contracts:** Liam Eagen
3333 [ posted] [ eagen glock ] to the Bitcoin-Dev mailing list about a
@@ -39,7 +39,7 @@ software.
3939 opinion) practical garbled lock whose fraud proof is a single
4040 signature, which represent over a 550x reduction of onchain data
4141 compared to BitVM2." As of this writing, his post has not received
42- any public replies.
42+ any public replies. {% assign timestamp="0:58" %}
4343
4444## Selected Q&A from Bitcoin Stack Exchange
4545
@@ -54,30 +54,30 @@ answers posted since our last update.*
5454
5555- [ Is it possible to recover a private key from an aggregate public key under strong assumptions?] ( {{bse}}127723 )
5656 Pieter Wuille explains current and hypothetical security assumptions around
57- [ MuSig2] [ topic musig ] scriptless [ multisignatures] [ topic multisignature ] .
57+ [ MuSig2] [ topic musig ] scriptless [ multisignatures] [ topic multisignature ] . {% assign timestamp="39:45" %}
5858
5959- [ Are all taproot addresses vulnerable to quantum computing?] ( {{bse}}127660 )
6060 Hugo Nguyen and Murch point out that even [ taproot] [ topic taproot ] outputs
6161 constructed to be spent only using script paths are [ quantum] [ topic quantum
6262 resistance] vulnerable. Murch goes on to note "Interestingly, the party that
6363 generated the output script would be able to show that the internal key was a
64- NUMS point and thus prove that a Quantum Decryption has occurred."
64+ NUMS point and thus prove that a Quantum Decryption has occurred." {% assign timestamp="41:24" %}
6565
6666- [ Why cant we set the chainstate obfuscation key?] ( {{bse}}127814 )
6767 Ava Chow highlights that the key that obfuscates on-disk contents of the
6868 ` blocksdir ` (see [ Newsletter #339 ] [ news339 blocksxor ] ) is not the
6969 same key that obfuscates the ` chainstate ` contents (see [ Bitcoin Core
70- #6650 ] [ ] ).
70+ #6650 ] [ ] ). {% assign timestamp="45:20" %}
7171
7272- [ Is it possible to revoke a spending branch after a block height?] ( {{bse}}127683 )
7373 Antoine Poinsot points to a [ previous answer] ( {{bse}}122224 ) confirming that
7474 expiring spending conditions, or "inverse timelocks", are not possible and
75- perhaps not even desirable.
75+ perhaps not even desirable. {% assign timestamp="52:09" %}
7676
7777- [ Configure Bitcoin Core to use onion nodes in addition to IPv4 and IPv6 nodes?] ( {{bse}}127727 )
7878 Pieter Wuille clarifies that setting the ` onion ` configuration option only
7979 applies to outbound peer connections. He goes on to outline how to configure
80- [ Tor] [ topic anonymity networks ] and ` bitcoind ` for inbound connections.
80+ [ Tor] [ topic anonymity networks ] and ` bitcoind ` for inbound connections. {% assign timestamp="53:45" %}
8181
8282## Releases and release candidates
8383
@@ -86,10 +86,10 @@ projects. Please consider upgrading to new releases or helping to test
8686release candidates._
8787
8888- [ Bitcoin Core 29.1rc2] [ ] is a release candidate for a maintenance
89- version of the predominant full node software.
89+ version of the predominant full node software. {% assign timestamp="54:22" %}
9090
9191- [ Core Lightning v25.09rc4] [ ] is a release candidate for a new major
92- version of this popular LN node implementation.
92+ version of this popular LN node implementation. {% assign timestamp="56:45" %}
9393
9494## Notable code and documentation changes
9595
@@ -109,28 +109,28 @@ repo], and [BINANAs][binana repo]._
109109 manages and submits block templates to experiment with the multiprocess layout
110110 without custom builds. For additional context on the multiprocess project and
111111 the ` bitcoin-node ` binary, see Newsletters [ #99 ] [ news99 ipc ] , [ #147 ] [ news147
112- ipc] , [ #320 ] [ news320 ipc ] , [ #323 ] [ news323 ipc ] .
112+ ipc] , [ #320 ] [ news320 ipc ] , [ #323 ] [ news323 ipc ] . {% assign timestamp="57:37" %}
113113
114114- [ LDK #3979 ] [ ] adds splice-out support, enabling an LDK node to both initiate a
115115 splice-out transaction, and accept requests from a counterparty. This
116116 completes LDK’s [ splicing] [ topic splicing ] implementation, as [ LDK #3736 ] [ ]
117117 already added splice-in support. This PR adds a ` SpliceContribution ` enum that
118118 covers both in and out scenarios and ensures that the output values of a
119119 splice-out transaction don’t exceed the user’s channel balance after
120- accounting for fees and reserve requirements.
120+ accounting for fees and reserve requirements. {% assign timestamp="1:04:46" %}
121121
122122- [ LND #10102 ] [ ] adds a ` gossip.ban-threshold ` option (100 is the default, 0
123123 disables it) that allows users to configure the score threshold at which a
124124 peer is banned for sending invalid [ gossip] [ topic channel announcements ]
125125 messages. The peer banning system was previously introduced and covered in
126126 [ Newsletter #319 ] [ news319 ban ] . This PR also resolves an issue where
127127 unnecessary node and [ channel announcement] [ topic channel announcements ]
128- messages were sent in response to a backlog gossip query request.
128+ messages were sent in response to a backlog gossip query request. {% assign timestamp="1:06:19" %}
129129
130130- [ Rust Bitcoin #4907 ] [ ] introduces script tagging by adding a new generic tag
131131 parameter ` T ` to ` Script ` and ` ScriptBuf ` , and defines the type aliases
132132 ` ScriptPubKey ` , ` ScriptSig ` , ` RedeemScript ` , ` WitnessScript ` , and ` TapScript `
133- which are backed by a sealed ` Tag ` trait for compile-time role safety.
133+ which are backed by a sealed ` Tag ` trait for compile-time role safety. {% assign timestamp="1:07:04" %}
134134
135135{% include snippets/recap-ad.md when="2025-09-02 16:30" %}
136136{% include references.md %}
0 commit comments