What to know

  • PR36365 was merged onSeptember29.
  • The change provides fallback when the mempool-based estimator is unavailable.
  • Applications still need to handle unavailable estimates and version differences.

What changed in the repository

Bitcoin Core pull request 36365 was merged on 29 September 2026. The author describes three changes: using the confirmation-based estimator when the mempool-based alternative is unavailable, clearing gathered mempool-estimator data after a restart with failed mempool loading, and renaming a default estimator option from none to auto. This is a report about a merged code change and its stated purpose. Release inclusion and the behavior of an operator’s installed binary must be checked separately.

The practical problem is an incomplete observation

Fee estimation depends on what the software has observed and retained. A process can be running while one of its data sources is not ready. Our interpretation is that returning a useful result from a still-valid source is preferable to treating every partial failure as total failure, provided the API makes its behavior clear. The restart case also illustrates why remembered health information should not be trusted without checking the data that supposedly supports it.

An application should understand its fallback

Wallets and payment services often add their own behavior around a node response. They may retry, use a configured value, stop the transaction flow or ask a user to choose. Those choices deserve explicit review because a missing estimate can otherwise become an unexpectedly low or high fee. A fallback should have an owner, a maximum age and a documented failure mode. Simply logging an exception does not show that the resulting transaction request remains appropriate for the user’s task.

A bounded integration review

For a service integrating with Bitcoin Core, a useful test matrix includes a normal response, an unavailable estimate, a restart and an unexpected parameter value. Compare the actual response shape against the exact version being deployed. Store the test inputs and outputs without including private wallet data. These are suggested application-level checks, not claims that BijliCoin has tested this pull request. An operator should also verify whether a separate library caches or transforms the estimate before it reaches the interface.

Do not confuse reliability with prediction

A more reliable estimator interface does not guarantee a transaction will confirm within a fixed interval or prevent future fee changes. It improves how software handles a particular information gap. Readers should follow the final release notes and their integration’s compatibility guidance before changing production behavior. The engineering lesson is broader than this merge: when an application depends on several imperfect observations, it should specify which observations can substitute for others and when it must decline to produce a confident answer.

Sources and reading

Editorial note: AI-assisted original BijliCoin synthesis. Original BijliCoin synthesis of the linked public primary source. Analysis and suggested checks are editorial interpretation; reported claims are attributed. Illustration is conceptual, not a photograph of the event.

Sources & context

  1. Bitcoin Core PR36365, merged September 29 ↗

See our editorial policy or report a correction.