Skip to content

Commit 9988cc3

Browse files
committed
News362: whitespace-only reflow to Gustavojfe section
1 parent 76da6ff commit 9988cc3

File tree

1 file changed

+23
-5
lines changed

1 file changed

+23
-5
lines changed

_posts/en/newsletters/2025-07-11-newsletter.md

Lines changed: 23 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -104,11 +104,29 @@ Proposals (BIPs)][bips repo], [Lightning BOLTs][bolts repo],
104104
[Lightning BLIPs][blips repo], [Bitcoin Inquisition][bitcoin inquisition
105105
repo], and [BINANAs][binana repo]._
106106

107-
- [Core Lightning #8377][] tightens [BOLT11][] invoice parsing requirements by mandating that senders not pay an invoice if a [payment secret][topic payment secrets] is missing or if a mandatory field such as p (payment hash), h (description hash), or s (secret), has an incorrect length. These changes are made to align with the recent specification updates (see Newsletters [#350][news350 bolts] and [#358][news358 bolts]).
108-
109-
- [BDK #1957][] introduces RPC batching for transaction history, merkle proofs, and block header requests to optimize full scan and sync performance with an Electrum backend. This PR also adds anchor caching to skip Simple Payment Verification (SPV) (see Newsletter [#312][news312 spv]) revalidation during a sync. Using sample data, the author observed performance improvements of 8.14 seconds to 2.59 seconds with RPC call batching on a full scan and of 1.37 seconds to 0.85 seconds with caching during a sync.
110-
111-
- [BIPs #1888][] removes `H` as a hardened-path marker from [BIP380][], leaving just the canonical `h` and the alternative `'`. The recent Newsletter [#360][news360 bip380] had noted that grammar was clarified to allow all three markers, but since few (if any) descriptor implementations actually support it (neither Bitcoin Core nor rust-miniscript do), the specification is tightened to disallow it.
107+
- [Core Lightning #8377][] tightens [BOLT11][] invoice parsing
108+
requirements by mandating that senders not pay an invoice if a
109+
[payment secret][topic payment secrets] is missing or if a mandatory
110+
field such as p (payment hash), h (description hash), or s (secret),
111+
has an incorrect length. These changes are made to align with the
112+
recent specification updates (see Newsletters [#350][news350 bolts]
113+
and [#358][news358 bolts]).
114+
115+
- [BDK #1957][] introduces RPC batching for transaction history, merkle
116+
proofs, and block header requests to optimize full scan and sync
117+
performance with an Electrum backend. This PR also adds anchor caching
118+
to skip Simple Payment Verification (SPV) (see Newsletter
119+
[#312][news312 spv]) revalidation during a sync. Using sample data,
120+
the author observed performance improvements of 8.14 seconds to 2.59
121+
seconds with RPC call batching on a full scan and of 1.37 seconds to
122+
0.85 seconds with caching during a sync.
123+
124+
- [BIPs #1888][] removes `H` as a hardened-path marker from [BIP380][],
125+
leaving just the canonical `h` and the alternative `'`. The recent
126+
Newsletter [#360][news360 bip380] had noted that grammar was clarified
127+
to allow all three markers, but since few (if any) descriptor
128+
implementations actually support it (neither Bitcoin Core nor
129+
rust-miniscript do), the specification is tightened to disallow it.
112130

113131
{% include snippets/recap-ad.md when="2025-07-15 16:30" %}
114132
{% include references.md %}

0 commit comments

Comments
 (0)