[31.x] More Backports #35699

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

   Backports:

   • #34873
   • #35406
   • #35678 (partial)
   • #35679
   • #35691
   • #35766
   • #35769
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.

   Type	Reviewers
   Stale ACK	optout21

   If your review is incorrectly listed, please copy-paste <code>&lt;!--meta-tag:bot-skip--&gt;</code> into the comment that the bot should ignore.

   <!--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. fanquake force-pushed on Jul 10, 2026
13. DrahtBot added the label CI failed on Jul 10, 2026
14. DrahtBot removed the label CI failed on Jul 10, 2026
15. 
    instagibbs commented at 5:29 PM on July 13, 2026: member

    private tx commits lgtm https://github.com/bitcoin/bitcoin/pull/35699/commits/1f432b28b262fa65cce15df27dc109085f890491

16. 
    optout21 commented at 6:48 AM on July 14, 2026: contributor

    ACK 1f432b28b262fa65cce15df27dc109085f890491

    I've reviewed commits, compared commits to the originals, checked local build & unit tests. I've noticed out of the 4 commits of #35678 only the first one is included, two test-only and one minor change not. I suppose they were not deemed important.

17. fuzz: Remove unused `DeserializeFromFuzzingInput` params overload

    This overload has been unused since it was added in fac81affb527132945773a5315bd27fec61ec52f.
    
    Github-Pull: #35679
    Rebased-From: efa7f8c1437681dfae536017da6f27c75f8f2309

    504ded6b0e
18. fuzz, refactor: Remove `Serialize` overload

    Serialization parameters should be embedded into the object being
    serialized rather than passed as a separate argument. This works here
    because only serialization is performed and no new object needs to be
    constructed.
    
    Github-Pull: #35679
    Rebased-From: afab8d4225c720f8d8658d4ea134505b3d9531f9

    444f2d7965
19. fanquake force-pushed on Jul 20, 2026
20. p2p: Assume v2transport for addresses from seeds

    By now, the vast majority of nodes in the network supports BIP324.
    Even if the optimistic guess would turn out to be wrong for a given
    node, we would just reconnect with v1.
    This is better than making v1 connections with peers when both nodes support v2.
    
    Github-Pull: #35766
    Rebased-From: cf0f2aeae009c98615bffd4dafd74e46f20a0ae6

    c02ff3e793
21. fanquake force-pushed on Jul 22, 2026
22. DrahtBot added the label CI failed on Jul 22, 2026
23. DrahtBot removed the label CI failed on Jul 23, 2026
24. depends, zeromq: Apply upstream patch

    See https://github.com/zeromq/libzmq/pull/4911.
    
    Github-Pull: #35769
    Rebased-From: e446ea09c4d37771798cf9b2d92c3cd1afeaac53

    163821639c
25. doc: update release notes for v31.x 869dcca4fb
26. fanquake force-pushed on Jul 23, 2026

Milestone
31.2