The Bitcoin Lightning Network liquidity crisis in November 2026
ACINQ fee increases and Amboss channel graph centralization threaten Lightning Network stability. Phoenix users face 1% liquidity fees and potential routing failures if providers like River Financial default or ACINQ infrastructure experiences disruption.
ACINQ fee increases and liquidity bottlenecks
The fee surge from ACINQ disrupts users who rely on Phoenix for automated channel management. Phoenix uses splicing to resize a single dynamic channel to the ACINQ node instead of opening multiple channels. This technology requires a 1% liquidity fee for inbound amounts with a 3,000 sat minimum. Users sending Lightning payments pay a 0.4% fee. A 50,000 sat payment costs 200 sats in routing fees. This remains much cheaper than on-chain fees, which range from 5,000 to 30,000 sats during busy periods. However, the 1% liquidity fee for channel expansion creates a sudden cost when a channel needs to expand to receive a payment. The wallet rejects any incoming payment if the fee exceeds 5,000 sats or half the amount. The first receive incurs a one-time 1,000 sat channel creation fee. You can adjust the maximum fee you are willing to pay for channel management when receiving payments. The 1% fee is higher than managing your own node, but it remains dramatically simpler. The fee is a fixed 0.4%, and the application displays the total before you confirm.
| Feature | Phoenix Detail |
|---|---|
| Sending Fee | 0.4% |
| Liquidity Fee | 1% (min 3,000 sats) |
| First Receive | 1,000 sat fee |
| Recovery | 12-word seed |
Centralization and the hosted node model
Concentration within the Amboss channel graph exposes the limits of current Lightning architecture. Phoenix users depend entirely on ACINQ’s Lightning Service Provider, which provides no redundancy for routing. Because Phoenix uses trampoline routing, ACINQ’s node knows the final destination of every payment sent. The design offers convenience, yet it sacrifices privacy. The Blockstream Greenlight hosted node custody model presents similar risks by centralizing control. The necessity of a single channel to the ACINQ node means that any disruption to their specific Lightning Service Provider infrastructure prevents all Lightning functionality for users until they can connect to a different node. ACINQ removed Phoenix from US app stores on May 3, 2024, but the company returned the wallet to the US market on April 8, 2025. Privacy-minded users may find the removal of the embedded Tor library in early 2025 frustrating, as they must now use Orbot to route over Tor. Phoenix remains self-custodial through a 12-word seed phrase which prevents ACINQ from accessing funds. ACINQ is an implementation team based in Paris, France. The wallet supports BOLT 11 and BOLT 12, which enables reusable payment offers. The wallet provides a swap-in Bitcoin address to receive on-chain payments.
Routing failures and node defaults
The River Financial routing node default highlights how provider instability impacts the network. If ACINQ’s node goes permanently offline, users cannot make new Lightning payments until they connect to another service provider. Your funds remain safe on-chain because the 12-word seed phrase allows for recovery. However, you must wait for the timelock to expire, which typically takes 2 to 4 weeks. Users must manually sweep funds on-chain to regain access to their bitcoin after the transaction settles. A force-closed channel requires a delay of five days. You must manage your own seed phrase to ensure you can recover funds. Balances may briefly appear as zero. This is a genuine user experience failure. You must understand your seed to avoid total loss. Does the industry move fast enough to prevent such widespread liquidity freezes?
Join the discussion