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,
Good morning Rusty,
The fact that amount is optional, and the separator character between
human-readable and data is the character "1", may mean some trouble with
parsing of the optional amount.
Currently, the version is 0, which translates to the character "q" appearing
after "1". So 1q is
