Private broadcast tracking #34476

issue vasild openend this issue on February 2, 2026
  1. vasild commented at 10:49 am on February 2, 2026: contributor

    A meta issue to track the pull requests related to private broadcast

    Initial

    • 🪓 🔥 ⛔ First attempt that tried to put the transaction in the mempool (#27509)
    • 🟢 ✔️ 🥳 Implement the ability to broadcast a transaction via a short lived privacy connection and use that for the sendrawtransaction RPC (#29415)

    Followups and extensions

    Wallet

    Other

    Fixes and improvements

  2. fanquake added the label Tracking Issue on Feb 2, 2026
  3. Crypt-iQ commented at 6:32 pm on February 4, 2026: contributor

    Looks like the private broadcast changes introduced non-determinism in the process_message(s) fuzz harnesses. They re-use the same Connman across iterations, and the m_outbound_tor_ok_at_least_once may have already been flipped true by a previous iteration. The non-determinism shows up here: https://github.com/bitcoin/bitcoin/blob/d4bc620ad8cf6b7975be55d5ae27dc943cceef3f/src/net.cpp#L4066-L4071

    Ideally, this check would not be hit if private broadcast is disabled?

  4. vasild referenced this in commit 41c94739ca on Feb 5, 2026
  5. vasild commented at 8:53 am on February 5, 2026: contributor

    non-determinism in the process_message(s) fuzz harnesses

    Addressed in https://github.com/bitcoin/bitcoin/pull/34511

  6. vasild referenced this in commit 2cb7e99dee on Feb 5, 2026
  7. vasild commented at 5:40 am on February 7, 2026: contributor
    Added #34533 wallet: resubmit transactions with private broadcast if enabled

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-02-10 18:13 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me