From rusty at rustcorp.com.au Wed Nov 21 00:32:24 2018 From: rusty at rustcorp.com.au (Rusty Russell) Date: Wed, 21 Nov 2018 11:02:24 +1030 Subject: [Lightning-dev] Invoice Address Format In-Reply-To: <253946303.14656.1542735239405@privateemail.com> References: <253946303.14656.1542735239405@privateemail.com> Message-ID: <87o9ajp8x3.fsf@rustcorp.com.au> Varunram Ganesh writes: > Now, I am no expert on error encoding formats, but I think that bech32 is under optimised for invoices (whose lengths are greater than 71). Related to this, is there a reason why we use hex encoded pubkeys in lightning? Unless I'm missing something, I think bech32 is better to use in this context. Please correct me if I'm wrong. No, you're right. It was chosen because it's an existing encoding which already exists in the bitcoin ecosystem. The signature on an invoice provides a far stronger guarantee than the 6-char checksum anyway. Cheers, Rusty.