pull down to refresh
20 sats \ 6 replies \ @BallLightning 2 Dec \ on: ZEUS Lightning Wallet Featured in Bitcoin News Interview lightning
I know you guys like Zeus, but I have had various problems from time to time (which I have written about here). My last problem was that somehow robosats rejected my wrapped invoice. I don't know whether this specifically was a problem with zeus, but it was yet another problem I experienced while using this wallet.
I know you guys like Zeus
We don't like Zeus because is good... we like it because is hard and advanced features rich node management.
Few users understand this statement. Maybe only those that are also running a desktop routing node, not as a hobby but as professional.
If you want an "easy to use" wallet app, there are plenty out there. But you must know that easy to use it doesn't mean is good or is offering everything you need.
reply
I don't jave enough money to run desktop routing node even as a hobby lol :)
reply
Nobody says you should do it. That's why Zeus is offering this option to run an small embedded node in your mobile device, where you don't need large amount of liquidity.
But you must learn all the details about it.
And I see you are doing it quite well, asking pertinent questions here on SN.
reply
Zeus is not for anybody. Is an advanced wallet app and you must know quite a lot about LN in order to be able to use it.
I know that Zeus devs are trying to make it as much as friendly possible but behind the scenes require good LN knowledge to use it. It is what it is, is a long way to the top if you wanna rock'n'roll...
Your particular case with robosats, is coming from the hold invoices, not from Zeus. I would not use wrapped invoices together with hold invoices. Wrapped invoices are used only in very specific cases not with robosats. What you can use with robosats are the routing hints.
Also an important aspect: when is used with robosats/hold invoices, activate persistent mode.
reply
I don't understand... There is no way as far as I know for the coordinator node to destinguish hodl from normal invoice. And my app was running in the foreground during this time. This was the message:
unknown hash, invalid amount or invalid final CLTV delta
Is this really caused by hodl invoices? What exactly in the invoice throws it off?
reply
This is a particular issues with hold invoices, not with Zeus.
By adding wrapped info about your LSP in the hold invoice it creates conflicts.
Is the same as using lnproxy.org for an invoice.
Read more about how hold invoices works.
reply