Talk:BIP 0020: Difference between revisions
No edit summary |
|||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 11: | Line 11: | ||
== Use-cases - buy this link == | == Use-cases - buy this link == | ||
On the buy-this link, perhaps we should also incorporate an optional transaction id or something which would be passed along to the bitcoin client. Not really transaction but some sort of arbitrary data, only meaningful to the merchant. Something an online merchant can use to verify which transaction it has received is relevant to a purchase. [[User:Dantman|Dantman]] 20:45, 18 April 2011 (GMT) | On the buy-this link, perhaps we should also incorporate an optional transaction id or something which would be passed along to the bitcoin client. Not really transaction but some sort of arbitrary data, only meaningful to the merchant. Something an online merchant can use to verify which transaction it has received is relevant to a purchase. [[User:Dantman|Dantman]] 20:45, 18 April 2011 (GMT) | ||
== Why all the crazy representation stuff? == | == Why all the crazy representation stuff? == | ||
| Line 51: | Line 24: | ||
Example: I want to buy a digital newspaper or app via QR code: I scan the code, pay the amount and am then redirected to a refreshing "waiting for payment" page that will show me the content when it considers the transaction valid. | Example: I want to buy a digital newspaper or app via QR code: I scan the code, pay the amount and am then redirected to a refreshing "waiting for payment" page that will show me the content when it considers the transaction valid. | ||
[[User:Phelix|Phelix]] 10:19, 22 January 2012 (GMT) | |||
== The bitcoin URL scheme doesn't include "web+" prefix == | |||
https://bitcointalk.org/index.php?topic=128822.0 | |||
[[User:Ripper234|Ripper234]] ([[User talk:Ripper234|talk]]) 20:56, 2 December 2012 (GMT) | |||
Latest revision as of 20:56, 2 December 2012
Has anybody thought about including network addresses (IPv4/IPv6) of the receiving client into the URL? This way, a payment transaction could be sent directly (in addition to sending P2P of course). --Goonie 11:21, 23 July 2011 (GMT)
Fallback URI
On Android an app can register to open with a normal web URI. This has the advantage of acting as a fallback URI in case there is no app that supports bitcoin:. For example we could propose https://en.bitcoin.it/wiki/Send/<address>[?][amount=<size>][&][label=<label>][&][message=<message>]. If the user had a mobile app that supported bitcoin it would have registered https://en.bitcoin.it/wiki/Send/ and be launched. If the user did not have such an app their browser would launch and be directed to https://en.bitcoin.it/wiki/Send/. This page could then inform the user about various apps that support bitcoin transfers and possibly have a link to MyBitcoin as well. Maybe https://bitcoin.org/Send/ would be more appropriate, though that one might not be updated often enough.
- iPhone support
There is even a way to have this work on iOS devices. Have the web page redirect to the standard bitcoin: scheme. If an app is present to support this the app will launch, if not the browser the will stay open at the explanation page.
- Upshot
This fallback proposal will make bitcoin QR codes meaningful regardless of if the user has a bitcoin app installed.--BitMark 16:05, 2 April 2011 (GMT)
Use-cases - buy this link
On the buy-this link, perhaps we should also incorporate an optional transaction id or something which would be passed along to the bitcoin client. Not really transaction but some sort of arbitrary data, only meaningful to the merchant. Something an online merchant can use to verify which transaction it has received is relevant to a purchase. Dantman 20:45, 18 April 2011 (GMT)
Why all the crazy representation stuff?
Amounthex, amountdec, exponents.. wtf? Why not settle on one normalized representation, this complicates parsing (and testing of parsers) for no good reason --Witchspace 05:14, 4 August 2011 (GMT)
- An earlier draft used a simple Satoshi count for amount, but some community members thought it needed to use more high-level units so we ended up with a combination of both. Parsing is not very complicated, and doing it this way allows people writing URIs to easily specify the value they want in any existing unit. The spec also has examples which can be used for testing. --Luke-jr 14:04, 10 August 2011 (GMT)
After Buy URL
It might be interesting to include an URL the user is directed to after payment.
Use case: buy digital goods for mobile devices.
Example: I want to buy a digital newspaper or app via QR code: I scan the code, pay the amount and am then redirected to a refreshing "waiting for payment" page that will show me the content when it considers the transaction valid.
Phelix 10:19, 22 January 2012 (GMT)