Zeus Wallet

This review contains affiliate links. If you buy via these links, I may earn a commission at no extra cost to you. It doesn’t change what I say about the product.

TL;DR

Zeus is the power user’s Lightning wallet. If you run your own Bitcoin and Lightning node — whether on Umbrel, Start9, myNode, or a bare LND server — Zeus is the missing mobile client. It connects directly to your node over Tor or clearnet, giving you full control over routing, channel management, and spending without any intermediary or third-party Lightning service provider. The trade-off is steep: Zeus assumes you know what a Lightning channel is, why inbound liquidity matters, and what it means to force-close a channel under the wrong conditions. It is not a wallet for first-time Bitcoin users.

What Zeus is

Zeus is an open-source Bitcoin and Lightning Network wallet built primarily for connecting to self-hosted Lightning nodes. It was originally created by developer Evan Kaloudis (known online as Kaloudis / k1z) in 2019, and has since grown into a full-featured Lightning mobile client maintained by the Zeus LN company with a small but technically skilled team.

The name and branding — ZEUS — reflects the wallet’s ambition: a mobile interface worthy of controlling the full power of a self-hosted Lightning node. Where most Lightning wallets abstract node operations away entirely, Zeus exposes them. You can see your channels, inspect routing fees, open new channels to specific peers, close channels cooperatively or forcefully, view the channel graph, and adjust routing fee parameters — all from your phone.

Zeus is free and open-source under the MIT license. The iOS app is available on the Apple App Store. The Android app has had a more complicated history: Zeus was briefly available on the Google Play Store but has at various points been distributed primarily through direct APK download and through F-Droid (the open-source Android app store). As of early 2026, check zeusln.com for the current recommended download source for your platform — the situation has shifted several times.

Reproducible builds are supported, meaning advanced users can verify that the compiled binary they are installing matches the published source code. This is a meaningful security feature that few mobile wallets offer.

Two modes: Remote node and Embedded node

Zeus operates in two distinct modes, which serve very different user profiles.

Remote node mode (the original use case)

In remote node mode, Zeus acts as a mobile frontend for a Lightning node you run elsewhere — typically on a dedicated home server, a Raspberry Pi, or a cloud instance. Your node runs 24/7 on that hardware. Zeus connects to it via your node’s API (REST or gRPC), authenticates with credentials you generate from the node, and gives you a mobile interface to manage it.

This is the mode Zeus was built for, and it is where Zeus shines. The experience feels like having a terminal to your node in your pocket — without needing to SSH into a server. You can check your channel balances, initiate payments, receive via Lightning invoice, and manage channels, all from your phone, while your node does the actual work of staying connected to the Lightning Network and routing payments.

Remote node mode requires:

• A running Lightning node (LND, Core Lightning, or Eclair)
• The node must be accessible over the internet — either directly (less private), behind a Tor hidden service (more private), or through a VPN
• You need the API credentials from your node (REST or gRPC connection details, macaroon or equivalent)

Embedded node mode

For users who do not run their own node, Zeus added an embedded node option: a bundled version of LND that runs directly on your phone. You do not need any external hardware. Zeus manages the LND instance, opens channels automatically, and handles the full Lightning stack on the mobile device itself.

This sounds appealing, but there are meaningful trade-offs. A Lightning node needs to be online to receive payments — if your phone is off or the app is closed, incoming payments will fail. Mobile nodes also drain battery and consume storage. Channel management is partly automated but still exposes more complexity than a product like Phoenix Wallet (ACINQ’s auto-managed wallet), which handles everything silently.

The embedded node is best thought of as a power-user feature for people who want full node sovereignty on mobile without any external server dependency, and who understand the operational requirements. It is not Phoenix’s seamless auto-channel experience — it is a real Lightning node on your phone.

Installation and setup

Remote node setup

1. Download Zeus from zeusln.com for your platform.
2. Generate connection credentials on your node:
   • LND: Use lncli bakemacaroon to create a scoped macaroon, or use the admin macaroon (less recommended). Grab the LND REST or gRPC endpoint. If your node runs behind Tor, note the .onion address.
   • Core Lightning: Generate an access token via the commando plugin or your node management interface.
   • Umbrel / Start9 / myNode: These platforms expose a “Connect Wallet” or “Pair” QR code specifically for Zeus. Scan it directly.
3. Pair via QR code: In Zeus, tap “Add a Node” and scan the QR code from your node management interface, or enter the connection details manually.
4. Choose Tor or clearnet: If your node exposes a .onion address, enable Tor in Zeus settings for improved privacy. Connecting over clearnet is faster but reveals your node’s IP address to Zeus’s network traffic.

The pairing flow is well-documented and most node management platforms (Umbrel, Start9, myNode, Raspiblitz) have dedicated Zeus connection flows that generate the QR code automatically.

Embedded node setup

1. Launch Zeus and select “Quick Connect” → “Embedded Node.”
2. Zeus initializes a fresh LND wallet and generates a seed phrase. Write this down. It is your recovery key.
3. Fund the on-chain wallet by sending BTC to the address Zeus displays.
4. Open channels to peers. Zeus can suggest peers or you can specify a specific node’s pubkey.
5. Once channels are open, you can send and receive Lightning payments.

Day-to-day UX

Once connected, Zeus’s home screen shows your on-chain balance, your Lightning balance, and recent transactions. The interface is capable but dense — there are many options, and Zeus does not hide them. Beginners will feel overwhelmed. Experienced Lightning users will feel at home.

Sending: Paste a BOLT 11 invoice or scan a QR code. Zeus shows the payment details (amount, routing fee estimate, destination node hint) before you confirm. For BOLT 12 offers (supported as of recent versions), you can paste the offer string directly.

Receiving: Generate a Lightning invoice of any amount. For larger amounts, Zeus checks whether you have sufficient inbound liquidity. If not, it will tell you — a more transparent (if less automated) approach than wallets like Phoenix, which silently open or splice channels.

On-chain support: Zeus also manages your node’s on-chain Bitcoin wallet. You can send and receive on-chain, check your UTXO set, and perform coin control — selecting specific UTXOs for on-chain transactions. This is a meaningful privacy and UTXO management feature that most mobile Lightning wallets omit entirely.

Channel graph: Zeus can display a visual representation of your node’s channel graph — the connections between your node and its peers. This is more educational than operationally critical for most users, but it helps illustrate how routing works.

Routing fees: You can set your node’s routing fees (the fee you charge when your node routes other people’s payments) directly from Zeus. This is only relevant if you’re running a routing node for profit, but it demonstrates the depth of control Zeus provides.

Channel management

Channel management is where Zeus truly differentiates itself from consumer Lightning wallets.

Opening channels: You can open a channel to any node on the Lightning Network by specifying the node’s pubkey (and optionally an IP/Tor address), choosing the channel capacity, and setting the fee rate for the channel-opening on-chain transaction. Zeus gives you full control over these parameters.

Closing channels: Cooperative close (fast, requires the peer to be online) and force close (unilateral, works even if the peer is offline, but includes a timelock delay of typically 144 blocks — about one day) are both available. Zeus warns you about force-close consequences clearly.

Rebalancing: Zeus supports loop-in and loop-out operations (via the Lightning Loop service) to move liquidity between channels. For nodes with many channels, rebalancing is crucial to maintaining the ability to both send and receive. Zeus also supports circular rebalancing — routing a payment through your own node via a specific path to shift balance between channels.

Custom routes: Advanced users can specify a custom routing path for payments — forcing the payment through specific intermediate nodes. This is a niche feature, but useful for testing routing paths or avoiding specific intermediaries.

Zeus vs Phoenix — a direct comparison

The most instructive comparison is Zeus versus Phoenix Wallet, since they represent two different philosophies for non-custodial Lightning.

Phoenix = auto-managed with ACINQ trust. Phoenix handles all channel operations silently. You never open, close, or rebalance channels — ACINQ’s infrastructure manages all of that. Your channel peer is always an ACINQ-operated node. You control your seed, but not your routing infrastructure.

Zeus = your node, your rules. Zeus connects to a node you control. You choose your channel peers, you set routing fees, you manage your own liquidity. Your money routes through your node’s channels, not through ACINQ’s infrastructure. The trust model is different: you trust yourself, not a third party.

The right choice depends on your situation:

Most people starting out with Lightning should use Phoenix. When you understand Lightning well enough to feel constrained by Phoenix’s automation — when you want to choose your own peers, control your routing fees, or inspect your channel database — that’s when Zeus makes sense.

Who Zeus is for

Zeus is the right wallet if:

• You already run a Bitcoin and Lightning node on Umbrel, Start9, myNode, Raspiblitz, or bare LND/Core Lightning
• You want a mobile interface to your node without SSH access
• You care about routing sovereignty — not having your payments routed through a third party’s infrastructure
• You want full channel control: opening channels to specific peers, closing when you choose, managing your UTXO set with coin control
• You’re running a routing node and need to manage fees from your phone

Zeus is the wrong wallet if:

• You’re new to Bitcoin or Lightning and don’t yet understand what a channel is
• You don’t run your own node and don’t want to
• You want a zero-setup Lightning wallet that “just works”
• You need to receive Lightning payments reliably on a mobile device with no always-on backend (the embedded node helps, but it’s not seamless)
• You’re looking for something to recommend to a non-technical friend

The divide is clear: Phoenix is the wallet for people who want self-custodial Lightning without infrastructure responsibility. Zeus is the wallet for people who have accepted that infrastructure responsibility and want the best mobile interface for it.

Open source and reproducible builds

Zeus is licensed under the MIT license. The source code is available at github.com/ZeusLN/zeus. The project publishes reproducible build instructions, meaning you can verify that the app distributed in the App Store or as an APK corresponds to the published source code — a form of trust-minimization that is rare in mobile app distribution.

Tor support is first-class: Zeus can route all traffic through Tor, hiding your connection to your node from network observers. This is particularly valuable for remote node users who want to keep their node’s IP address private even from their mobile carrier.

Verdict

Zeus earns its 4.6 rating by doing something genuinely hard: making full Lightning node management usable from a phone. It is not the right tool for everyone — the learning curve is steep, and you need your own node to get the most out of it. But for the user who has made the commitment to run their own node and wants sovereign control over their Lightning experience, Zeus is the best mobile interface available.

The 0.4 deduction from a perfect score reflects the UX density (the interface can be overwhelming), the operational requirements (most people can’t run a Lightning node), and the embedded node’s limitations compared to a full always-on server-side node. These are not bugs — they are honest trade-offs of the self-sovereign approach. Zeus makes the right call at every decision point; the limitations are inherent to the territory.

If you run Umbrel, Start9, or bare LND, install Zeus. You will not go back to SSH.

Sources:

• Zeus official site: zeusln.com
• Zeus GitHub (MIT license): github.com/ZeusLN/zeus
• BOLT 11 invoice specification: github.com/lightning/bolts/blob/master/11-payment-encoding.md
• BOLT 12 offers specification: github.com/lightning/bolts/pull/798
• LND (Lightning Network Daemon): github.com/lightningnetwork/lnd
• Core Lightning: github.com/ElementsProject/lightning