Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1W8qK2-0005u4-Km for bitcoin-development@lists.sourceforge.net; Thu, 30 Jan 2014 12:02:18 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.213.182 as permitted sender) client-ip=209.85.213.182; envelope-from=pieter.wuille@gmail.com; helo=mail-ig0-f182.google.com; Received: from mail-ig0-f182.google.com ([209.85.213.182]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1W8qJx-0005xk-NK for bitcoin-development@lists.sourceforge.net; Thu, 30 Jan 2014 12:02:18 +0000 Received: by mail-ig0-f182.google.com with SMTP id uy17so6921347igb.3 for ; Thu, 30 Jan 2014 04:02:02 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.43.98.202 with SMTP id cp10mr10422079icc.28.1391083322088; Thu, 30 Jan 2014 04:02:02 -0800 (PST) Received: by 10.50.100.10 with HTTP; Thu, 30 Jan 2014 04:02:02 -0800 (PST) In-Reply-To: References: <52E9E787.8080304@borboggle.com> <52EA343E.4010208@borboggle.com> Date: Thu, 30 Jan 2014 13:02:02 +0100 Message-ID: From: Pieter Wuille To: Mike Hearn Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (pieter.wuille[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1W8qJx-0005xk-NK Cc: Bitcoin-Dev Subject: Re: [Bitcoin-development] BIP70 message delivery reliability X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jan 2014 12:02:18 -0000 On Thu, Jan 30, 2014 at 12:59 PM, Mike Hearn 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 submitting or some kind of internal server > error, and the UI would show that the payment failed. That seems > straightforward and how I'd expect things to work as a user. That's one right way to do it imho, but not what is suggested or required by the specification, and not what bitcoin core master currently implements. -- Pieter