Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1V4fyF-0007JQ-CF for bitcoin-development@lists.sourceforge.net; Wed, 31 Jul 2013 23:38:19 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.169 as permitted sender) client-ip=74.125.82.169; envelope-from=gavinandresen@gmail.com; helo=mail-we0-f169.google.com; Received: from mail-we0-f169.google.com ([74.125.82.169]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1V4fyD-0006lh-KL for bitcoin-development@lists.sourceforge.net; Wed, 31 Jul 2013 23:38:19 +0000 Received: by mail-we0-f169.google.com with SMTP id n5so1156832wev.28 for ; Wed, 31 Jul 2013 16:38:11 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.170.227 with SMTP id ap3mr23599779wjc.40.1375313891426; Wed, 31 Jul 2013 16:38:11 -0700 (PDT) Received: by 10.194.82.198 with HTTP; Wed, 31 Jul 2013 16:38:11 -0700 (PDT) In-Reply-To: References: <20130731084538.GL16713@giles.gnomon.org.uk> Date: Thu, 1 Aug 2013 09:38:11 +1000 Message-ID: From: Gavin Andresen To: E willbefull 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: 1V4fyD-0006lh-KL Cc: bitcoin-development@lists.sourceforge.net 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, 31 Jul 2013 23:38:19 -0000 On Thu, Aug 1, 2013 at 9:30 AM, E willbefull wrote: > I think it's important to expect PaymentRequest-only bitcoin URIs in the > future. Some types of payments (exotic transactions) may not make sense to > have a single fallback address. P2SH addresses already support all exotic transactions. > Or, a page with a bitcoin URI link may be > relying on a separate service provider to assemble the transaction. Do you mean assemble the PaymentRequest message? Because the payment transaction will always be created by the customer's wallet software. IF PaymentRequests take over the world and we get 100% wallet software support, then I'd be happy to write another BIP that says that a bitcoin: URI can be just bitcoin:?request=http... -- -- Gavin Andresen