From ZmnSCPxj at protonmail.com  Thu Jun  1 03:48:46 2017
From: ZmnSCPxj at protonmail.com (ZmnSCPxj)
Date: Wed, 31 May 2017 23:48:46 -0400
Subject: [Lightning-dev] [RFC] Lightning invoice/payment format draft
In-Reply-To: <LgBEZTIwZietTZKmz1eNigHGsoFPyrPFmGjxfpYuYqktbwXo6doj_Wfbsb9OGQ5VY1s-eTcBtJQ-qRUxTyRvZD3SPA2LkXbsVsZQ0xUiork=@protonmail.com>
References: <874lw0h4y3.fsf@rustcorp.com.au>
	<LgBEZTIwZietTZKmz1eNigHGsoFPyrPFmGjxfpYuYqktbwXo6doj_Wfbsb9OGQ5VY1s-eTcBtJQ-qRUxTyRvZD3SPA2LkXbsVsZQ0xUiork=@protonmail.com>
Message-ID: <Yvxsx9v_dQ2h0mJeS1lYDUQ2wL3k-Eq03IjY99YVwNFtItAQNdAMamEsgb21Q154g1tzbeq7OWAPVJ4XhallmiaD9cTH8CxLDfmsCsLov98=@protonmail.com>

Good morning,

>Or do I mistake my understanding of bech32?

Looking again at bech32 spec, yes, my understanding is wrong: the character "1" is not allowed in the data part, so the last "1" digit in the bech32 string is unambiguously the separator between the human-readable and data parts, please ignore me.

Regards,
ZmnSCPxj
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20170531/2f45c053/attachment.html>