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-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1V4Ueb-0000M6-Ii for bitcoin-development@lists.sourceforge.net; Wed, 31 Jul 2013 11:33:17 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.173 as permitted sender) client-ip=74.125.82.173; envelope-from=gavinandresen@gmail.com; helo=mail-we0-f173.google.com; Received: from mail-we0-f173.google.com ([74.125.82.173]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1V4UeX-0003hm-P0 for bitcoin-development@lists.sourceforge.net; Wed, 31 Jul 2013 11:33:17 +0000 Received: by mail-we0-f173.google.com with SMTP id x55so489649wes.18 for ; Wed, 31 Jul 2013 04:33:07 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.108.132 with SMTP id hk4mr49931424wjb.43.1375270387631; Wed, 31 Jul 2013 04:33:07 -0700 (PDT) Received: by 10.194.82.198 with HTTP; Wed, 31 Jul 2013 04:33:07 -0700 (PDT) In-Reply-To: References: <20130731084538.GL16713@giles.gnomon.org.uk> Date: Wed, 31 Jul 2013 21:33:07 +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: 1V4UeX-0003hm-P0 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 11:33:17 -0000 On Wed, Jul 31, 2013 at 6:45 PM, Roy Badami wrote: > > Is it envisaged to be possible/sensible to have a URI that is *only* a > payment request? i.e. something like the following (although I'm not > sure this is a valid URI): > > bitcoin:?request=https%3A%2F%2Fmerchant.com%2Fpay.php%3Fh%3D2a8628fc2fbe I think we'll want a bitcoin address in there for a long time for backwards compatibility. If web browser support for arbitrary MIME types is strong enough (I haven't tested), then a payment request can be initiated with just an anchor tag: Doing it that way saves a http round-trip. -- -- Gavin Andresen