From 955e874acc535ab2c74c1cf0eab61896ea4224ff Mon Sep 17 00:00:00 2001 From: Rusty Russell Date: Mon, 21 Aug 2017 14:19:23 +0930 Subject: [PATCH] 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: #206 Signed-off-by: Rusty Russell --- .aspell.en.pws | 1 + 11-payment-encoding.md | 6 ++++++ 2 files changed, 7 insertions(+) diff --git a/.aspell.en.pws b/.aspell.en.pws index 905bebd..5f4d6c6 100644 --- 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 index f015c92..2d45a24 100644 --- 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