Posted by Yuval Kogman
Mar 28, 2025/23:41 UTC
The discussion revolves around the intricacies of Payjoin, a protocol that offers an alternative to traditional Bitcoin transactions by allowing the receiver to participate in the transaction, potentially enhancing privacy. This method does not obligate the receiver to opt-in for participating; they have the freedom to broadcast the transaction received from the sender as is. The conversation highlights that zero-confirmation considerations remain unchanged regardless of participation in Payjoin, emphasizing the protocol's flexibility.
One significant point raised is the potential for Payjoin to allow for more strategic coin selection, possibly even manual coin control, under BIP 77. However, skepticism exists regarding the effectiveness of coin control in preventing privacy leaks within this context. It's argued that the nature of on-chain payments inherently poses a risk of information disclosure, whether or not Payjoin is utilized. The inherent problem lies in the unavoidable revelation of transaction details at some point, making privacy a challenging goal.
Furthermore, the discussion delves into the technicalities of BIP 77, noting its asynchronous nature and how it accommodates various levels of interaction between sender and receiver, including the signaling of Payjoin support and the optional nature of its adoption. A specific point of contention is the cost associated with transaction replacement, which, according to protocol specifications, becomes significant unless the attacker has substantial control over the network's hash rate. This introduces a safeguard where receivers can set a minimum contribution threshold for the attacker, essentially creating a financial deterrent.
Attention is also given to the implementation challenges faced by applications like the BullBitcoin mobile app, which hasn't fully embraced the Payjoin protocol, particularly highlighting the difference between automated systems and manual peer-to-peer workflows. The importance of implementing fallback transactions to prevent costless attacks is underscored, suggesting room for improvement in software development and protocol documentation to better address security concerns.
Lastly, the conversation touches upon historical analyses of Bitcoin's anonymity and privacy challenges, referencing academic works that lay the groundwork for current discussions. Notably, it corrects a common misconception about the pioneering research in this field, clarifying the timeline and contributions of various scholars towards understanding Bitcoin's privacy implications.
In summary, the dialogue encapsulates a technical examination of Payjoin's potential and limitations, exploring its impact on privacy, protocol adherence, and the broader implications for Bitcoin transaction practices. Through a detailed dissection of protocol specifications, implementation challenges, and historical context, it provides a comprehensive overview of ongoing efforts to enhance transaction privacy in the Bitcoin ecosystem.
TLDR
We’ll email you summaries of the latest discussions from authoritative bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.
We'd love to hear your feedback on this project?
Give Feedback