-
-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make getinfo
more awesome
#192
Comments
Moving this to the next release in june |
I did some work on this. Will put up a PR tomorrow. |
uuh amazin, lets see if we can include it inside this release because I am a little bit in delay |
This is not finished @Harshit933 Are you able to add the address specified by the user inside the getinfo response? Currently we do not know where the node is listening, if it is listening somewhere |
@vincenzopalazzo can we close this? |
The response is reach like the core lightning one? I do not thing so Why you want to close it? |
I thought #229 were the final steps for the issue. |
With code there is never a final step, but the get info needs more love anyway. The core lightning one is more complete https://docs.corelightning.org/reference/lightning-getinfo#synopsis |
As discussed on discord, we should add more information about the node inside
getinfo
. Make it similar to thecore-lightning
implementation.The text was updated successfully, but these errors were encountered: