There is an issue with withdrawing sats out of Zeus.

What does ‘offline’ at the top of the screen indicate when I connect to my node from Zeus? The node is online and synced.

Would it cause issues on lightning for me to be running on-device ldk on zeus and an albyhub ldk on a computer using the same seed words? Not really interested in doing it (yet)...more curious if you can. 🤙

Yes it would. Do not do this.

Please email us. We’ll help you out.

what happened to LND node in the phone?

still there!

So bolt12?

Awesome release @ZEUS Here is an idea to handle offline receive through lnaddress - Zeus could unify its LDK and Cashu capabilities by turning its Lightning Address endpoint into a conditional settlement layer. When a sender resolves a user’s LN address, the Zeus backend would first check the availability of the user’s LDK node. If the node is online and reachable, it returns a standard Lightning invoice generated by the LDK wallet, allowing direct, non-custodial settlement over the user’s existing channels and LSP. If the node is offline, instead of failing the receive path, the endpoint returns a Lightning invoice issued by a configured Cashu mint. The sender still experiences a normal Lightning payment, but settlement occurs at the mint, which issues eCash tokens associated with the user. On the client side, Zeus already has the primitives to complete the loop. When the mobile device comes back online, the wallet detects pending mint-issued tokens (via blinded messages or encrypted delivery) and automatically redeems them into the user’s local wallet or converts them back into Lightning liquidity as appropriate. This creates a seamless dual-mode receive path: synchronous, self-custodial Lightning when online, and asynchronous, mint-buffered receipt when offline. The result is a single LN address that preserves sovereignty under availability while eliminating failed payments due to node downtime, effectively bridging Lightning’s real-time constraint with eCash’s store-and-forward model without exposing complexity to the sender.

This is a cool idea we've thought about a bit. I think this is the direction things will head towards but there are some privacy concerns here. Right now the best path is to leverage the automatically sweep to self-custody threshold under Ecash settings.

lmk if you're still having this issue. haven't been quite able to recreate this one

After more time it seems it is because I have a Zeus node in phone/ecash wallet with no open channels and that shows the offline message toward the top. (Probably because no lightning channels?) if I switch over to control of my node wallet the offline message stays visible. It goes away if I close Zeus and open it again just the node wallet

It's just based on your internet connectivity. Are you often using it in a place with poor connection?

No, that wallet just always shows offline for some reason. the node info screen shows it’s synced.

We diagnosed this issue today. For now it may help to change your default block explorer. A patch will be rolling out over the next few days. Apologies for the inconvenience.

Test build is ready:

GitHub

Release v13.0.1-rc1 · ZeusLN/zeus

v13.0.1 Highlights: Bug fixes What's Changed Full Changelog: v13.0.0...v13.0.1-rc1 Verifying the Release In order to verify the release, you'll n...

Cheers!