Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change bip272 to follow current wallets implementations #2

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Change bip272 to follow current wallets implementations #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 10 additions & 18 deletions bip-0272.mediawiki
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@

==Abstract==

This BIP describes an extension to the bitcoin: URI scheme (BIP 3) to
This BIP describes additional scheme beside the bitcoin: URI scheme (BIP 3) to
support the simplified payment protocol (BIP 270).

==Motivation==
Expand All @@ -18,21 +18,18 @@ bitcoin wallets.

==Specification==

The bitcoin: URI scheme is extended with an additional, optional
"r" parameter, whose value is a URL from which a PaymentRequest
The pay: URI scheme is introduced. It could have the same prefix like in BIP3 (bitcoin:)
but the proposed one is more generic and fits better for multi-currency wallets.

The scheme requires one "r" parameter, whose value is a URL from which a PaymentRequest
message should be fetched (characters not allowed within the scope
of a query parameter must be percent-encoded as described in RFC 3986
and bip-0003).

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:?r=... ).

When Bitcoin wallet software that supports this BIP receives a
bitcoin: URI with a request parameter, it should ignore the bitcoin
address/amount/label/message in the URI and instead fetch a
pay: URI with a request parameter, it should fetch a
PaymentRequest message and then follow the payment protocol, as
described in BIP 70.
described in BIP 270.

Bitcoin wallets must support fetching PaymentRequests via the
HTTPS protocol; they may support other protocols. Wallets must
Expand All @@ -49,17 +46,12 @@ redirect) should be handled as outlined in RFC 2616.

==Compatibility==

Wallet software that does not support this BIP will simply ignore the
r parameter and will initiate a payment to bitcoin address.
This BIP is not compatible with the original one (BIP3) and Wallet software that does not support this BIP
cannot proceed with a payment.

==Examples==
A backwards-compatible request:
<pre>
bitcoin:mq7se9wy2egettFxPbmn99cK8v5AFq55Lx?sv&amount=0.11&r=https://merchant.com/pay.php?h%3D2a8628fc2fbe
</pre>
Non-backwards-compatible equivalent:
<pre>
bitcoin:?sv&r=https://merchant.com/pay.php?h%3D2a8628fc2fbe
pay:?sv&r=https://merchant.com/pay.php?h%3D2a8628fc2fbe
</pre>

==References==
Expand Down