Skip to content

Fix waitNext() description in News346 #2857

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
murchandamus wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fix waitNext() description in News346 #2857

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions _posts/en/newsletters/2025-03-21-newsletter.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -153,10 +153,11 @@ 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
`BlockTemplate` interface, which returns a new template once the chain
tip changes or the fees in the latest block template rise by at least a caller-specified `fee_threshold`.
If no `fee_threshold` is supplied, a new template is generated only after a tip change.
Previously, miners would receive a new template on every request.
This change aligns with the [Stratum
V2][topic pooled mining] protocol specification. {% assign timestamp="37:27" %}

- [Eclair #3037][] enhances the `listoffers` command (See Newsletter
Expand Down