From f8ef3b42221295f3913aa1b0663221dadd5776f6 Mon Sep 17 00:00:00 2001
From: Rusty Russell <rusty@rustcorp.com.au>
Date: Tue, 4 Aug 2020 06:48:22 +0930
Subject: [PATCH] BOLT 11: make UPPERCASE explicit. (#677)

Explicitly mirror the BIP-173 advice for QR codes, and note the reader
requirements.

Fixes: #659
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
---
 11-payment-encoding.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/11-payment-encoding.md b/11-payment-encoding.md
index 5bcc9b1..b682413 100644
--- a/11-payment-encoding.md
+++ b/11-payment-encoding.md
@@ -35,10 +35,12 @@ encoding.
 
 A writer:
    - MUST encode the payment request in Bech32 (see BIP-0173)
+   - SHOULD use upper case for QR codes (see BIP-0173)
    - MAY exceed the 90-character limit specified in BIP-0173.
 
 A reader:
   - MUST parse the address as Bech32, as specified in BIP-0173 (also without the character limit).
+	- Note: this includes handling uppercase as specified by BIP-0173
   - if the checksum is incorrect:
     - MUST fail the payment.