From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1V7Azl-0000O0-2J for bitcoin-development@lists.sourceforge.net; Wed, 07 Aug 2013 21:10:13 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.42 as permitted sender) client-ip=74.125.82.42; envelope-from=gavinandresen@gmail.com; helo=mail-wg0-f42.google.com; Received: from mail-wg0-f42.google.com ([74.125.82.42]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1V7Azj-0005s8-Al for bitcoin-development@lists.sourceforge.net; Wed, 07 Aug 2013 21:10:13 +0000 Received: by mail-wg0-f42.google.com with SMTP id j13so25188wgh.1 for ; Wed, 07 Aug 2013 14:10:05 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.180.183.108 with SMTP id el12mr3229985wic.55.1375909805120; Wed, 07 Aug 2013 14:10:05 -0700 (PDT) Received: by 10.194.82.198 with HTTP; Wed, 7 Aug 2013 14:10:05 -0700 (PDT) In-Reply-To: References: Date: Thu, 8 Aug 2013 07:10:05 +1000 Message-ID: From: Gavin Andresen To: Bitcoin Dev 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 (gavinandresen[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: 1V7Azj-0005s8-Al Subject: Re: [Bitcoin-development] Payment Protocol: BIP 70, 71, 72 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: Wed, 07 Aug 2013 21:10:13 -0000 RE: making the bitcoin address in the bitcoin: URI optional: Ok, I'm convinced, sometimes merchants won't want or need backwards compatibility and sometimes it won't make sense for them to put an arbitrary bitcoin: address there. RE: should the customer's machine not broadcast the transaction: I'd like to hear from other wallet implementors. Do you have a notion of 'locked inputs' ? The tricky bit in constructing a transaction but not broadcasting it right away is the inputs must be locked, so they're not accidentally double-spent. I'd also like to hear from merchants: any issue with your payment processing server having "broadcast transaction" functionality? My biggest worry is that the payment protocol will not get wide support if it is too hard to implement. -- -- Gavin Andresen