Published on: 2013-12-13T21:49:23+00:00
In a discussion about a possible use case for pastebin style hosting sites for payment requests, it is proposed that regular end-users could upload signed or unsigned payment requests to a site like payr.com. The site would then handle incrementing the iteration count on each download of the file, relieving users from having to handle it themselves. This would be particularly useful for organizations receiving multiple payment requests with different xpubkeys. Both use cases can be supported, and iteration ranges can be specified if someone wants to specify expiry in terms of number of payments rather than time.Address reuse is another topic discussed, specifically in the context of an individual providing the Bitcoin Foundation with a PaymentRequest that includes multiple outputs, each having a different xpubkey. It is suggested that the Foundation's wallet software should take care of iterating in this situation. Rotating through multiple outputs is seen as a temporary solution to address reuse, with HD wallets ultimately being the more effective solution.Integration of BIP32 and BIP70 is also mentioned in an email conversation between Mike Hearn and Gavin Andresen. The proposal suggests adding an additional xpubkey and iteration count field to each output script for improved privacy. However, this requires a backwards incompatible change to the protocol. The conversation also discusses the possibility of last-minute changes to BIP70 before wallets ship and merchant support begins. "Super addresses" from BIP32 are suggested as a way to enhance privacy in BIP70's PaymentDetails message, which allows for multiple outputs. The refund_to address in Payment could also be upgraded to a super address for increased privacy.Another email conversation proposes the implementation of "super addresses" in Bitcoin wallets, aligning with the concept of BIP32. Super addresses encourage the use of a single address instead of traditional ones, improving privacy by eliminating the need to merge coins. This concept would fit well into BIP70, allowing payments to be broken into pieces to match unspent outputs in customers' wallets. Upgrading the refund_to address in Payment to a super address is also suggested. The author believes that implementing these proposals could greatly enhance Bitcoin's privacy features.In an article aimed at a non-developer audience, Bitcoin privacy topics are discussed, including P2P connection encryption, address reuse/payment protocol, and CoinJoin and merge avoidance. The article provides insights into the importance of privacy in Bitcoin transactions and explores various methods for improving it. It also delves into the use of SSL for P2P connections and its potential benefits and limitations. The article serves as a valuable resource for those looking to better understand Bitcoin privacy and contributes to the ongoing discussion around the topic.Overall, these discussions and proposals highlight the potential for improved privacy in Bitcoin transactions through the integration of BIP32 and BIP70, the use of "super addresses," and the exploration of various privacy-enhancing features in the payment protocol.
Updated on: 2023-08-01T06:51:29.978922+00:00