@@ -73,6 +73,8 @@ Bitcoin-Dev mailing list.
73
73
attacker's receiving node received an amount extracted from the
74
74
victim's node.
75
75
76
+ {% assign timestamp="1:26" %}
77
+
76
78
As Siegel reports, two changes were made to Bitcoin Core to prevent
77
79
stalling:
78
80
@@ -115,7 +117,7 @@ Bitcoin-Dev mailing list.
115
117
output for CPFP fee bumping now, waiting for [ cluster mempool] [ topic
116
118
cluster mempool] to hopefully allow v3 to permit more permissive
117
119
topologies (i.e., more than just one parent, one child), and then to
118
- drop the extra output in favor of using a more permissive topology.
120
+ drop the extra output in favor of using a more permissive topology. {% assign timestamp="17:08" %}
119
121
120
122
- ** Requirement to verify inputs use segwit in protocols vulnerable to txid malleability:**
121
123
Bastien Teinturier [ posted] [ teinturier segwit ] to Delving Bitcoin to
@@ -172,6 +174,8 @@ Bitcoin-Dev mailing list.
172
174
as much bandwidth as the first procedure.<!-- ~ 4,000,000 byte
173
175
transaction divided by ~ 22 byte P2WPKH scriptPubKey -->
174
176
177
+ {% assign timestamp="27:00" %}
178
+
175
179
- ** Proposal for replace by feerate to escape pinning:** Peter Todd
176
180
[ posted] [ todd rbfr ] to the Bitcoin-Dev mailing list a proposal for a
177
181
set of [ transaction replacement] [ topic rbf ] policies that can be used
@@ -228,12 +232,12 @@ Bitcoin-Dev mailing list.
228
232
229
233
The separate discussions were not reconciled as of this writing.
230
234
Peter Todd has released an experimental [ implementation] [ libre relay ]
231
- of the replace by feerate rules.
235
+ of the replace by feerate rules. {% assign timestamp="35:21" %}
232
236
233
237
- ** Bitcoin-Dev mailing list migration update:** as of this writing, the
234
238
Bitcoin-Dev mailing list is no longer accepting new emails as part of
235
239
the process of migrating it to a different list server (see [ Newsleter #276 ] [ news276 ml ] ). Optech will
236
- provide an update when the migration is complete.
240
+ provide an update when the migration is complete. {% assign timestamp="51:15" %}
237
241
238
242
## Releases and release candidates
239
243
@@ -246,7 +250,7 @@ release candidates.*
246
250
that fixes multiple bugs: Channel open hanging until restart, a memory
247
251
leak when using polling mode for ` bitcoind ` , sync getting lost for
248
252
pruned nodes and the REST proxy not working when TLS certificate
249
- encryption is turned on."
253
+ encryption is turned on." {% assign timestamp="1:00:02" %}
250
254
251
255
## Notable code and documentation changes
252
256
@@ -264,7 +268,7 @@ repo]._
264
268
software. However, the library hasn't seen any significant adoption
265
269
and it has become a burden on maintenance of Bitcoin Core. The plan
266
270
is to "not migrate it to CMake and let it end with v27. Any remaining
267
- use-cases could be handled in the future by [ libbitcoinkernel] [ ] ."
271
+ use-cases could be handled in the future by [ libbitcoinkernel] [ ] ." {% assign timestamp="1:01:13" %}
268
272
269
273
- [ Bitcoin Core #28956 ] [ ] removes adjusted time from Bitcoin Core and
270
274
warns users if their computer's clock appears to be out of sync with the
@@ -275,25 +279,25 @@ repo]._
275
279
give blocks it produced a more accurate time. However, adjusted time
276
280
has also led to problems in the past and does not provide meaningful
277
281
benefits to nodes on the current network. See [ Newsletter
278
- #284 ] [ news284 adjtime ] for previous coverage of this PR.
282
+ #284 ] [ news284 adjtime ] for previous coverage of this PR. {% assign timestamp="1:07:23" %}
279
283
280
284
- [ Bitcoin Core #29347 ] [ ] enables [ v2 P2P transport] [ topic v2 p2p
281
285
transport] by default. New connections between two peers that both
282
- support the v2 protocol will use encryption.
286
+ support the v2 protocol will use encryption. {% assign timestamp="1:10:03" %}
283
287
284
288
- [ Core Lightning #6985 ] [ ] adds options to ` hsmtool ` that allow it to
285
289
return the private keys for the onchain wallet in a way that allows
286
- those keys to be imported into another wallet.
290
+ those keys to be imported into another wallet. {% assign timestamp="1:10:45" %}
287
291
288
292
- [ Core Lightning #6904 ] [ ] makes various updates to CLN's connection
289
293
and gossip management code. A user-visible change is the addition of
290
294
fields that indicate when a peer last had a stable connection to the
291
295
local node for at least a minute. This can allow removing peers with
292
- unstable connections.
296
+ unstable connections. {% assign timestamp="1:12:54" %}
293
297
294
298
- [ Core Lightning #7022 ] [ ] removes ` lnprototest ` from Core Lightning's
295
299
testing infrastructure. See [ Newsletter #145 ] [ news145 lnproto ] for
296
- our description of them being added.
300
+ our description of them being added. {% assign timestamp="1:14:53" %}
297
301
298
302
- [ Core Lightning #6936 ] [ ] adds infrastructure to assist with
299
303
deprecating CLN features. Features are now deprecated in code using
@@ -304,7 +308,7 @@ repo]._
304
308
feature would be reported as deprecated but continued functioning
305
309
by default for a long time after it was planned for removal, possibly
306
310
leading users to continue depending on it and making actual removal
307
- more difficult.
311
+ more difficult. {% assign timestamp="1:16:16" %}
308
312
309
313
- [ LND #8345 ] [ ] begins testing whether transactions are likely to relay
310
314
before broadcasting them by calling a full node's ` testmempoolaccept `
@@ -313,7 +317,7 @@ repo]._
313
317
potentially speeding up the discovery of a problem and limiting the
314
318
potential harm from a bug. Versions of the ` testmempoolaccept ` RPC
315
319
are available in Bitcoin Core, most modern software forks of Bitcoin
316
- Core, and the btcd full node.
320
+ Core, and the btcd full node. {% assign timestamp="1:18:02" %}
317
321
318
322
{% assign day_after_posting = page.date | date: "%s" | plus: 86400 | date: "%Y-%m-%d 15:00" %}
319
323
{% include snippets/recap-ad.md when=day_after_posting %}
0 commit comments