@@ -24,7 +24,7 @@ popular Bitcoin infrastructure software.
24
24
disclosed] [ topic responsible disclosures ] . An attacker could
25
25
repeatedly request historic gossip messages from an LND node until it
26
26
ran out of memory and was terminated. The vulnerability was fixed in
27
- LND 0.18.3, released September 2024.
27
+ LND 0.18.3, released September 2024. {% assign timestamp="0:53" %}
28
28
29
29
- ** Chain code withholding for multisig scripts:** Jurvis Tan
30
30
[ posted] [ tan ccw ] to Delving Bitcoin about research he performed with
@@ -76,7 +76,7 @@ popular Bitcoin infrastructure software.
76
76
77
77
Some providers may require that the change output for a spending
78
78
transaction sends the money back to the same script template. Tan's
79
- post describes how this can easily be accomplished.
79
+ post describes how this can easily be accomplished. {% assign timestamp="15:16" %}
80
80
81
81
- ** Research indicates common Bitcoin primitives are compatible with quantum-resistant signature algorithms:**
82
82
Jesse Posner [ posted] [ posner qc ] to Delving Bitcoin several links to
@@ -85,7 +85,7 @@ popular Bitcoin infrastructure software.
85
85
those currently used in Bitcoin for [ BIP32 HD wallets] [ topic bip32 ] ,
86
86
[ silent payment addresses] [ topic silent payments ] , [ scriptless
87
87
multisignatures] [ topic multisignature ] , and [ scriptless threshold
88
- signatures] [ topic threshold signature ] .
88
+ signatures] [ topic threshold signature ] . {% assign timestamp="38:46" %}
89
89
90
90
## Selected Q&A from Bitcoin Stack Exchange
91
91
@@ -100,16 +100,16 @@ answers posted since our last update.*
100
100
101
101
- [ How does Bitcoin Core handle reorgs larger than 10 blocks?] ( {{bse}}127512 )
102
102
TheCharlatan links to Bitcoin Core code that handles chain reorganizations by
103
- only re-adding a maximum of 10 blocks worth of transactions to the mempool.
103
+ only re-adding a maximum of 10 blocks worth of transactions to the mempool. {% assign timestamp="57:36" %}
104
104
105
105
- [ Advantages of a signing device over an encrypted drive?] ( {{bse}}127596 )
106
106
RedGrittyBrick points out that data on an encrypted drive can be extracted
107
107
while the drive is unencrypted whereas hardware signing devices are designed to
108
- prevent this data extraction attack.
108
+ prevent this data extraction attack. {% assign timestamp="1:01:29" %}
109
109
110
110
- [ Spending a taproot output through the keypath and scriptpath?] ( {{bse}}127601 )
111
111
Antoine Poinsot details how the use of merkle trees, key tweaks, and leaf
112
- scripts achieves taproot's keypath and scriptpath spending capabilities.
112
+ scripts achieves taproot's keypath and scriptpath spending capabilities. {% assign timestamp="1:03:21" %}
113
113
114
114
## Releases and release candidates
115
115
@@ -119,7 +119,7 @@ release candidates._
119
119
120
120
- [ Libsecp256k1 v0.7.0] [ ] is a release of this library containing
121
121
cryptographic primitives compatible with Bitcoin. It contains a few
122
- small changes that break API/ABI compatibility with previous releases.
122
+ small changes that break API/ABI compatibility with previous releases. {% assign timestamp="1:04:36" %}
123
123
124
124
## Notable code and documentation changes
125
125
@@ -138,7 +138,7 @@ repo], and [BINANAs][binana repo]._
138
138
enforce the limit at the consensus level. If the softfork took place without
139
139
this change, miners who don’t upgrade could become targets of trivial DoS
140
140
attacks. See Newsletter [ #340 ] [ news340 sigops ] for additional details on the
141
- legacy input sigops limit.
141
+ legacy input sigops limit. {% assign timestamp="1:05:16" %}
142
142
143
143
- [ Bitcoin Core #31829 ] [ ] adds resource limits to the orphan transaction
144
144
handler, ` TxOrphanage ` (See Newsletter [ #304 ] [ news304 orphan ] ), to preserve
@@ -152,29 +152,29 @@ repo], and [BINANAs][binana repo]._
152
152
` ‑maxorphantxs ` option (default 100), whose policy of evicting random
153
153
announcements allowed attackers to replace the entire orphan set and render
154
154
[ 1p1c relay] [ 1p1c relay ] useless. See also [ Newsletter #362 ] [ news362
155
- orphan] .
155
+ orphan] . {% assign timestamp="1:15:00" %}
156
156
157
157
- [ LDK #3801 ] [ ] extends [ attributable failures] [ topic attributable failures ] to
158
158
the payment success path by recording how long a node holds an [ HTLC] [ topic
159
159
htlc] and propagating those hold‑time values upstream in the attribution
160
160
payload. Previously, LDK only tracked hold times for failed payments (see
161
- Newsletter [ #349 ] [ news349 attributable ] ).
161
+ Newsletter [ #349 ] [ news349 attributable ] ). {% assign timestamp="1:19:51" %}
162
162
163
163
- [ LDK #3842 ] [ ] extends its [ interactive transaction construction] [ topic dual
164
164
funding] state machine (See Newsletter [ #295 ] [ news295 dual ] ) to handle the
165
165
signing coordination for shared inputs in [ splicing] [ topic splicing ]
166
166
transactions. The ` prevtx ` field of the ` TxAddInput ` message is made optional
167
- to reduce memory usage and simplify validation.
167
+ to reduce memory usage and simplify validation. {% assign timestamp="1:21:11" %}
168
168
169
169
- [ BIPs #1890 ] [ ] changes the separator parameter from ` + ` to ` - ` in [ BIP77] [ ]
170
170
because some HTML 2.0 URI libraries treat ` + ` as if it is a blank space. In
171
171
addition, fragment parameters must now be ordered lexicographically, rather
172
- than in reverse, to simplify the async [ payjoin] [ topic payjoin ] protocol.
172
+ than in reverse, to simplify the async [ payjoin] [ topic payjoin ] protocol. {% assign timestamp="1:21:57" %}
173
173
174
174
- [ BOLTs #1232 ] [ ] makes the ` channel_type ` field (see Newsletter [ #165 ] [ news165
175
175
type] ) mandatory when opening a channel because every implementation enforces
176
176
it. This PR also updates [ BOLT9] [ ] by adding a new context type ` T ` for
177
- features that can be included in the ` channel_type ` field.
177
+ features that can be included in the ` channel_type ` field. {% assign timestamp="1:23:53" %}
178
178
179
179
{% include snippets/recap-ad.md when="2025-07-29 16:30" %}
180
180
{% include references.md %}
0 commit comments