[30.x] 30.3rc1 #35452

1. 
   fanquake commented at 5:02 PM on June 3, 2026: member

   Final changes for v30.3rc1.

   Backports since 30.2:

   • #34283
   • #34459
   • #34689
   • #34754
   • #34805
   • #34856
   • #35211
   • #35232
2. doc: update release notes for v30.3rc1 06fb949cb4
3. build: bump version to v30.3rc1 e5cbff9b4e
4. doc: update manual pages for v30.3rc1 9d43eb0d8b
5. fanquake added this to the milestone 30.3 on Jun 3, 2026
6. DrahtBot added the label Backport on Jun 3, 2026
7. 
   DrahtBot commented at 5:02 PM on June 3, 2026: contributor

   <!--e57a25ab6845829454e8d69fc972939a-->

   The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

   <!--006a51241073e994b41acfe9ec718e94-->

   Code Coverage & Benchmarks

   For details see: https://corecheck.dev/bitcoin/bitcoin/pulls/35452.

   <!--021abf342d371248e50ceaed478a90ca-->

   Reviews

   See the guideline for information on the review process. A summary of reviews will appear here.

   <!--5faf32d7da4f0f540f40219e4f7537a3-->

8. 
   andrewtoth commented at 8:50 PM on June 3, 2026: contributor

   Can we have something like this in the release notes. Also for 29 point release (and possibly 31 if we don't have an automatic compaction patch merged):

   This fixes an issue where the chainstate database would repeatedly rewrite large portions of itself, causing excessive disk reads and writes during normal operation.

   As a side effect, the chainstate will be around 4 GB larger after an initial sync. To reclaim this space, restart the node with -forcecompactdb=1 after the initial sync has finished. It should be removed on subsequent restarts. Leaving it set will cause significant disk reads and writes every time the node is restarted.

Milestone
30.3