Podcast: add 371 recap

Author: bitschmidty

_posts/en/newsletters/2025-09-12-newsletter.md

@@ -20,7 +20,7 @@ software.
   day event to "teach developers the basics of provable cryptography,
   [...] consisting of cryptographic definitions, propositions, proofs
   and exercises."  The workbook is available as a [PDF][workbook pdf]
-  with freely licensesd [source][workbook source].
+  with freely licensesd [source][workbook source]. {% assign timestamp="0:48" %}
 
 ## Releases and release candidates
 
@@ -29,7 +29,7 @@ projects.  Please consider upgrading to new releases or helping to test
 release candidates._
 
 - [Bitcoin Core 29.1][] is the release of a maintenance
-  version of the predominant full node software.
+  version of the predominant full node software. {% assign timestamp="10:48" %}
 
 - [Eclair v0.13.0][] is the release of this LN node implementation.  It
   "s release contains a lot of refactoring, an initial implementation of
@@ -39,10 +39,10 @@ release candidates._
   they should not be used by regular users.  The release notes also
   warn: "This is the last release of eclair where channels that don't
   use anchor outputs will be supported.  If you have channels that don't
-  use anchor outputs, you should close them."
+  use anchor outputs, you should close them." {% assign timestamp="11:17" %}
 
 - [Bitcoin Core 30.0rc1][] is a release candidate for the next major
-  version of this full verification node software.
+  version of this full verification node software. {% assign timestamp="25:27" %}
 
 ## Notable code and documentation changes
 
@@ -62,42 +62,42 @@ repo], and [BINANAs][binana repo]._
   the default [signet][topic signet]. The new version of the coinstats index is
   stored in `/indexes/coinstatsindex/` and an upgraded node will need to sync
   from scratch to rebuild the index. The old version is kept for downgrade
-  protection, but may be removed in a future update.
+  protection, but may be removed in a future update. {% assign timestamp="33:18" %}
 
 - [Eclair #3163][] adds a test vector to ensure that a payee’s public key can be
   recovered from a [BOLT11][] invoice with a high-S signature, in addition to
   already allowing low-S signatures. This aligns with the behaviour of
-  libsecp256k1 and the proposed [BOLTs #1284][].
+  libsecp256k1 and the proposed [BOLTs #1284][]. {% assign timestamp="33:18" %}
 
 - [Eclair #2308][] introduces a new `use-past-relay-data` option that when set
   to true (default false), uses a probabilistic approach based on past
   payment attempt history to improve pathfinding. This replaces a prior method
-  that assumed uniformity in channel balances.
+  that assumed uniformity in channel balances. {% assign timestamp="40:27" %}
 
 - [Eclair #3021][] allows the non-initiator of a [dual-funded channel][topic
   dual funding] to [RBF][topic rbf] the funding transaction, which is already
   allowed in [splicing][topic splicing] transactions. However, an exception
   applies to [liquidity advertisement][topic liquidity advertisements] purchase
-  transactions. This has been proposed in [BOLTs #1236][].
+  transactions. This has been proposed in [BOLTs #1236][]. {% assign timestamp="45:18" %}
 
 - [Eclair #3142][] adds a new `maxClosingFeerateSatByte` parameter to the
   `forceclose` API endpoint that overrides the global feerate configuration
   for non-urgent force close transactions on a per-channel basis. The global
-  setting `max-closing-feerate` was introduced in [Eclair #3097][].
+  setting `max-closing-feerate` was introduced in [Eclair #3097][]. {% assign timestamp="48:08" %}
 
 - [LDK #4053][] introduces zero-fee commitment channels by replacing the two
   anchor outputs with one shared [Pay-to-Anchor (P2A)][topic ephemeral anchors]
   output, capped at a value of 240 sats. Additionally, it switches [HTLC][topic
   htlc] signatures in zero-fee commitment channels to
   `SIGHASH_SINGLE|ANYONECANPAY` and bumps HTLC transactions to [version 3][topic
-  v3 transaction relay].
+  v3 transaction relay]. {% assign timestamp="50:30" %}
 
 - [LDK #3886][] extends `channel_reestablish` for [splicing][topic splicing] with
   two `funding_locked_txid` TLVs (what a node last sent and received) so that
   peers can reconcile the active funding transaction upon reconnecting.
   Additionally, it streamlines the reconnection process by resending
   `commitment_signed` before `tx_signatures`, handling implicit `splice_locked`,
-  adopting `next_funding`, and requesting announcement signatures as needed.
+  adopting `next_funding`, and requesting announcement signatures as needed. {% assign timestamp="58:12" %}
 
 {% include snippets/recap-ad.md when="2025-09-16 16:30" %}
 {% include references.md %}

_posts/en/podcast/2025-09-16-newsletter-recap.md

@@ -0,0 +1,24 @@
+---
+title: 'Bitcoin Optech Newsletter #371 Recap Podcast'
+permalink: /en/podcast/2025/09/16/
+reference: /en/newsletters/2025/09/12/
+name: 2025-09-16-recap
+slug: 2025-09-16-recap
+type: podcast
+layout: podcast-episode
+lang: en
+---
+Mark “Murch” Erhardt and Mike Schmidt are joined by Jonas Nick and Bastien
+Teinturier to discuss [Newsletter #370]({{page.reference}}).
+
+{% include functions/podcast-links.md %}
+
+{% include functions/podcast-player.md url="https://d3ctxlq1ktw2nl.cloudfront.net/staging/2025-8-16/407600787-44100-2-853167a259869.m4a" %}
+
+{% include newsletter-references.md %}
+
+## Transcription
+
+_transcription coming soon_
+
+{% include references.md %}