@@ -23,7 +23,7 @@ infrastructure projects.
2323 potential algorithms along with their expected onchain size. The
2424 choice of algorithms and the specific implementation details are
2525 left for future discussion, as are additional BIPs necessary to fully
26- realize the vision of adding full quantum resistance to Bitcoin.
26+ realize the vision of adding full quantum resistance to Bitcoin. {% assign timestamp="3:36" %}
2727
2828## Bitcoin Core PR Review Club
2929
@@ -58,6 +58,8 @@ second time. [Bitcoin Core #30132][] can make node startup more
5858efficient by avoiding the wiping of the optional indexes when not
5959necessary.
6060
61+ {% assign timestamp="23:28" %}
62+
6163{% include functions/details-list.md
6264 q0="What is the behavior change introduced by this PR?"
6365 a0="Behaviour is changed in three ways. First, as per the goal of this
@@ -108,10 +110,10 @@ release candidates.*
108110 [ offer] [ topic offers ] invoices (see [ Newsletter #304 ] [ news304 cln
109111 offers] ), and a fix for a fee overpayment issue when the
110112 ` ignore_fee_limits ` configuration option is used (see [ Newsletter
111- #306 ] [ news306 cln overpay ] ).
113+ #306 ] [ news306 cln overpay ] ). {% assign timestamp="30:45" %}
112114
113115- [ Bitcoin Core 27.1] [ ] is a maintenance release of the predominant
114- full node implementation. It contains multiple bug fixes.
116+ full node implementation. It contains multiple bug fixes. {% assign timestamp="32:46" %}
115117
116118## Notable code and documentation changes
117119
@@ -129,42 +131,42 @@ repo], and [BINANAs][binana repo]._
129131 relay] ) transactions standard. If a transaction’s version is 3, it will be
130132 treated as a TRUC transaction as defined in the [ BIP431] [ ] specification. The
131133 ` CURRENT_VERSION ` remains 2, meaning the wallet will not create TRUC
132- transactions yet.
134+ transactions yet. {% assign timestamp="34:48" %}
133135
134136- [ Bitcoin Core #28307 ] [ ] fixes a bug that imposed the 520-byte P2SH maximum
135137 script size limit on SegWit redeem scripts for both P2SH-segwit and bech32.
136138 This fix enables the creation of multisig [ output descriptors] [ topic
137139 descriptors] involving more than 15 keys (now allowing up to the ` OP_CHECKMULTISIG ` consensus limit of 20), including
138140 signing for these scripts, along with other post-segwit redeem scripts that
139- exceed the P2SH limit.
141+ exceed the P2SH limit. {% assign timestamp="38:58" %}
140142
141143- [ Bitcoin Core #30047 ] [ ] refactors the model of the [ bech32] [ topic bech32 ] encoding scheme
142144 ` charlimit ` from a constant of 90 to an ` Enum ` . This change allows for easy
143145 support of new address types that use the bech32 encoding scheme but don't
144146 have the same character limit as [ BIP173] [ ] was designed for. For example, to enable
145147 parsing [ silent payment] [ topic silent payments ] addresses, which require up to
146- 118 characters.
148+ 118 characters. {% assign timestamp="37:04" %}
147149
148150- [ Bitcoin Core #28979 ] [ ] updates the documentation of the ` sendall ` RPC
149151 command (see [ Newsletter #194 ] [ news194 sendall ] ) to mention that it spends unconfirmed
150152 change in addition to confirmed
151153 outputs. If unconfirmed outputs are spent, it will compensate for any
152- _ fee deficit_ (see [ Newsletter #269 ] [ news269 deficit ] ). _ This item was corrected after publication._ [ ^ correction-28979 ]
154+ _ fee deficit_ (see [ Newsletter #269 ] [ news269 deficit ] ). _ This item was corrected after publication._ [ ^ correction-28979 ] {% assign timestamp="41:23" %}
153155
154156- [ Eclair #2854 ] [ ] and [ LDK #3083 ] [ ] implement [ BOLTs #1163 ] [ ] to remove the
155157 requirement of a ` channel_update ` on an [ onion message] [ topic onion messages ]
156158 delivery failure. This requirement facilitated an attack where a relayer node
157159 that generated the delivery failure error status could identify the sender of
158160 the [ HTLC] [ topic htlc ] through the ` channel_update ` field, compromising the
159- sender’s privacy.
161+ sender’s privacy. {% assign timestamp="43:12" %}
160162
161163- [ LND #8491 ] [ ] adds a ` cltv_expiry ` flag on the ` lncli ` RPC commands
162164 ` addinvoice ` and ` addholdinvoice ` to allow users to set the
163165 ` min_final_cltv_expiry_delta ` (the [ CLTV expiry delta] [ topic cltv expiry delta ] for the last hop).
164166 No motivation for the change is described on the pull request, but it
165167 could be in response to LND recently raising its default from 9 blocks
166168 to 18 blocks to follow the [ BOLT2] [ ] specification (see [ Newsletter
167- #284 ] [ news284 lnd final delta ] ).
169+ #284 ] [ news284 lnd final delta ] ). {% assign timestamp="44:23" %}
168170
169171- [ LDK #3080 ] [ ] refactors ` MessagerRouter ` ’s ` create_blinded_path ` command into
170172 two methods: one for compact [ blinded path] [ topic rv routing ] creation, and
@@ -182,7 +184,7 @@ repo], and [BINANAs][binana repo]._
182184 onion messages don't require channels).
183185 ` ChannelManager ` is updated to use compact blinded paths for short-lived
184186 [ offers] [ topic offers ] and refunds, while reply paths are refactored to use
185- normal (non-compact) blinded paths.
187+ normal (non-compact) blinded paths. {% assign timestamp="45:41" %}
186188
187189- [ BIPs #1551 ] [ ] adds [ BIP353] [ ] with a specification for DNS Payment Instructions,
188190 a protocol to encode [ BIP21] [ ] URIs in DNS TXT records, for
@@ -192,7 +194,7 @@ repo], and [BINANAs][binana repo]._
192194 DNSSEC-signed TXT record containing a BIP21 URI like
193195 ` bitcoin:bc1qexampleaddress0123456 ` . See [ Newsletter #290 ] [ news290
194196 bip353] for our previous description and [ last week's newsletter] [ news306
195- dns] for the merge of a related BLIP.
197+ dns] for the merge of a related BLIP. {% assign timestamp="47:13" %}
196198
197199{% assign four_days_after_posting = page.date | date: "%s" | plus: 345600 | date: "%Y-%m-%d 14:30" %}
198200{% include snippets/recap-ad.md when=four_days_after_posting %}
0 commit comments