Expose the RPC litrpc.Proxy.GetInfo via LNC wasm about lightning-node-connect HOT 4 OPEN

Thanks for the additional context here @ellemouton. I also agree that Stop shouldn't be exposed over LNC. We'd still like to have a way to get the litd version in addition to faraday so I'd like to add that as a TODO as well.

from lightning-node-connect.

I'm wondering if it would make more sense to include version numbers in the subserver RPC instead of exposing GetInfo?

It looks like GetInfo only returns version information for litd:

If the subserver status server returned version information for all subservers it would be a lot more useful for feature detection for loop, pool, etc. not just lit

from lightning-node-connect.

The issue is on the LiT side. Currently we dont expose Proxy calls over LNC since it would also expose things like Stop. So either we just say we are ok with the user being able to call Stop over LNC if they have an admin session in which case this is an easy fix on the LiT side. Otherwise we should consider splitting up the Proxy service a bit.

from lightning-node-connect.

If the subserver status server returned version information for all subservers it would be a lot more useful for feature detection for loop, pool, etc. not just lit

I think these are already queryable directly though? Pool, Loop and Taproot-assets all have a GetInfo call. So those can just be called directly. So the only TODO here imo is adding a GetInfo to faraday

from lightning-node-connect.