[31.x] More Backports #35699

1. 
   fanquake commented at 9:32 AM on July 10, 2026: member

   Backports:

   • #34873
   • #35406
   • #35678 (partial)
   • #35691
2. chainparams: delete my DNS seed

   Github-Pull: #35691
   Rebased-From: d9080639804187601a84bad18582e7afb93101c3

   b4dd6ba49b
3. fanquake added this to the milestone 31.2 on Jul 10, 2026
4. DrahtBot added the label Backport on Jul 10, 2026
5. 
   DrahtBot commented at 9:32 AM on July 10, 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/35699.

   <!--021abf342d371248e50ceaed478a90ca-->

   Reviews

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

   <!--5faf32d7da4f0f540f40219e4f7537a3-->

6. net: introduce TxSendStatus internal state container

   Github-Pull: #34873
   Rebased-From: 999d18ab1ca6f802f13bfae8c4d10572ae55c6c3

   0086a236cb
7. net: delay stale evaluation and expose time_added in private broadcast

   Github-Pull: #34873
   Rebased-From: 325afe664d103bbdfd0758881f113aaa84f90627

   ef7542aa29
8. private broadcast: limit outstanding txs to count of 10,000

   Add a belt-and-suspenders feature, limit the amount of
   memory and cpu possible when unlucky or simply misconfigured.
   The worst case limit is roughly 400kB * 10,000 = 4GB, regardless
   of usage pattern.
   
   Before this change, sheer volume of broadcasts, mismatches in
   standardness rules, or simply fee mismatches may result in unbounded
   growth of memory usage. As the feature may be expanded in
   the future, explicit bounds helps reasoning going forward.
   
   Github-Pull: #35406
   Rebased-From: 5aea3d0373f7f1961ddbab4a6c26fd0d8e35275e

   c1a0ed5225
9. Release cs_main between individual private tx re-attempts

   This queue may be hundreds to thousands of items, each of
   which are being revalidated at short interval. Allow the
   node to be more responsive in this scenario.
   
   Github-Pull: #35406
   Rebased-From: cbf8c107c12f53045d584f5286337d45f1080954

   cd32ebd3f4
10. fanquake force-pushed on Jul 10, 2026
11. rpc: define and use new RPC_LIMIT_EXCEEDED error code

    The server isn't running out of memory when the private broadcast
    transaction queue is full. Add a new RPC_LIMIT_EXCEEDED code that
    can be used whenever a resource is bound and currently at capacity.
    
    Github-Pull: #35678
    Rebased-From: 82a02a2a2208a94686949cf3b5991a834b37263a

    ec1123aed1
12. doc: update release notes for v31.x 1f432b28b2
13. fanquake force-pushed on Jul 10, 2026
14. DrahtBot added the label CI failed on Jul 10, 2026
15. DrahtBot removed the label CI failed on Jul 10, 2026

Milestone
31.2