From rusty at rustcorp.com.au Sat May 6 04:08:47 2017 From: rusty at rustcorp.com.au (Rusty Russell) Date: Sat, 06 May 2017 13:38:47 +0930 Subject: [Lightning-dev] [RFC] Lightning payment format In-Reply-To: References: <87h918ghdv.fsf@rustcorp.com.au> Message-ID: <87h90yeieo.fsf@rustcorp.com.au> Olaoluwa Osuntokun writes: > However, it utilizes an > encoding whose rationale make sense for the Bitcoin address use-case, but in > my opinion, doesn't carry over those compelling traits to the LN payreq > use-case. I agree, but it's nice for QR codes too, and denser than hex. And now we're using your key recovery idea, having a checksum is not *completely* pointless. I've implemented and pushed fallback addresses in the example encoder/decoder, and tweaked the format slightly: the first 5-bit value is the witness version, or 17 for p2pkh, 18 for p2sh. It's now complete. In some places the encoding is a little awkward (trying to get on 5 bit boundaries), ideas welcome.