Phoenix channel capacity and Lightning Network growth

ACINQ’s Phoenix wallet opened a 2 million splicing channel. This capacity expansion follows a period of growth where public Lightning channels recorded a net capacity expansion of 5.09 BTC on October 22, 2026. The network has a public capacity of 3,454.60 BTC. There are 32,920 open public channels and 12,552 nodes with open channels. On October 22, the network saw 178 channels opened and 231 channels closed. The median new channel was 16.5 million satoshis. The largest channel opened that day involved 4 BTC between LOOP and Strike. Over the seven days before October 22, the network saw 1,200 channels open, averaging 171.4 openings per day. Six new nodes appeared daily. Most closed channels, 88%, were mutual closures, while 12% were force closes. The median time from funding to close was 23 days. The network sees new nodes like Shunhe-lnd-v6 and LightNode.

Metadata and the reality of transaction privacy

Lightning transactions are not inherently private. Metadata reveals information about users even if the transaction content stays encrypted. Global network eavesdroppers like internet service providers or national intelligence agencies analyze traffic to see the to, from, path length, and time. Intermediary adversary nodes also pose a risk. These nodes see the predecessor node, the successor node, payment identifiers, and the payment amounts. If an adversary controls two nodes in the path, they can determine the full path of the route and know who is originating and receiving the payment, plus the near exact amount of the payment. This vulnerability exists because users optimize for the shortest and cheapest routes. You should know that privacy is weak due to payment route captures and repeating transactional behavior. This behavior leads to predecessor attacks. Even when nodes appear unconnected, they broadcast a traffic fingerprint that makes them traceable. The network optimizes for the shortest and cheapest routes, which makes it easier for a corrupted node to identify the sender or receiver by eliminating impossible paths. Can the network maintain privacy while users prioritize the lowest fees?

Fee compression and integration delays

Merchant routing fees compressed by 23%. This compression forced Block to pause the Bitkey integration. Spiral reported adoption metrics for BOLT 12 despite this pause. Lightning fees are 1,000% lower than traditional payment systems like Visa or Mastercard. Users can transfer USDT using Taproot Assets. Lightning Labs released Taproot Assets v0.8 in June 2026 to help developers build multi-asset applications. The network uses Hashed Timelock Contracts to secure funds during hops. These contracts use the Bitcoin Script language to create conditional transactions. Alice sends an update_add_htlc message to Bob that contains the image, CLTV timeout, and amount. Bob sends an update_fulfill_htlc message that shares the preimage. This process ensures that funds transfer only when the required conditions are met. If Bob does not respond within 8 hours, the transaction reverts. The secret, which Bob must prove he has by returning the correct hash, prevents forwarding nodes from seeing the recipient. Parties send Bitcoin to a multisig wallet to act as collateral. In a typical exchange, Alice and Bob create a funding transaction with a 2-of-2 multisig spend requirement. This requires a transaction on the Bitcoin blockchain. During the flow, they exchange commitment transactions that represent the current channel state. If Alice decides to force-close the channel, Bob can punish her by taking the liquidity from the channel using her revocation key. The current implementation of source routing has privacy issues that developers attempt to solve with route blinding or Rendezvous routing. The clunky block requirements of Hashed Timelock Contracts might eventually be replaced by Point Time Locked Contracts. These use Schnorr signatures to increase practical privacy and save block space.

Transaction speed and liquidity limits

The Lightning Network handles 6.6 million monthly transactions. Payments settle in seconds. Swapzone data shows that completed Lightning exchanges had a median processing time of 3 minutes. The middle 50% of these transactions took between 2 and 5 minutes. Regular Bitcoin exchanges had a median processing time of 6 minutes, while the middle 50% of those exchanges ranged from 2 to 13 minutes. This makes Lightning a better option for small, time-sensitive payments. The network relies on outbound liquidity, which is Bitcoin available to send, and inbound liquidity, which is capacity available for receiving. Liquidity remains a fundamental limitation. If a route lacks sufficient liquidity, the transaction fails even when both sender and recipient are online. In 2023, Antoine Riard published a paper describing a replacement cycling attack that could lead to a loss of funds. Users must keep their wallet software up to date to defend against such flaws. Fewer than 25% of the 20 exchange providers in the Swapzone comparison support Lightning.