You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great if the app could add CLNRest options to the connect wallet screen.
The only coonection options for ZEUS wallet to Core Lightning are based on c-ligntning REST, taht are marked as deprecated.
It would have to expose:
The host address and port
The Rune
The Tor option
The text was updated successfully, but these errors were encountered:
I conquer. I'm a loyal Zeus Wallet myself (hail to their LNurl @zeuspay feat.).
In fact the core reason that brought me to Core Lightning at the first place is Zeus (c-rest), and lightning payments overhaul. I'm one who believes that rich and simplistic wallet implementations are what brings value to the network/users. The non-custodial wallets, ofc. The custodial ones can kindly be omitted eternally!!
I believe replacing the current c-lightning-rest option with the new clnrest URL should be fine, as nearly all applications have migrated to clnrest by now.
You'll have to pardon my profound ignorance about what's latest-scoops and al LN. I'm literally only 1.5 day in CLN ;)
I've noticed Zeus ability to scan a QR from the LND implementation (a beyond-words-heavyweight implementation I failed miserably with btw). If there was anything super cool to credit about, it was that; Zeus' wallet being able to QR connect to the node with only 2-clicks. Magical stuff!
Side note. I did noticed that it can do CLNrest too a few minutes ago though (manual input). I'll give this a try when I managed to bypass my NAT constraints here (need tor, I think).
It would be great if the app could add CLNRest options to the connect wallet screen.
The only coonection options for ZEUS wallet to Core Lightning are based on c-ligntning REST, taht are marked as deprecated.
It would have to expose:
The host address and port
The Rune
The Tor option
The text was updated successfully, but these errors were encountered: