Phoenix Wallet has become the benchmark for self-custodial Lightning wallets in 2026. Built by ACINQ — one of the three original Lightning implementation teams — Phoenix uses splicing to manage a single channel that grows and shrinks as you need, eliminating the channel management complexity that has historically made Lightning difficult for regular users. If you want to send and receive bitcoin over the Lightning Network without running your own node or understanding channel mechanics, Phoenix is the wallet that makes it possible.
This review evaluates Phoenix Wallet’s architecture, fee structure, user experience, privacy properties, and real-world performance based on extensive testing in early 2026.
Phoenix Wallet Specifications
| Specification | Detail |
|---|---|
| Developer | ACINQ (Paris, France) |
| Lightning Implementation | lightning-kmp (ACINQ’s mobile Lightning library) |
| Custody Model | Self-custodial (your keys, your coins) |
| Platforms | Android, iOS |
| Channel Management | Automated via splicing (single channel) |
| On-chain Support | Yes (unified balance via swap-in/splice) |
| Invoice Support | BOLT 11, BOLT 12 (Offers), LNURL |
| Backup | 12-word seed + encrypted copy of your channel data on ACINQ’s node |
| Privacy | Trampoline routing (ACINQ sees payment destinations) |
| License | Open source (Apache 2.0) |
| Tor Support | Yes |
Architecture: How Phoenix Actually Works
Phoenix runs a lightweight Lightning node directly on your phone, built on lightning-kmp, ACINQ’s mobile Lightning library (ACINQ’s server software, Eclair, runs the node at the other end of your channel). Your private keys and channel state are stored locally on your device — ACINQ never has access to your funds. This makes Phoenix genuinely self-custodial, unlike wallet apps that connect to a third-party custodian behind a friendly interface.
The Splicing Innovation
Phoenix’s defining technical achievement is its use of splicing for channel management. In traditional Lightning wallets, you might open and close multiple channels as your needs change — each requiring an on-chain transaction with mining fees. Phoenix maintains a single channel to ACINQ’s node and dynamically resizes it:
- Receiving more than your inbound capacity? Your inbound capacity is the room left in your channel to receive, which is ACINQ’s side of it. Phoenix automatically performs a splice-in, expanding the channel to accommodate the incoming payment. This requires one on-chain transaction.
- Want to move funds on-chain? Phoenix performs a splice-out, directly sending bitcoin from your channel to an on-chain address. No swap service needed — the operation is trustless.
- Channel stays operational during splicing. Unlike traditional channel opens/closes, splicing does not interrupt your ability to send and receive Lightning payments.
The result for users: one balance, no channel management decisions, and a seamless experience that hides Lightning’s underlying complexity without compromising self-custody.
Trampoline Routing
Phoenix does not compute payment routes independently. When you send a payment, Phoenix delegates route-finding to ACINQ’s node using a protocol called trampoline routing. Your phone sends the payment to ACINQ’s node with instructions like “deliver this to destination X,” and ACINQ’s well-connected node figures out the best path.
This design saves bandwidth and battery on your phone, which matters for a mobile wallet. The tradeoff is privacy: ACINQ’s node sees the amount of every payment you send, and the destination of ordinary invoices (BOLT 11, LNURL included) and of payments to other Phoenix users. Paying a BOLT 12 offer from someone not on Phoenix can hide who you paid, when their blinded path starts at a node other than their own. Phoenix supports Tor connections to obscure your IP address, but Tor does not hide the destination from ACINQ.
Fee Structure
Phoenix’s fee model changed significantly with the splicing update of July 2023. Here is the structure as published in Phoenix’s FAQ, as of November 2026:
- Sending Lightning payments: 0.4% of the payment amount plus 4 sats, routing included. This fee is fixed and shown before you confirm.
- Receiving Lightning payments: free when the payment fits in your channel. When it doesn’t, Phoenix expands the channel (a splice-in) and charges 1% of the amount plus the mining fee for the splice transaction. Your very first channel also costs 1,000 sats to create.
- Splice-out (on-chain withdrawal): Mining fee for the on-chain transaction only. No additional service fee.
- No monthly fees and no subscription.
For context: sending a 50,000-sat Lightning payment (about $38 in November 2026) costs 204 sats (about $0.15), routing included. A simple on-chain payment costs the same whatever the amount: about 141 sats at the 1 sat/vB typical in November 2026, and thousands of sats during fee spikes like those of 2023 and 2024. So Phoenix is cheaper for small everyday payments, and for any everyday amount when fees spike; on a calm day, for amounts above about 34,000 sats, a simple on-chain payment costs less.
The 1% liquidity fee for channel expansion is higher than managing your own node channels, but dramatically simpler. Most users never want to manually manage inbound and outbound liquidity — Phoenix handles it automatically at a reasonable cost.
User Experience
Setup
Initial setup takes under two minutes: install the app, write down your 12-word seed phrase, and you are ready to receive your first payment. There is no account creation, no email verification, no KYC. Phoenix creates your wallet on the spot.
Sending Payments
Tap “Send,” scan a Lightning invoice (BOLT 11), paste an LNURL, or scan a BOLT 12 offer. Phoenix displays the amount and total fee before you confirm. A payment usually arrives within a few seconds.
Receiving Payments
Tap “Receive,” specify an amount (or leave open for any amount), and Phoenix generates a QR code. If the incoming payment exceeds your current inbound capacity, Phoenix handles the splice-in automatically, as long as the fee stays within the limit in Settings → Channel management. By default Phoenix refuses an incoming payment whose fee would be more than 5,000 sats or 50% of the amount, and the payment goes back to the sender.
On-chain Integration
Phoenix provides a swap-in Bitcoin address for receiving on-chain payments. Funds sent to this address are automatically spliced into your Lightning channel, appearing in your unified balance once the on-chain transaction has 3 confirmations, as long as the mining fee for the splice is below the maximum you set in Settings → Channel management (until then the funds show as “sleeping”; they are still yours). This eliminates the mental overhead of managing separate on-chain and Lightning balances.
Backup and Recovery
Phoenix uses a 12-word seed phrase for key derivation, plus an encrypted copy of your channel data that ACINQ’s node keeps for you. If you lose your phone:
- Install Phoenix on a new device.
- Enter your 12-word seed phrase.
- Phoenix retrieves your encrypted channel state and restores your balance.
This is a significant usability advantage over wallets that require manual Static Channel Backup (SCB) management. The tradeoff: ACINQ stores your encrypted channel state. They cannot access it without your seed phrase, but the data exists on their infrastructure.
Pros and Cons
Pros
- Best user experience of any self-custodial Lightning wallet — genuinely rivals custodial simplicity
- Splicing eliminates channel management complexity entirely
- Unified balance (no separate on-chain and Lightning funds to manage)
- Transparent, predictable fee structure
- Active development by one of Lightning’s core implementation teams
- Open source (Apache 2.0)
- BOLT 12 support enables reusable payment offers
- Tor support for IP privacy
Cons
- Depends entirely on ACINQ’s Lightning Service Provider (LSP) — if ACINQ goes offline, you can still recover funds on-chain but cannot make Lightning payments until they return
- Trampoline routing means ACINQ sees your payment destinations
- 0.4% sending fee is higher than routing through your own node (where you pay only network routing fees)
- No desktop app: Phoenix is a phone app (phoenixd, ACINQ’s server version, is for developers)
- Single-LSP dependency means no redundancy for routing
Phoenix vs Other Lightning Wallets
| Feature | Phoenix | Zeus | Breez | Wallet of Satoshi |
|---|---|---|---|---|
| Custody | Self-custodial | Self-custodial | Self-custodial | Custodial in some regions, self-custodial (Spark) elsewhere, per the company (not verified by us, Nov 2026) |
| Channel management | Automated (splicing) | Manual or LSP | LSP-assisted | None (managed) |
| Technical knowledge needed | None | Moderate to high | Low | None |
| Sending fee | 0.4% + 4 sats | Network only | Network + LSP | None visible (built in) |
| Privacy | Moderate (trampoline) | High (own node) | Moderate (LSP) | Not verified (see note below) |
| Best for | Everyday users | Power users | Merchants | Beginners (custody model not verified) |
Two notes on this table, as of November 2026. The original Breez app has left the app stores, so its column shows the app as we compared it in February 2026. In February we listed Wallet of Satoshi as custodial. The company now describes two modes (its disclosure, last updated 25 August 2026): a custodial account, which new users get first in the regions where it is offered, and a self-custodial Spark wallet, available everywhere, with a 12-word recovery phrase. Only the self-custodial mode has those words, and they restore in Spark-compatible wallets, not in a standard BIP39 wallet, so check which mode your app is in; we have not verified its architecture.
For a detailed comparison of all these wallets and more, see our comprehensive Lightning wallet comparison.
Verdict: Is Phoenix the Best Lightning Wallet in 2026?
For the majority of users who want self-custody without managing infrastructure, yes. Phoenix is the wallet that proves self-custodial Lightning can be as simple as custodial alternatives — without sacrificing control of your keys. The splicing architecture is genuinely innovative, the fee structure is transparent, and the ACINQ team has a decade-long track record of serious Lightning development.
Phoenix is not the best choice if you prioritize maximum privacy (ACINQ sees your payment destinations), maximum fee savings (running your own node is cheaper), or desktop use (Phoenix is a phone app). For those use cases, Zeus or Alby Hub may be better fits.
But for the person who wants to hold their own keys, make Lightning payments daily, and never think about channels — Phoenix is the answer.
Frequently Asked Questions
Is Phoenix Wallet safe?
Phoenix is self-custodial — you control your private keys via a 12-word seed phrase. ACINQ cannot access or freeze your funds. ACINQ itself calls Phoenix “trust-minimized, but not trustless”: when an incoming Lightning payment creates or enlarges your channel, you rely on ACINQ until that on-chain transaction confirms. The main risk is losing your seed phrase, which would make fund recovery impossible. Write your seed phrase on paper or metal and store it offline.
How much does Phoenix Wallet cost?
Phoenix is free to download and use. You pay 0.4% + 4 sats per Lightning payment sent, and 1% plus the mining fee when your channel needs to expand for an incoming payment (your first channel also costs 1,000 sats to create). Receiving a payment that fits in your channel is free. As of November 2026, there are no subscriptions, monthly fees, or hidden charges.
Can I receive on-chain Bitcoin with Phoenix?
Yes. Phoenix provides a swap-in Bitcoin address. On-chain funds are automatically spliced into your Lightning channel after 3 confirmations, for the mining fee. Your balance appears as a single unified amount — no separate on-chain and Lightning balances to manage.
What happens if ACINQ shuts down?
If ACINQ’s node goes permanently offline, your Lightning channel would need to be force-closed (Settings → Danger zone in Phoenix). ACINQ says to do this only in that case: high fees apply. Your funds would return on-chain after a delay of 720 blocks, about five days. You would not lose bitcoin — you would lose Lightning payments in Phoenix, which connects only to ACINQ’s node, until you move to another Lightning wallet or run your own node. Keep Phoenix installed until the funds are back; your seed phrase also recovers them in a standard wallet such as Electrum.
Does Phoenix support BOLT 12?
Yes. Phoenix supports BOLT 12 offers, which allow reusable payment requests. Instead of generating a new invoice for every payment, you can share a single BOLT 12 offer that others can pay multiple times — useful for donations, recurring payments, or public-facing payment links.
Related Articles
- Running a Lightning Node: Complete 2026 Guide
- Lightning Channel Management: Best Practices
- Alby Wallet Review: Lightning for the Browser
