🧪 Tested the `privatebroadcast` option introduced in Bitcoin Core v31.0 🆕👇
-> PR: 
-> In the release notes: 
---
1️⃣ In this 1st test, here we can see the initial behavior after broadcasting a transaction on testnet4 using Sparrow → Fulcrum → Bitcoin Core flow.
👀 In the top-right screen, we can see the `bitcoin-cli getprivatebroadcastinfo` command running, which provides introspection and control over private broadcast status in the peer manager:
---
2️⃣ In this 2nd test, we broadcast the transaction just like the 1st, but immediately run `bitcoin-cli abortprivatebroadcast <txid>` in the bottom-left screen to stop it from propagating — acting as a "cancel" button by removing it from the private broadcast queue.
👀 In the top-right screen, `bitcoin-cli getprivatebroadcastinfo` shows the effect instantly, with the transaction disappearing from the peer manager view:
🎨 Finally, an AI-generated diagram explaining how it works under the hood:
Note for @MiniBolt ers: this option is not yet enabled "by default" in the @MiniBolt following the Bitcoin Core initial configuration (`bitcoin.conf`), as it should be used with caution. The broadcast process using this option is **significantly slower**, to the point that Sparrow may display a timeout error, since transactions are not immediately visible in the mempool due to delayed propagation while private connections are established and peers are reached. By observing how this transaction relay delay affects our node, especially LND, we can evaluate whether this should become "the default" Bitcoin Core setting in the future.
---
@npub1hea9...g9v2 ...perhaps it would be a good idea to increase the waiting time or add a condition to prevent Sparrow from throwing that timeout error when `privatebroadcast=1` is enabled in Bitcoin Core, idk. Issue opened: 
---
Good news for the #Bitcoin ecosystem! #Privacy tools are always welcome!🥷💪
GitHub
Broadcast own transactions only via short-lived Tor or I2P connections by vasild · Pull Request #29415 · bitcoin/bitcoin
Parts of this PR are isolated in independent smaller PRs to ease review:
test: extend the SOCKS5 Python proxy to actually connect to a destinatio...
GitHub
bitcoin/doc/release-notes/release-notes-31.0.md at master · bitcoin/bitcoin
Bitcoin Core integration/staging tree. Contribute to bitcoin/bitcoin development by creating an account on GitHub.
Note for @MiniBolt ers: this option is not yet enabled "by default" in the @MiniBolt following the Bitcoin Core initial configuration (`bitcoin.conf`), as it should be used with caution. The broadcast process using this option is **significantly slower**, to the point that Sparrow may display a timeout error, since transactions are not immediately visible in the mempool due to delayed propagation while private connections are established and peers are reached. By observing how this transaction relay delay affects our node, especially LND, we can evaluate whether this should become "the default" Bitcoin Core setting in the future.
---
@npub1hea9...g9v2 ...perhaps it would be a good idea to increase the waiting time or add a condition to prevent Sparrow from throwing that timeout error when `privatebroadcast=1` is enabled in Bitcoin Core, idk. Issue opened: GitHub
Feature request: add support for Bitcoin Core privatebroadcast · Issue #1989 · sparrowwallet/sparrow
After activating and testing the new privatebroadcast option introduced with the new Bitcoin Core v31.0 (bitcoin/bitcoin#29415), I observed that th...
