ZEUS v13.0.0 is now available. This release features:
- New 'node in the phone': LDK Node
- New onboarding process
- Embedded LND: Migrate devices with channels intact
- Cashu rewrite + offline mode
...
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.
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.
2❤️1
