@@ -39,7 +39,7 @@ popular Bitcoin infrastructure software
3939 the race condition from crashing the node.
4040
4141 For more information, we recommend reading Morehouse's excellent
42- [ full disclosure] [ morehouse full ] blog post.
42+ [ full disclosure] [ morehouse full ] blog post. {% assign timestamp="2:15" %}
4343
4444- ** New LNHANCE combination soft fork proposed:** Brandon Black
4545 [ posted] [ black lnhance ] to Delving Bitcoin details about a soft fork
@@ -63,7 +63,7 @@ popular Bitcoin infrastructure software
6363 CTV-style congestion control and CSFS-style signature delegation.
6464
6565 As of this writing, technical discussion was limited to the request
66- about what protocols the combination proposal would enable.
66+ about what protocols the combination proposal would enable. {% assign timestamp="4:59" %}
6767
6868- ** Proposal for 64-bit arithmetic soft fork:** Chris Stewart
6969 [ posted] [ stewart 64 ] a [ draft BIP] [ bip 64 ] to Delving Bitcoin for
@@ -81,7 +81,7 @@ popular Bitcoin infrastructure software
8181 proposal, such as how to encode the integer value, what
8282 [ taproot] [ topic taproot ] upgrade feature to use, and whether
8383 creating a new set of arithmetic opcodes is preferred to upgrading
84- existing ones.
84+ existing ones. {% assign timestamp="21:08" %}
8585
8686- ** Overview of cluster mempool proposal:** Suhas Daftuar
8787 [ posted] [ daftuar cluster ] a summary of the [ cluster mempool] [ topic
@@ -129,7 +129,7 @@ popular Bitcoin infrastructure software
129129 developers working on software for mining, wallets, or contract
130130 protocols to read Daftuar's description and ask questions about
131131 anything that's not clear or which might adversely affect how Bitcoin
132- software will interact with cluster mempool.
132+ software will interact with cluster mempool. {% assign timestamp="38:25" %}
133133
134134- ** Updated specification and implementation of Bitcoin transaction compression:**
135135 Tom Briar [ posted] [ briar compress ] to the Bitcoin-Dev mailing list an
@@ -142,7 +142,7 @@ popular Bitcoin infrastructure software
142142 original proposal. Briar describes the notable changes: "removing the
143143 grinding of the nLocktime in favor of a relative block height, which
144144 all of the compressed inputs use, and the use of a second kind of
145- variable integer."
145+ variable integer." {% assign timestamp="45:22" %}
146146
147147- ** Discussion of Miner Extractable Value (MEV) in non-zero ephemeral anchors:**
148148 Gregory Sanders [ posted] [ sanders mev ] to Delving Bitcoin to discuss
@@ -195,7 +195,7 @@ popular Bitcoin infrastructure software
195195 to miners in a way that ensures all miners and relay nodes can
196196 obtain the same set of transactions.
197197
198- No clear conclusion seemed to have been reached at the time of writing.
198+ No clear conclusion seemed to have been reached at the time of writing. {% assign timestamp="46:51" %}
199199
200200## Releases and release candidates
201201
@@ -206,7 +206,7 @@ release candidates.*
206206- [ LDK 0.0.119] [ ] is a new release of this library for building
207207 LN-enabled applications. Multiple new features are added, including
208208 receiving payments to multi-hop [ blinded paths] [ topic rv routing ] ,
209- along with multiple bug fixes and other improvements.
209+ along with multiple bug fixes and other improvements. {% assign timestamp="56:24" %}
210210
211211## Notable code and documentation changes
212212
@@ -224,21 +224,21 @@ Proposals (BIPs)][bips repo], [Lightning BOLTs][bolts repo], and
224224 ` -seednode ` configuration arguments if ` -v2transport ` is enabled and
225225 reconnects with v1 if the peer does not support v2. Additionally,
226226 this update adds a column displaying the transport protocol version
227- to the ` netinfo ` peer connection ` bitcoin-cli ` dashboard.
227+ to the ` netinfo ` peer connection ` bitcoin-cli ` dashboard. {% assign timestamp="57:17" %}
228228
229229- [ Bitcoin Core #29200 ] [ ] allows the [ I2P network support] [ topic
230230 anonymity networks] to use connections encrypted using "ECIES-X25519
231231 and ElGamal (types 4 and, 0, respectively). This allows to connect to
232232 I2P peers of either type, and the newer, faster ECIES-X25519 will be
233- preferred."
233+ preferred." {% assign timestamp="58:59" %}
234234
235235- [ Bitcoin Core #28890 ] [ ] removes the ` -rpcserialversion ` configuration
236236 parameter that was previously deprecated (see [ Newsletter
237237 #269 ] [ news269 rpc ] ). This option was introduced during the transition
238238 to v0 segwit to allow older programs to continue to access blocks and
239239 transactions in stripped format (without any segwit fields). At this
240240 point, all programs should be updated to handle segwit transactions
241- and this option should no longer be needed.
241+ and this option should no longer be needed. {% assign timestamp="1:00:08" %}
242242
243243- [ Eclair #2808 ] [ ] updates the ` open ` command with a
244244 ` --fundingFeeBudgetSatoshis ` parameter that defines the maximum amount
@@ -247,15 +247,15 @@ Proposals (BIPs)][bips repo], [Lightning BOLTs][bolts repo], and
247247 try to pay a lower fee if possible, but it will pay up to the budgeted
248248 amount if necessary. The ` rbfopen ` command is also updated to accept
249249 the same parameter which defines the maximum amount to spend on [ RBF
250- fee bumping] [ topic rbf ] .
250+ fee bumping] [ topic rbf ] . {% assign timestamp="1:01:25" %}
251251
252252- [ LND #8188 ] [ ] adds several new RPCs for quickly obtaining debugging
253253 information, encrypting it to a public key, and decrypting it given a
254254 private key. As the PR explains, "The idea is that we would publish a
255255 public key in the GitHub issue template and would ask users to run the
256256 ` lncli encryptdebugpackage ` command and upload the encrypted output
257257 files to the GitHub issue to provide us with the information we
258- normally require to debug user problems."
258+ normally require to debug user problems." {% assign timestamp="1:02:09" %}
259259
260260- [ LND #8096 ] [ ] adds a "fee spike buffer". In the current LN protocol,
261261 the party who single-funded a channel is responsible for paying
@@ -272,11 +272,11 @@ Proposals (BIPs)][bips repo], [Lightning BOLTs][bolts repo], and
272272 funds to ensure an additional payment can be received even if feerates
273273 rise. LND now implements this solution, which is also implemented by
274274 Core Lightning and Eclair (see Newsletters [ #85 ] [ news85 stuck ] and
275- [ #89 ] [ news89 stuck ] ).
275+ [ #89 ] [ news89 stuck ] ). {% assign timestamp="1:07:44" %}
276276
277277- [ LND #8095 ] [ ] and [ #8142 ] [ lnd #8142 ] add additional logic to parts of
278278 LND's codebase for handling [ blinded paths] [ topic rv routing ] . This is
279- part of ongoing work to add full support for blinded paths to LND.
279+ part of ongoing work to add full support for blinded paths to LND. {% assign timestamp="1:09:08" %}
280280
281281{% assign day_after_posting = page.date | date: "%s" | plus: 86400 | date: "%Y-%m-%d 15:00" %}
282282{% include snippets/recap-ad.md when=day_after_posting %}
0 commit comments