mirrors/bitcoin-bips
1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2025-02-23 23:27:22 +01:00
Code Issues Projects Releases Wiki Activity

Revert "Update BIP-21 URI scheme for payment code support"

Browse source 
This reverts commit 2e6e5cf958.
This commit is contained in:
Luke Dashjr 2016-02-01 20:36:37 +00:00
parent 664c19aca5
commit e22ad0cd71
1 changed files with 0 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
bip-0021.mediawiki
View file

@ -56,7 +56,6 @@ The scheme component ("bitcoin:") is case-insensitive, and implementations must
*address: bitcoin address *address: bitcoin address
*message: message that describes the transaction to the user ([[#Examples|see examples below]]) *message: message that describes the transaction to the user ([[#Examples|see examples below]])
*size: amount of base bitcoin units ([[#Transfer amount/size|see below]]) *size: amount of base bitcoin units ([[#Transfer amount/size|see below]])
*paycode: payment code (BIP-47)
*(others): optional, for future extensions *(others): optional, for future extensions
==== Transfer amount/size ==== ==== Transfer amount/size ====
@ -68,11 +67,6 @@ I.e. amount=50.00 or amount=50 is treated as 50 BTC, and amount=50,000.00 is inv
Bitcoin clients MAY display the amount in any format that is not intended to deceive the user. Bitcoin clients MAY display the amount in any format that is not intended to deceive the user.
They SHOULD choose a format that is foremost least confusing, and only after that most reasonable given the amount requested. They SHOULD choose a format that is foremost least confusing, and only after that most reasonable given the amount requested.
For example, so long as the majority of users work in BTC units, values should always be displayed in BTC by default, even if mBTC or TBC would otherwise be a more logical interpretation of the amount. For example, so long as the majority of users work in BTC units, values should always be displayed in BTC by default, even if mBTC or TBC would otherwise be a more logical interpretation of the amount.
==== Payment code ====
If a URI provides a payment code, and if the client supports BIP-47, then the resulting transaction SHOULD construct a transaction per BIP-47 instead of using the address provided in the URI.
== Rationale == == Rationale ==
===Payment identifiers, not person identifiers=== ===Payment identifiers, not person identifiers===
@ -128,6 +122,3 @@ Characters must be URI encoded properly.
=== Bitcoin clients === === Bitcoin clients ===
* Bitcoin-Qt supports the old version of Bitcoin URIs (ie without the req- prefix), with Windows and KDE integration as of commit 70f55355e29c8e45b607e782c5d76609d23cc858. * Bitcoin-Qt supports the old version of Bitcoin URIs (ie without the req- prefix), with Windows and KDE integration as of commit 70f55355e29c8e45b607e782c5d76609d23cc858.
==References==
* [[bip-0047.mediawiki|BIP47 - Reusable Payment Codes for Hierarchical Deterministic Wallets]]