[Lightning-dev] Invoice Address Format

Rusty Russell rusty at rustcorp.com.au
Wed Nov 21 00:32:24 UTC 2018

Varunram Ganesh <contact at varunram.com> 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.


More information about the Lightning-dev mailing list