mirror of
https://github.com/bitcoin/bips.git
synced 2024-11-19 01:40:05 +01:00
Update BIP-21 URI scheme for payment code support
Incorporates suggestion by erasmospunk: https://github.com/bitcoin/bips/pull/159#issuecomment-115277577
This commit is contained in:
parent
e700392b15
commit
2e6e5cf958
@ -56,6 +56,7 @@ The scheme component ("bitcoin:") is case-insensitive, and implementations must
|
||||
*address: bitcoin address
|
||||
*message: message that describes the transaction to the user ([[#Examples|see examples below]])
|
||||
*size: amount of base bitcoin units ([[#Transfer amount/size|see below]])
|
||||
*paycode: payment code (BIP-47)
|
||||
*(others): optional, for future extensions
|
||||
|
||||
==== Transfer amount/size ====
|
||||
@ -67,6 +68,11 @@ 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.
|
||||
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.
|
||||
|
||||
==== 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 ==
|
||||
|
||||
===Payment identifiers, not person identifiers===
|
||||
@ -122,3 +128,6 @@ Characters must be URI encoded properly.
|
||||
=== 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.
|
||||
|
||||
==References==
|
||||
|
||||
* [[bip-0047.mediawiki|BIP47 - Reusable Payment Codes for Hierarchical Deterministic Wallets]]
|
||||
|
Loading…
Reference in New Issue
Block a user