From 9783bfea90e00bd755feb4a291335d804661ff29 Mon Sep 17 00:00:00 2001 From: "Sera (Bartok9)" Date: Mon, 20 Jul 2026 08:28:36 -0400 Subject: [PATCH] News346: correct waitNext() fee_threshold / MAX_MONEY description MAX_MONEY is the default fee_threshold that disables fee-based template updates, not a threshold that mempool fees must exceed. --- _posts/en/newsletters/2025-03-21-newsletter.md | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/_posts/en/newsletters/2025-03-21-newsletter.md b/_posts/en/newsletters/2025-03-21-newsletter.md index 88e1fe7904..26e8b0b5a4 100644 --- a/_posts/en/newsletters/2025-03-21-newsletter.md +++ b/_posts/en/newsletters/2025-03-21-newsletter.md @@ -153,11 +153,14 @@ repo], and [BINANAs][binana repo]._ centralized element. {% assign timestamp="1:03:19" %} - [Bitcoin Core #31283][] introduces a new `waitNext()` method to the - `BlockTemplate` interface, which will only return a new template if the chain - tip changes or the mempool fees increase above the `MAX_MONEY` threshold. - Previously, miners would receive a new template with every request, resulting - in unnecessary template generation. This change aligns with the [Stratum - V2][topic pooled mining] protocol specification. {% assign timestamp="37:27" %} + `BlockTemplate` interface, which returns a new template only when the chain + tip changes or when total fees in a freshly assembled template rise by at + least a caller-specified `fee_threshold`. The default `fee_threshold` is + `MAX_MONEY`, which skips the expensive fee comparison and effectively waits + only for a tip change (or timeout). Previously, miners would receive a new + template with every request, resulting in unnecessary template generation. + This change aligns with the [Stratum V2][topic pooled mining] protocol + specification. {% assign timestamp="37:27" %} - [Eclair #3037][] enhances the `listoffers` command (See Newsletter [#345][news345 offers]) to return all relevant [offer][topic offers] data,