From b8028440f00dddd92d64bb5db982e57f6872af89 Mon Sep 17 00:00:00 2001
From: Gavin Andresen <gavinandresen@gmail.com>
Date: Fri, 6 Dec 2013 09:09:22 +1000
Subject: Replace request= with shorter, QR-friendlier, r=

Consensus from bitcoin-development mailing list discussion.
---
 bip-0072.mediawiki | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

(limited to 'bip-0072.mediawiki')

diff --git a/bip-0072.mediawiki b/bip-0072.mediawiki
index 9909118..4edd749 100644
--- a/bip-0072.mediawiki
+++ b/bip-0072.mediawiki
@@ -21,13 +21,13 @@ bitcoin wallets.
 ==Specification==
 
 The bitcoin: URI scheme is extended with an additional, optional
-"request" parameter, whose value is a URL from which a PaymentRequest
+"r" parameter, whose value is a URL from which a PaymentRequest
 message should be fetched (unsafe and reserved octets in the URL value
 must be encoded as described in RFC 1738).
 
-If the "request" parameter is provided and backwards compatibility
+If the "r" parameter is provided and backwards compatibility
 is not required, then the bitcoin address portion of the URI may be
-omitted (the URI will be of the form: bitcoin:?request=... ).
+omitted (the URI will be of the form: bitcoin:?r=... ).
 
 When Bitcoin wallet software that supports this BIP receives a
 bitcoin: URI with a request parameter, it should ignore the bitcoin
@@ -37,7 +37,7 @@ described in BIP 70.
 
 Bitcoin wallets must support fetching PaymentRequests via http and
 https protocols; they may support other protocols. Wallets must
-include an Accept HTTP header in HTTP requests:
+include an Accept HTTP header in HTTP(s) requests:
 <pre>Accept: application/bitcoin-paymentrequest</pre>
 
 If a PaymentRequest cannot be obtained (perhaps the server is
@@ -47,14 +47,14 @@ payment processing system is unavailable.
 ==Compatibility==
 
 Wallet software that does not support this BIP will simply ignore the
-request parameter and will initiate a payment to bitcoin address.
+r parameter and will initiate a payment to bitcoin address.
 
 ==Examples==
 A backwards-compatible request:
 <pre>
-bitcoin:mq7se9wy2egettFxPbmn99cK8v5AFq55Lx?amount=0.11&request=https%3A%2F%2Fmerchant.com%2Fpay.php%3Fh%3D2a8628fc2fbe
+bitcoin:mq7se9wy2egettFxPbmn99cK8v5AFq55Lx?amount=0.11&r=https%3A%2F%2Fmerchant.com%2Fpay.php%3Fh%3D2a8628fc2fbe
 </pre>
 Non-backwards-compatible equivalent:
 <pre>
-bitcoin:?request=https%3A%2F%2Fmerchant.com%2Fpay.php%3Fh%3D2a8628fc2fbe
+bitcoin:?r=https%3A%2F%2Fmerchant.com%2Fpay.php%3Fh%3D2a8628fc2fbe
 </pre>
-- 
cgit v1.2.3

