BOLT 11: recommend URI schemes.

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: bitcoin#206 Signed-off-by: Rusty Russell <[email protected]>
luke-jr · Aug 22, 2017 · 955e874 · 955e874
1 parent 4bcf9dd
commit 955e874
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 0 deletions.
diff --git a/.aspell.en.pws b/.aspell.en.pws
@@ -304,3 +304,4 @@ A
 AAAA
 SRV
 TTL
+URI
diff --git a/11-payment-encoding.md b/11-payment-encoding.md
@@ -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
-Original file line number
+Diff line change
@@ Expand Up / @@ -304,3 +304,4 @@ A @@
     AAAA
     SRV
     TTL
+    URI