@@ -188,19 +188,42 @@ Proposals (BIPs)][bips repo], [Lightning BOLTs][bolts repo],
188
188
[ Lightning BLIPs] [ blips repo ] , [ Bitcoin Inquisition] [ bitcoin inquisition
189
189
repo] , and [ BINANAs] [ binana repo ] ._
190
190
191
- - [ Bitcoin Core #29954 ] [ ] RPC: Return ` permitbaremultisig ` and ` maxdatacarriersize ` in ` getmempoolinfo `
192
-
193
- - [ Bitcoin Core #33004 ] [ ] Enable ` -natpmp ` by default
194
-
195
- - [ LDK #3246 ] [ ] Enable Creation of Offers and Refunds Without Blinded Path
196
-
197
- - [ LDK #3892 ] [ ] offer: make the merkle tree signature public
198
-
199
- - [ LDK #3662 ] [ ] LSPS5 implementation
191
+ - [ Bitcoin Core #29954 ] [ ] extends the ` getmempoolinfo ` RPC by adding two relay
192
+ policy fields to its response object: ` permitbaremultisig ` (whether the node
193
+ relays bare multisig outputs) and ` maxdatacarriersize ` (the maximum aggregate
194
+ bytes allowed in OP_RETURN outputs for a transaction in the mempool). Other
195
+ policy flags, such as [ ` fullrbf ` ] [ topic rbf ] and ` minrelaytxfee ` , were already
196
+ exposed, so these additions allow for a complete relay policy snapshot.
197
+
198
+ - [ Bitcoin Core #33004 ] [ ] enables the ` -natpmp ` option by default, allowing
199
+ automatic port forwarding via the [ Port Control Protocol (PCP)] [ pcp ] with a
200
+ fallback to the [ NAT Port Mapping Protocol (NAT-PMP)] [ natpmp ] (see Newsletter
201
+ [ #323 ] [ news323 natpmp ] ). A listening node behind a router that supports either
202
+ PCP or NAT-PMP becomes reachable without manual configuration.
203
+
204
+ - [ LDK #3246 ] [ ] enables the creation of [ BOLT12 offers] [ topic offers ] and
205
+ refunds without a [ blinded path] [ topic rv routing ] by using the offer’s
206
+ ` signing_pubkey ` as the destination. The ` create_offer_builder ` and
207
+ ` create_refund_builder ` functions now delegate blinded path creation to
208
+ ` MessageRouter::create_blinded_paths ` , where a caller can generate a compact
209
+ path by passing ` DefaultMessageRouter ` , a full-length pubkey path with
210
+ ` NodeIdMessageRouter ` , or no path at all with ` NullMessageRouter ` .
211
+
212
+ - [ LDK #3892 ] [ ] exposes the merkle tree signature of [ BOLT12] [ topic offers ]
213
+ invoices publicly, enabling developers to build CLI tools or other software to
214
+ verify the signature or recreate invoices. This PR also adds an ` OfferId `
215
+ field to BOLT12 invoices to track the originating offer.
216
+
217
+ - [ LDK #3662 ] [ ] implements [ BLIPs #55 ] [ ] , also known as LSPS05, which defines
218
+ how clients can register for webhooks via an endpoint to receive push
219
+ notifications from an LSP. The API exposes additional endpoints that enable
220
+ clients to list all webhook registrations or remove a specific one. This can
221
+ be useful for clients to get notified when receiving an [ async payment] [ topic
222
+ async payments] .
200
223
201
224
{% include snippets/recap-ad.md when="2025-08-05 16:30" %}
202
225
{% include references.md %}
203
- {% include linkers/issues.md v=2 issues="29954,33004,3246,3892,3662" %}
226
+ {% include linkers/issues.md v=2 issues="29954,33004,3246,3892,3662,55 " %}
204
227
[ bitcoin core 29.1rc1 ] : https://bitcoincore.org/bin/bitcoin-core-29.1/
205
228
[ augur #3 ] : https://github.com/block/bitcoin-augur/issues/3
206
229
[ news315 cb ] : /en/newsletters/2024/08/09/#statistics-on-compact-block-reconstruction
@@ -222,3 +245,6 @@ repo], and [BINANAs][binana repo]._
222
245
[ news348 destroy ] : /en/newsletters/2025/04/04/#should-vulnerable-bitcoins-be-destroyed
223
246
[ black th ] : https://mailing-list.bitcoindevs.xyz/bitcoindev/aG9FEHF1lZlK6d0E@console/
224
247
[ news361 bitvm ] : /en/newsletters/2025/07/04/#continued-discussion-about-ctv-csfs-advantages-for-bitvm
248
+ [ news323 natpmp ] : /en/newsletters/2024/10/04/#bitcoin-core-30043
249
+ [ pcp ] : https://datatracker.ietf.org/doc/html/rfc6887
250
+ [ natpmp ] : https://datatracker.ietf.org/doc/html/rfc6886
0 commit comments