Zeus vs Phoenix Wallet: Self-Custodial Lightning Compared

Zeus vs Phoenix: Overview

Zeus and Phoenix are two of the most capable self-custodial Lightning wallets available, but they target fundamentally different users. Zeus gives power users full control over their Lightning node and channel configuration, with support for both an embedded on-device node and connections to remote infrastructure. Phoenix abstracts away every technical detail behind automated channel management powered by ACINQ's Lightning Service Provider. Both wallets are open source, non-custodial, and capable of sending and receiving Lightning payments, but the path from install to first payment looks very different.

This comparison covers node architecture, channel management, fee structures, privacy models, backup approaches, and platform support to help you decide which wallet fits your needs.

For a broader view of the full Lightning wallet landscape, see our Lightning wallet comparison tool.

Node Architecture

The core difference between Zeus and Phoenix is how each wallet handles the Lightning node layer. This architectural decision shapes everything from setup complexity to privacy to what you can do with the wallet.

Zeus: Embedded LDK Node or Remote Node

Zeus v13.0.0 (April 2026) introduced a major architecture change: the default embedded node switched from LND to LDK Node. This was described by the Zeus team as "a full engine swap" and makes Zeus one of the largest mobile wallets shipping LDK Node. The embedded LND backend remains available as a legacy option (running LND v0.21.2-beta as of v13.2.0).

Zeus can also connect to a remote Lightning node over the network. Supported backends include LND, Core Lightning, and LNDHub instances (such as LNbits or Alby). This makes Zeus a versatile mobile frontend for users who already run their own Lightning infrastructure. All connections are routed through Tor by default, protecting the IP address of both the mobile device and the remote node.

Phoenix: On-Device Node with Trampoline Routing

Phoenix runs ACINQ's lightning-kmp (Kotlin Multiplatform) Lightning node on the device. Unlike Zeus's general-purpose embedded node, this implementation is purpose-built for the mobile wallet use case: it does not download or sync the Lightning gossip graph. Instead, Phoenix uses trampoline routing to delegate pathfinding to ACINQ's node. The result is faster startup, lower bandwidth usage, and better battery life, but with a significant privacy tradeoff: ACINQ has stated that Phoenix currently offers "no advantage regarding privacy over existing, hosted, custodial wallets" because the trampoline node sees payment destinations and amounts for BOLT 11 payments.

There is no option to connect Phoenix to a different node or backend. The wallet is tightly integrated with ACINQ's infrastructure and cannot be decoupled from it. This is the price of the streamlined experience.

Channel Management

How channels are opened, managed, and resized determines both the user experience and the cost structure of each wallet.

Zeus: Manual Control with LSP Option

Zeus gives users full control over their channels. You can manually open channels with any peer on the Lightning Network, choose your channel capacity, set routing fees, and close channels cooperatively or unilaterally.

For users who do not want to manage channels manually, Zeus integrates with OLYMPUS by ZEUS, its own LSP. OLYMPUS offers several channel types: just-in-time (JIT) channels that open automatically when you receive a payment (100,000 to 5,000,000 sats), purchase-in-advance channels via LSPS1 (100,000 to 10,000,000 sats with user-selectable lifetime from 2 weeks to 12 months), and channels opened with on-chain funds (150,000 to 1,500,000 sats). The maximum total capacity across all OLYMPUS channels is 10,000,000 sats per user.

Zeus v13.0.0 also introduced a graduated wallet experience with Mortal, God, and Olympian tiers, allowing users to choose their preferred level of complexity. The Mortal tier hides most channel management details, while Olympian exposes everything.

Phoenix: Automated Splicing

Phoenix maintains exactly one channel with ACINQ's node. When you need more capacity (for example, to receive a payment larger than your current inbound balance), Phoenix automatically performs an on-chain splice to resize the channel without closing it. Users see a single unified balance and never interact with channel concepts directly.

This model was introduced in the Phoenix 2.0 rewrite (mid-2023) and replaced the earlier multi-channel approach. Splicing is transparent: the wallet shows a fee estimate before the operation and handles the on-chain transaction automatically. The cost is 1% of the added liquidity plus mining fees (minimum 3,000 sats). Users can also manually request liquidity from 100,000 to 10,000,000 sats, guaranteed for one year. During periods of high on-chain congestion, these fees can be significant. For a deep dive into how splicing works, see our research on splicing Lightning channels.

Fee Structure Comparison

Fees are one of the most important factors when choosing a Lightning wallet. Zeus and Phoenix have very different fee models, and which one is cheaper depends on your usage pattern.

Zeus's per-payment cost is lower: standard Lightning routing fees are typically a few sats regardless of payment size. Phoenix charges 0.4% plus 4 sats on every send, so a 1,000,000-sat payment costs 4,004 sats in fees. For frequent senders moving larger amounts, this difference adds up quickly.

On the liquidity side, the comparison depends on channel size. For channels under 1,000,000 sats, Zeus's OLYMPUS LSP charges a flat 10,000 sats, while Phoenix charges 1% plus mining fees. A 500,000-sat channel costs 10,000 sats via Zeus but roughly 5,000 sats plus mining fees via Phoenix, making Phoenix cheaper in that range. Above 1,000,000 sats, both charge approximately 1%, but Phoenix adds mining fees on top. Users who open channels manually in Zeus pay only mining fees, and those connecting to their own remote node pay zero LSP fees entirely. For more on how fee markets affect Lightning economics, see our research.

Privacy and Security

Both wallets are self-custodial: neither ACINQ nor Zeus can access or freeze your funds. The privacy models differ significantly, however.

Zeus routes all connections through Tor by default. The embedded node operates as a private, unannounced node: it does not route other users' payments and its channels are not visible on the public Lightning graph. Zeus also performs its own pathfinding using the local gossip graph, so no single third party sees the destination of your payments. Additional privacy features include coin control for on-chain transactions, stealth mode to hide sensitive data on screen, and support for custom Mempool instances (v13.2.0) to avoid leaking fee estimation queries.

Phoenix has weaker privacy properties. It delegates all pathfinding to ACINQ via trampoline routing, meaning ACINQ can observe the destination and amount of BOLT 11 payments. ACINQ has been transparent about this limitation, stating publicly that Phoenix currently offers no privacy advantage over custodial wallets in this regard. BOLT 12 support partially addresses this: with BOLT 12 Offers, ACINQ no longer learns the destination node. However, most Lightning payments still use BOLT 11. Phoenix's built-in Tor support was removed in early 2025; users who want IP-level privacy must now install the external Orbot app separately.

For users where payment privacy is a high priority, Zeus provides substantially stronger guarantees. For a broader analysis, see our research on Lightning Network privacy.

Backup and Recovery

Recovery from device loss is one of the most critical features in any self-custodial wallet. Zeus and Phoenix handle this differently.

Zeus (LDK Node mode) uses a 12-word seed phrase by default, with a 24-word option added in v13.2.0. The LDK Node backend supports device migration that transfers all channel state, on-chain funds, Lightning balances, and Cashu ecash funds instantly to a new device via the seed. For the legacy embedded LND mode, Zeus uses the aezeed 24-word format and provides static channel backups (SCB) for channel recovery. Users can optionally back up channel state to the OLYMPUS server.

Phoenix uses a 12-word BIP-39 seed phrase with standard BIP-84 derivation. Channel state is automatically encrypted and backed up to ACINQ's servers (on iOS, iCloud backup is also available). Recovery is straightforward: reinstall the app, enter the seed, and the encrypted state is downloaded. If the backup is unavailable, Phoenix falls back to a force close of the channel, returning funds on-chain after a timelock delay of two to four weeks. Payment history is not recoverable from the seed alone.

Phoenix's automatic backup is more user-friendly. Zeus's LDK Node migration provides a similarly smooth experience for device upgrades, though users still need to safeguard their seed phrase.

Platform Support and Server Options

Phoenix was removed from US app stores on May 3, 2024, following the Samourai Wallet indictment and associated regulatory uncertainty. ACINQ advised US users to drain their wallets. Phoenix returned to both the iOS App Store and Google Play on April 8, 2025, after the regulatory environment shifted. As of 2026, both wallets are available to US users without restrictions.

Phoenix offers phoenixd, a headless server version that exposes an HTTP API for programmatic Lightning payments. It runs on Linux (x86/ARM), macOS, and Windows (via WSL) and provides automated liquidity management with the same fee structure as the mobile wallet. A BTCPay Server plugin enables merchant integration. Zeus does not offer its own server daemon, but since it connects to standard LND or CLN backends, server users run those implementations directly.

On-Chain Fallback and Force Close Behavior

Both wallets allow users to move funds on-chain when needed, but the mechanisms differ.

Phoenix supports splice-out: users can send to a standard Bitcoin address by resizing the channel downward via an on-chain transaction. This is a cooperative operation with ACINQ's node and costs only mining fees. If ACINQ becomes unreachable, Phoenix can unilaterally force-close the channel. With Taproot channel support (introduced in Phoenix v2.7.0 in October 2025), cooperative close transactions are indistinguishable from standard P2TR spends on-chain, improving privacy. The Swaproot mechanism (v2.2.0) uses MuSig2 key aggregation for on-chain receives, making swap-in transactions 20-30% cheaper and indistinguishable from regular Bitcoin transactions.

Zeus provides direct on-chain wallet functionality alongside the Lightning node. Users can hold UTXOs in the embedded wallet independently of any channels. Channel closes (cooperative or forced) return funds to the on-chain wallet. Zeus also added Taproot channel support in late 2025 for reduced on-chain fees. Since Zeus gives users control over coin selection and channel parameters, users can manage their on-chain footprint more deliberately.

How to Choose

Choose Zeus if you want maximum control over your Lightning setup. Zeus is the right choice for users who already run a home node, want to manage their own channels, care about payment privacy (Tor by default, local pathfinding, private node), or want to minimize per-payment fees. The graduated tier system (Mortal/God/Olympian) means beginners can start with a simplified view and unlock complexity as they learn. The tradeoff is that Zeus's embedded node takes longer to sync on startup and requires more hands-on management than Phoenix.

Choose Phoenix if you want the simplest self-custodial Lightning experience available. Phoenix handles channel management, liquidity, backups, and pathfinding automatically. You pay higher per-send fees (0.4% + 4 sats) and higher liquidity fees (1%) for this convenience, and you accept that ACINQ sees your payment destinations for BOLT 11 payments. Phoenix is the better choice for users who simply want to send and receive Lightning payments without thinking about node operations.

For users where on-chain channel setup costs are a concern, newer approaches like Spark eliminate per-user channel creation entirely. Spark-based wallets allow instant onboarding without mining fee overhead or channel management. For a comparison of Phoenix against another popular mobile wallet, see our Phoenix vs Breez comparison.

Frequently Asked Questions

Is Zeus or Phoenix better for beginners?

Phoenix is simpler for beginners. It presents a single balance, handles all channel operations automatically, and requires no understanding of Lightning node concepts. Zeus v13.0.0 introduced a graduated tier system (Mortal/God/Olympian) that can simplify the interface, but the embedded node still requires initial sync time and exposes more technical concepts than Phoenix. If you have never used a Lightning wallet before, Phoenix provides a faster path to your first payment.

Can Zeus connect to my own Bitcoin node?

Yes. Zeus can connect to a remote LND, Core Lightning, or LNDHub instance over Tor or direct IP. This is one of Zeus's key differentiators: it functions as a mobile interface for your existing Lightning infrastructure. Many node-in-a-box solutions (Umbrel, Start9, RaspiBlitz, myNode) provide easy pairing with Zeus through connection URIs or QR codes.

What are the maximum payment sizes for Zeus and Phoenix?

Maximum payment size in both wallets is determined by channel capacity. Phoenix's manual liquidity request supports up to 10,000,000 sats (0.1 BTC) per channel. Zeus's OLYMPUS LSP also caps total capacity at 10,000,000 sats across all channels. Users who open channels manually in Zeus can set any size the counterparty accepts. Both wallets support multi-path payments to split large payments across available capacity.

Does Zeus support splicing?

Not yet. As of September 2026, Zeus has an active pull request for LDK-based channel splicing (splice-in and splice-out) with end-to-end verification completed, but it has not shipped in a production release. Channel resizing in Zeus currently requires closing the existing channel and opening a new one. Phoenix, built on ACINQ's lightning-kmp library, was one of the first wallets to ship production splicing support in 2023.

Which wallet has better privacy?

Zeus offers substantially stronger payment privacy. It routes all traffic through Tor by default, performs pathfinding locally, and operates as a private unannounced node. ACINQ has publicly stated that Phoenix offers no privacy advantage over custodial wallets because trampoline routing exposes payment destinations and amounts. Phoenix removed built-in Tor support in early 2025, requiring the external Orbot app for IP-level privacy. BOLT 12 partially improves this by hiding destination nodes, but ecosystem-wide adoption remains limited.

What happens if ACINQ or Zeus shuts down?

Both wallets are self-custodial, so your funds are secured by your private keys regardless of what happens to either company. If ACINQ shut down, Phoenix users could force-close their channel and recover funds on-chain after a timelock period (typically two to four weeks). If Zeus's OLYMPUS LSP went offline, channels opened through it could still be closed cooperatively or unilaterally. Users connected to their own remote node are completely independent of Zeus's infrastructure. For more on how Lightning Service Providers work, see our research.

Does Phoenix support BOLT 12 Offers?

Yes. Phoenix added BOLT 12 Offers support in v2.3.x (mid-2024), enabling reusable, non-expiring payment codes that do not require a server. BOLT 12 also improves privacy by hiding the destination node from ACINQ's trampoline router. Zeus does not support BOLT 12 natively but supports LNURL for similar reusable payment functionality (LNURL requires an always-online HTTP server). For more on how these formats compare, see our Lightning invoices research.

Can I use Zeus without the OLYMPUS LSP?

Yes. The OLYMPUS LSP is optional. Zeus can be used in fully manual mode where you open channels directly with any Lightning peer, set your own fees, and manage liquidity yourself. You can also connect Zeus to a remote node you control, bypassing all of Zeus's built-in infrastructure entirely. This is the primary use case for users running home nodes who want a mobile interface for their existing setup.

This tool is for informational purposes only and does not constitute financial advice. Fee structures, features, and availability are based on publicly available information as of September 2026 and may change. Always verify current details on each wallet's official website before making decisions.