Future of the project?
1ma opened this issue · comments
Core Lightning has its own REST API now and even seems maintained by the same developers as c-lightning-REST, so I'm wondering what is the long term perspective for this project.
Are clnrest and c-lightning-REST meant to coexist and serve different use cases, or will RTL work eventually with clnrest and make c-lightning-REST redundant?
Hi @1ma RTL will be migrated to clnrest soon.
Would urge any c-lightning-REST dependent projects to migrate there as well. Will officially put this project in deprecation mode after RTL migration, giving time for other projects to migrate.
Eventually this project will not be supported in the long run.
@saubyk That's a great news - do you have any guess/timeframe, when the version of RTL migrated to cln-rest could be released? Thanks
Hi @Nogyara the next release of RTL is planned with clnrest integration
Cannot give you an exact timeline. Likely in a month or so
cc: @ShahanaFarooqui
The migration is already underway at https://github.com/Ride-The-Lightning/RTL/tree/clnrest-migration. The code has been updated and I am currently testing it with clnrest.
But need more time to estimate a release date.
Because of this clnrest.py plugin, I have not had a phone wallet eversince. Hopefuly this finally finds some stabilization soon as right now all I can do is maintain my CLN instance through the CLI, which is rather inpractical. :)
Thank you for your hard work!
I found RTL-0.15 with clnrest.py WAY slower than with c-lightning-REST.
Also ZeusLN uses c-lightning-REST and Evan hasn't "touched clnrest yet".
Both are pretty crucial apps, if you are working with CLN nodes.
Do you share this experience?
@martinneustein I haven't received any complain about clnrest being slower than c-lightning-REST. Have you done any comparative analysis?