Robert Olsson [ARCHIVE] on Nostr: 📅 Original date posted:2018-04-07 📝 Original message: Hello all, I seem to not ...
📅 Original date posted:2018-04-07
📝 Original message:
Hello all,
I seem to not find a bolt regarding the QR code of node at ip:port
It seems eclair only supports the format hex at ip:port format, and i haven't
tried any other mobile wallets.
I thought there would be support for bech32 nodeid:s to keep the QR small,
but it doesn't seem that way.
If it isn't standardized yet, i think we should do it soon so all wallets
will support it from start and we can avoid bulky QR codes.
To fully utilize QR it should work with charset in text-mode, so i would
suggest a format like
lightning:ln1bech32nodeid/ipnumber/port
where /port is optional if port is 9735
this is to avoid @ and confusion of : in ipv6 and :portnumber
(skip '[' and ']' in ipv6)
another approach would be to encode ip and portnumber in bech32 as well. my
opinion is that everything coded entirely in bech32 shouldn't need a
protocol so the 'lightning:' part could possibly be omitted as well.
or did i just miss a bolt somewhere?
best regards
Robert Olsson
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20180407/4dc3c679/attachment.html>;
📝 Original message:
Hello all,
I seem to not find a bolt regarding the QR code of node at ip:port
It seems eclair only supports the format hex at ip:port format, and i haven't
tried any other mobile wallets.
I thought there would be support for bech32 nodeid:s to keep the QR small,
but it doesn't seem that way.
If it isn't standardized yet, i think we should do it soon so all wallets
will support it from start and we can avoid bulky QR codes.
To fully utilize QR it should work with charset in text-mode, so i would
suggest a format like
lightning:ln1bech32nodeid/ipnumber/port
where /port is optional if port is 9735
this is to avoid @ and confusion of : in ipv6 and :portnumber
(skip '[' and ']' in ipv6)
another approach would be to encode ip and portnumber in bech32 as well. my
opinion is that everything coded entirely in bech32 shouldn't need a
protocol so the 'lightning:' part could possibly be omitted as well.
or did i just miss a bolt somewhere?
best regards
Robert Olsson
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20180407/4dc3c679/attachment.html>;