What changed, and why it matters
This commit only adds documentation: a release note explaining that the Bitcoin Core fee estimator now tracks lower fee rates (down to 0.1 sat/vB instead of 1 sat/vB). There is no code change, no bug fix, and no security issue in the diff itself.
No action required; this is a documentation-only commit. Review the associated fee-estimator code change separately if assessing security relevance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit creates doc/release-notes-33199.md describing a prior fee-estimator change. It documents that the minimum tracked fee bucket changed from 1 sat/vB to 0.1 sat/vB and that restarting with this change clears saved fee_estimates.dat. The diff contains only release-note text; no executable code is modified.
Changed components
doc/release-notes-33199.mdInspect captured patch +9 / −0
diff --git a/doc/release-notes-33199.md b/doc/release-notes-33199.md
new file mode 100644
index 00000000..90246d78
--- /dev/null
+++ b/doc/release-notes-33199.md
@@ -0,0 +1,9 @@
+Fee Estimation
+========================
+
+- The Bitcoin Core fee estimator minimum fee rate bucket was updated from **1 sat/vB** to **0.1 sat/vB**,
+ which matches the node’s default `minrelayfee`.
+ This means that for a given confirmation target, if a sub-1 sat/vB fee rate bucket is the minimum tracked
+ with sufficient data, its average value will be returned as the fee rate estimate.
+
+- Note: Restarting a node with this change invalidates previously saved estimates in `fee_estimates.dat`, the fee estimator will start tracking fresh stats.
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.