What the developer wrote
Authored by Fabian Jahr
doc: Add release note for 30469
What changed, and why it matters
This commit is just documentation: it adds a release note describing an earlier fix (pull request 30469) for an overflow bug in Bitcoin Core's coinstatsindex feature. The release note warns users that the index will be rebuilt on first startup after upgrading, and explains where the old and new index data are stored. The actual code fix is not shown in this commit, so we can only assess the issue from the release-note description.
Treat this as a low-confidence informational signal. Review PR 30469 and the actual code changes that fixed the coinstatsindex overflow to determine whether the bug could affect consensus, index integrity, or node availability. Users running coinstatsindex should upgrade and allow the index to resync; those not using the index are unaffected.
Security signals we found
Release note references a prior overflow bug in coinstatsindex
Overflow was observable on default Signet, implying it could affect mainnet-like index calculations
Index is rebuilt from scratch on upgrade, indicating data-format or computation change
No code changes in this commit; security assessment relies on release-note description only
Evidence from the diff
The commit creates doc/release-notes-30469.md, a release note for PR 30469. The note states that coinstatsindex had an overflow bug reproducible on the default Signet network, that the index implementation was changed to prevent it, and that the on-disk location changed from /indexes/coinstats/ to /indexes/coinstatsindex/. No source code changes are present in this commit. The overflow bug itself is not described in detail, and no exploit path is documented here.
Changed components
doc/release-notes-30469.mdcoinstatsindex (referenced only, not changed in this commit)Inspect captured patch +4 / −0
diff --git a/doc/release-notes-30469.md b/doc/release-notes-30469.md
new file mode 100644
index 00000000..a1f60459
--- /dev/null
+++ b/doc/release-notes-30469.md
@@ -0,0 +1,4 @@
+Indexes
+-------
+
+- The implementation of coinstatsindex was changed to prevent an overflow bug that could already be observed on the default Signet. The new version of the index will need to be synced from scratch when starting the upgraded node for the first time. The new version is stored in `/indexes/coinstatsindex/` in contrast to the old version which was stored at `/indexes/coinstats/`. The old version of the index is not deleted by the upgraded node in case the user chooses to downgrade their node in the future. If the user does not plan to downgrade it is safe for them to remove `/indexes/coinstats/` from their datadir. A future release of Bitcoin Core may remove the old version of the index automatically.
Why this scored 41/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.