Private Broadcast After Merge (Bitcoin Core Dev Tech, May 2026)

A short session on next steps after merging "private broadcast" — sending a wallet's own transactions to the network in a way that reduces the privacy fingerprint of which node originated them. Topics included adding wallet transactions in order even when they are not in the mempool, and whitelisting getdata for a transaction's ancestors (parents and ancestors are fine for privacy, but not siblings) using a GetAncestors API and a txgraph of the private-broadcast queue.

The design gets 1p1c package relay "for free" from that ancestor handling. The session also touched persistence (writing each added transaction to a file and replaying it on startup, though its necessity is debatable) and periodically broadcasting decoy transactions drawn from one's recent history.