mirrors/bitcoin-bips
1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2024-11-19 01:40:05 +01:00
Code Issues Projects Releases Wiki Activity

Replace request= with shorter, QR-friendlier, r=

Browse Source 
Consensus from bitcoin-development mailing list discussion.
This commit is contained in:
Gavin Andresen 2013-12-06 09:09:22 +10:00
parent 640b4f29fd
commit b8028440f0
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
bip-0072.mediawiki
View File

@ -21,13 +21,13 @@ bitcoin wallets.
==Specification== ==Specification==
The bitcoin: URI scheme is extended with an additional, optional 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 message should be fetched (unsafe and reserved octets in the URL value
must be encoded as described in RFC 1738). 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 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 When Bitcoin wallet software that supports this BIP receives a
bitcoin: URI with a request parameter, it should ignore the bitcoin 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 Bitcoin wallets must support fetching PaymentRequests via http and
https protocols; they may support other protocols. Wallets must 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> <pre>Accept: application/bitcoin-paymentrequest</pre>
If a PaymentRequest cannot be obtained (perhaps the server is If a PaymentRequest cannot be obtained (perhaps the server is
@ -47,14 +47,14 @@ payment processing system is unavailable.
==Compatibility== ==Compatibility==
Wallet software that does not support this BIP will simply ignore the 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== ==Examples==
A backwards-compatible request: A backwards-compatible request:
<pre> <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> </pre>
Non-backwards-compatible equivalent: Non-backwards-compatible equivalent:
<pre> <pre>
bitcoin:?request=https%3A%2F%2Fmerchant.com%2Fpay.php%3Fh%3D2a8628fc2fbe bitcoin:?r=https%3A%2F%2Fmerchant.com%2Fpay.php%3Fh%3D2a8628fc2fbe
</pre> </pre>