BIP 0020: Difference between revisions
Jump to navigation
Jump to search
More Examples |
LAN Example |
||
Line 29: | Line 29: | ||
Request to send 5 uBTC: | Request to send 5 uBTC: | ||
bitcoin:///18pnDgDYFMAKsHTA3ZqyAi6t8q9ztaWWXt?amount=500 | bitcoin:///18pnDgDYFMAKsHTA3ZqyAi6t8q9ztaWWXt?amount=500 | ||
Request to send 5 uBTC over the LAN to 192.168.1.2: | |||
bitcoin://192.168.1.2/18pnDgDYFMAKsHTA3ZqyAi6t8q9ztaWWXt?amount=500 | |||
Request to send 50 BTC with message: | Request to send 50 BTC with message: |
Revision as of 00:53, 10 January 2011
I propose a scheme like this:
() means optional, $* are placeholders
bitcoin://($host)/$address?amount=$size$unit(&label=$label)(&message=$message)
Variables
- label: Label for that address (e.g. name of receiver)
- address: bitcoin address
- message: optional message that is shown to the user after scanning the QR code
- size: amount of $unit
- unit: BTC, [ᵗˢᵐᵇ]TBC[ᵗˢᵐᵇ], or null/omitted (which refers to the base unit)
Examples
Just the address:
bitcoin:///18pnDgDYFMAKsHTA3ZqyAi6t8q9ztaWWXt
Address with name:BTC
bitcoin:///18pnDgDYFMAKsHTA3ZqyAi6t8q9ztaWWXt?label=tcatm
Request to send 20.30 BTC to tcatm:
bitcoin:///18pnDgDYFMAKsHTA3ZqyAi6t8q9ztaWWXt?amount=20.30BTC&label=tcatm
Request to send 400 TBC to Luke:
bitcoin:///1KczVqwopWXQdFLe5sNQbpCq7yGSmXx2oo?amount=400TBC
Request to send 5 uBTC:
bitcoin:///18pnDgDYFMAKsHTA3ZqyAi6t8q9ztaWWXt?amount=500
Request to send 5 uBTC over the LAN to 192.168.1.2:
bitcoin://192.168.1.2/18pnDgDYFMAKsHTA3ZqyAi6t8q9ztaWWXt?amount=500
Request to send 50 BTC with message:
bitcoin:///18pnDgDYFMAKsHTA3ZqyAi6t8q9ztaWWXt?amount=50BTC&label=tcatm&message=Payment%20for%20product%20xyz
Characters must be URI encoded properly.