Multiple port interfaces

[seth586]

The connection standard should be able to specify REST, lnd RPC (and maybe bitcoind protocol & RPC) ports individually so wallets can choose the appropriate connection.

For example, consider the following tor hidden service torrc config file to serve light clients Zeus (REST 8080) Pebble (lnd RPC 10009) and a light bitcoin wallet (bitcoind RPC 8332)

HiddenServiceDir/usr/local/etc/tor/lnd_apis/
HiddenServiceVersion 2
HiddenServiceAuthorizeClient stealth myandroid
HiddenServicePort 10009 127.0.0.1:10009
HiddenServicePort 8080 127.0.0.1:8080
HiddenServicePort 8332 127.0.0.1:8332

This would require three different qr codes to generate. The additional data to add all 3 ports to 1 qr code would be minimal, and help standardize remote connections across the ecosystem.

[ottosuess]

i think it's preferable to create a unique qr code for each of your specific need.

just to keep the lndconnect format as simple and focused as possible.

Internally we're using a URI format for the connection strings and try to stick to RFC 3986. Like a URI lndconnect should uniquely identify one way to connect to lnd.