On Thu, Jan 30, 2014 at 3:51 PM, Jeff Garzik <jgar...@bitpay.com> wrote:
> On Mon, Jan 27, 2014 at 5:17 PM, Pieter Wuille <pieter.wui...@gmail.com> 
> wrote:
>> On Mon, Jan 27, 2014 at 11:03 PM, Kevin Greene <kgree...@gmail.com> wrote:
>> > Should the wallet broadcast the transaction to the bitcoin network when it
>> > receives an ACK, or always assume that the merchant server will do that?
>> In my opinion, that should be the primary meaning of receiving an ACK:
>> acknowledgement that the receiver takes responsibility for getting the
>> transaction confirmed (to the extent possible, of course).
> Is this truly the intent?  That the merchant/processor takes full
> responsibility for getting the TX confirmed?

Confirmed is probably the wrong word. But IMHO (not how it's currently
worded), the merchant should take that responsibility after delivering
a PaymentACK. This means the client does not need to stay online
anymore. More importantly, it removes the requirement for the P2P
network to function as a reliable sender->receiver communication
channel (and reduces it to a broadcast medium to get transactions to


WatchGuard Dimension instantly turns raw network data into actionable 
security intelligence. It gives you real-time visual feedback on key
security issues and trends.  Skip the complicated setup - simply import
a virtual appliance and go from zero to informed in seconds.
Bitcoin-development mailing list

Reply via email to