mirrors/lightning-bolts
1
0
Fork 0
mirror of https://github.com/lightning/bolts.git synced 2025-03-10 09:10:07 +01:00
Code Issues Projects Releases Wiki Activity

BOLT 11: recommend URI schemes.

Browse source 
This is unofficial, since we don't have IANA tag, but it doesn't
clash with any existing one.  We'll see if this turns out to be something
people want.

Closes: #206
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
This commit is contained in:
Rusty Russell 2017-08-21 14:19:23 +09:30
parent 4bcf9dde7e
commit 955e874acc
2 changed files with 7 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
.aspell.en.pws
View file

@ -304,3 +304,4 @@ A
AAAA
SRV
TTL
URI

6
11-payment-encoding.md
View file

@ -14,6 +14,12 @@ simply reused here even though its 6-character checksum is optimized
for manual entry, which is unlikely to happen often given the length
of lightning invoices.
If a URI scheme is desired, the current recommendation is to either
use 'lightning:' as a prefix before the BOLT-11 encoding (note: not
'lightning://'), or for fallback for bitcoin payments, use 'bitcoin:'
as per BIP-21, with key 'lightning' and value equal to the BOLT-11
encoding.
## Requirements
A writer MUST encode the the payment request in Bech32 as specified in