🧪 Tested the `privatebroadcast` option introduced in Bitcoin...

Raw JSON

{
  "kind": 1,
  "id": "c24b22732eb11e185fc2abfbdcc328976656d3e6ce9d03576d7291cf4396f547",
  "pubkey": "b17fccdf07ba2387f038b34426720cd68d112df923bca2bed8f8c309b7211155",
  "created_at": 1777142381,
  "tags": [
    [
      "client",
      "Yakihonne",
      "31990:20986fb83e775d96d188ca5c9df10ce6d613e0eb7e5768a0f0b12b37cdac21b3:1700732875747"
    ],
    [
      "p",
      "763b053bc37a0924c16f8f5a60782b7c1ad0a95b9bcac67971b355994e8daf9f",
      "",
      "mention"
    ],
    [
      "p",
      "be7a5291b532e8b918f2dc98148948a33d3e0da07788d7416f73b4c7514f08e6",
      "",
      "mention"
    ],
    [
      "t",
      "Bitcoin"
    ],
    [
      "t",
      "Privacy"
    ]
  ],
  "content": "🧪 Tested the `privatebroadcast` option introduced in Bitcoin Core v31.0 🆕👇\n\n-\u003e PR: https://github.com/bitcoin/bitcoin/pull/29415\n\n-\u003e In the release notes: https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-31.0.md#p2p-and-network-changes\n\n---\n1️⃣ In this 1st test, here we can see the initial behavior after broadcasting a transaction on testnet4 using Sparrow → Fulcrum → Bitcoin Core flow.\n\n👀 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:\n\nhttps://blossom.minibolt.info/4acc29393dd8c5cbcd9e57b4f5fc157936d3c59a35417437587531472393e67b.mp4\n\n---\n2️⃣ In this 2nd test, we broadcast the transaction just like the 1st, but immediately run `bitcoin-cli abortprivatebroadcast \u003ctxid\u003e` in the bottom-left screen to stop it from propagating — acting as a \"cancel\" button by removing it from the private broadcast queue.\n\n👀 In the top-right screen, `bitcoin-cli getprivatebroadcastinfo` shows the effect instantly, with the transaction disappearing from the peer manager view:\n\nhttps://blossom.minibolt.info/65ca1e9af8ee51ee74a31e45d493d0ca73bc6599e5b05f469dfaaca3668aa7f5.mp4\n\n🎨 Finally, an AI-generated diagram explaining how it works under the hood:\n\nhttps://blossom.minibolt.info/2f8f092ea6a5b37f5314fc5ea3311a08dfb141951b5bd80501353cbdc92c15d0.webp\n\nNote for nostr:nprofile1qqs8vwc980ph5zfyc9hc7knq0q4hcxks49dehjkx09cmx4vef6x6l8c9lz6rd ers: this option is not yet enabled \"by default\" in the nostr:nprofile1qqs8vwc980ph5zfyc9hc7knq0q4hcxks49dehjkx09cmx4vef6x6l8c9lz6rd 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.\n\n---\n\nnostr:nprofile1qqstu7jjjx6n969erredexq539y2x0f7pks80zxhg9hh8dx8298s3es4t502m ...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: https://github.com/sparrowwallet/sparrow/issues/1989\n\n---\n\nGood news for the #Bitcoin ecosystem! #Privacy tools are always welcome!🥷💪",
  "sig": "632f5557f1dde929170836149c98943bca0c704907ef80aa72ac671f67c74f18a2f83f1cb2fd18e3e41089a24cb23ac3ef9de8a5b00724800810d3f95ec69002"
}