[Bitcoin-development] BIP70 message delivery reliability

2014-01-29 Thread Chuck
that the merchant can be confident the refund address is correct. In each step along the way until step 5, if a message delivery fails nobody is harmed because the purchase is incomplete. Thoughts? Chuck -- WatchGuard

Re: [Bitcoin-development] BIP70 message delivery reliability

2014-01-30 Thread Chuck
could argue the transactions seen on the network were insufficient. To me, this could be a problem. Cheers, Chuck -- WatchGuard Dimension instantly turns raw network data into actionable security intelligence

Re: [Bitcoin-development] BIP70 message delivery reliability

2014-01-30 Thread Chuck
. Merchants can also lie: reply with 200 OK and an empty body. Or, reply with 404 not found and broadcast transactions anyway. Cheers, Chuck -- WatchGuard Dimension instantly turns raw network data into actionable security

Re: [Bitcoin-development] BIP70 message delivery reliability

2014-01-30 Thread Chuck
On 1/30/2014 7:02 PM, Pieter Wuille wrote: On Thu, Jan 30, 2014 at 12:59 PM, Mike Hearn m...@plan99.net wrote: With the way it works in bitcoinj, the tx is only committed to the wallet if the server accepts the Payment message and ACKs it. So the tx would not be retried if there's a failure

Re: [Bitcoin-development] BIP70: PaymentACK semantics

2014-01-30 Thread Chuck
interest to have the transactions confirmed. c) Send them as a response to the PaymentRequest/PaymentDetails with the UNsigned transaction, and then follow up with the signed transaction in a separate message. ... On Wed, 29 Jan 2014 21:47:51 -0800, Chuck chuck+bitcoin...@borboggle.com wrote