@@ -24,14 +24,6 @@ the meeting.*
2424
2525FIXME: stickies-v
2626
27- ## Releases and release candidates
28-
29- _ New releases and release candidates for popular Bitcoin infrastructure
30- projects. Please consider upgrading to new releases or helping to test
31- release candidates._
32-
33- FIXME: Gustavojfe
34-
3527## Notable code and documentation changes
3628
3729_ Notable recent changes in [ Bitcoin Core] [ bitcoin core repo ] , [ Core
@@ -43,8 +35,69 @@ Proposals (BIPs)][bips repo], [Lightning BOLTs][bolts repo],
4335[ Lightning BLIPs] [ blips repo ] , [ Bitcoin Inquisition] [ bitcoin inquisition
4436repo] , and [ BINANAs] [ binana repo ] ._
4537
46- FIXME: Gustavojfe
38+ - [ Bitcoin Core #33908 ] [ ] adds ` btck_check_block_context_free ` to the
39+ ` libbitcoinkernel ` C API (see [ Newsletter #380 ] [ news380 kernel ] ) for
40+ validating candidate blocks with context-free checks: block size/weight
41+ limits, coinbase rules, and per-transaction checks that do not depend on
42+ chainstate, the block index, or the UTXO set. Callers can optionally enable
43+ proof-of-work verification and merkle-root verification in this endpoint.
44+
45+ - [ Eclair #3283 ] [ ] adds a ` fee ` field (in msats) to the full-format responses
46+ of the ` findroute ` , ` findroutetonode ` , and ` findroutebetweennodes ` endpoints
47+ used for pathfinding. This field provides the route's total
48+ [ forwarding fee] [ topic inbound forwarding fees ] , eliminating the need for
49+ callers to compute it manually.
50+
51+ - [ LDK #4529 ] [ ] enables operators to set different limits for announced and
52+ [ unannounced channels] [ topic unannounced channels ] when configuring the total
53+ value of inbound [ HTLCs] [ topic htlc ] in flight, as a percentage of channel
54+ capacity. The defaults are now 25% for announced channels and 100% for
55+ unannounced channels.
56+
57+ - [ LDK #4494 ] [ ] updates its internal [ RBF] [ topic rbf ] logic to ensure compliance
58+ with [ BIP125] [ ] 's replacement rules at low feerates. Instead of only applying
59+ the 25/24 feerate multiplier specified in [ BOLT2] [ ] , LDK now uses whichever is
60+ larger: that multiplier or an additional 25 sat/kwu. A related specification
61+ clarification is being discussed in [ BOLTs #1327 ] [ ] .
62+
63+ - [ LND #10666 ] [ ] adds a ` DeleteForwardingHistory ` RPC and an `lncli
64+ deletefwdhistory` command, enabling operators to selectively delete forwarding
65+ events older than a chosen cutoff timestamp. A minimum age guard of one hour
66+ prevents the accidental removal of recent data. This feature enables routing
67+ nodes to delete historical forwarding records without resetting the database
68+ or taking the node offline.
69+
70+ - [ BIPs #2099 ] [ ] publishes [ BIP393] [ ] , which specifies an optional annotation
71+ syntax for output script [ descriptors] [ topic descriptors ] , enabling wallets to
72+ store recovery hints, such as a birthday height to speed up wallet scanning
73+ (including for [ silent payment] [ topic silent payments ] scanning). See [ Newsletter
74+ #394 ] [ news394 bip393 ] for initial coverage of this BIP with additional
75+ details.
76+
77+ - [ BIPs #2118 ] [ ] publishes [ BIP440] [ ] and [ BIP441] [ ] as Draft BIPs in the Great
78+ Script Restoration (or Grand Script Renaissance) series (see [ Newsletter #399 ] [ news399 bips ] ).
79+ [ BIP440] [ ] proposes the Varops Budget for Script Runtime Constraint (see
80+ [ Newsletter #374 ] [ news374 varops ] ); [ BIP441] [ ] describes a new
81+ [ tapscript] [ topic tapscript ] version that restores opcodes disabled in 2010
82+ such as [ OP_CAT] [ topic op_cat ] (see [ Newsletter #374 ] [ news374 tapscript ] ) and
83+ limits script evaluation costs per the varops budget introduced in BIP440.
84+
85+ - [ BIPs #2134 ] [ ] updates [ BIP352] [ ] ([ silent payments] [ topic silent payments ] ) to
86+ warn wallet developers not to let policy filtering, such as for
87+ [ dust] [ topic uneconomical outputs ] , affect whether scanning continues after a
88+ match is found. Treating a filtered-out output as if there were no match can
89+ cause the wallet to prematurely stop scanning and miss later outputs from the
90+ same sender.
4791
4892{% include snippets/recap-ad.md when="2026-04-14 16:30" %}
4993{% include references.md %}
50- {% include linkers/issues.md v=2 issues="" %}
94+ {% include linkers/issues.md v=2 issues="33908,3283,4529,4494,10666,2099,2118,2134,1327" %}
95+ [ sources ] : /en/internal/sources/
96+ [ news380 kernel ] : /en/newsletters/2025/11/14/#bitcoin-core-30595
97+ [ news394 bip393 ] : /en/newsletters/2026/02/27/#draft-bip-for-output-script-descriptor-annotations
98+ [ news399 bips ] : /en/newsletters/2026/04/03/#varops-budget-and-tapscript-leaf-0xc2-aka-script-restoration-are-bips-440-and-441
99+ [ news374 varops ] : /en/newsletters/2025/10/03/#first-bip
100+ [ news374 tapscript ] : /en/newsletters/2025/10/03/#second-bip
101+ [ BIP393 ] : https://github.com/bitcoin/bips/blob/master/bip-0393.mediawiki
102+ [ BIP440 ] : https://github.com/bitcoin/bips/blob/master/bip-0440.mediawiki
103+ [ BIP441 ] : https://github.com/bitcoin/bips/blob/master/bip-0441.mediawiki
0 commit comments