Reviews

Lightning Network: Fees, Speed and Decentralization

Fast bitcoin payments for small everyday spending, better for people with some experience than for newcomers. Many rely on a company's app, and 2026 thefts hit Lightning nodes, so start small and keep apps updated.

4.0/10

ChainMatch score · Networks

Research-based Method v1.1 · scored November 10, 2026

CriterionWeightScoreWhy
Decentralization 25% 6.0 No Decentralization Index can be calculated for this network, because Lightning has no block producers or shared ledger of its own. In its favor, thousands of public nodes (trackers count from about 5,600 to over 17,000) can run on home computers. Rule changes also need two independent programs. Against it, a 2024 figure puts 80% of its money with central providers, and one program may run over 90% of nodes. Disputes also settle on Bitcoin, where three mining pools found most blocks last month, pulling it toward a 5.
Security track record 20% 4.0 Lightning has no blocks of its own, so it can't suffer the rollbacks or '51%' attacks the method describes, but attackers have repeatedly stolen from nodes: through BTCPay Server, separate software, in August 2026 (fixed in 2.4.2, exploited again on unpatched servers on November 1), and through two Core Lightning bugs in September 2026, where operators reported losses, maintainers said version 26.06.8 fixes them and the team warned on October 2 that unpatched nodes were being targeted. Theft-capable bugs were also found and fixed in LND, Eclair and LDK, no total loss has been published, and some attacks remain cheap or only partly fixed, so this sits below the method's 5. The December 2024 fee attack is only partly fixed and still allows some theft, so the limit for an unfixed problem applies.
Speed 15% 9.5 This uses our stand-in for payment-channel networks: the time until a payment settles and can't be reversed in practice. On Bitcoin itself, a payment is only final when its channel closes, which can be months later. A Fidelity Digital Assets report found almost all payments under 1 million sats (0.01 bitcoin) settle in under a second. That beats the 10's 5-second mark, but larger payments took about 7.6 seconds. The same report puts the success rate for almost all payments at 75% to 95%, so some payments fail or need retrying.
Cost to use 15% 7.0 This uses our stand-in for payment-channel networks: the fees routing nodes advertise, since nobody publishes the fees people actually pay. The median node on a payment's route asks under 1 sat plus 100 to 136 millionths of the amount. Converted to US dollars at mempool.space's exchange rate on November 4, 2026, an average $212 payment pays 2 to 3 cents per node. The $212 comes from River's November 2025 totals. That is under $0.10 but not under $0.01. Wallet fees and the Bitcoin fee to open a channel come on top.
Reliability 15% 9.0 No report shows the whole network stopping in the past 24 months, and one node failing doesn't stop payments. But no public tracker records Lightning outages to confirm this. In August 2026, the makers of Core Lightning, a main node program, told operators of unpatched nodes to go offline. Boltz, a swap service several wallets rely on, also shut down that month.
Wallet and app support 10% 6.0 Kraken, Coinbase, Cash App and Square support Lightning. So do many phone wallets, including Phoenix, Muun, BlueWallet and Wallet of Satoshi. But you need a Lightning-enabled wallet, and hardware wallets mostly can't use it. Trezor says it can't. Blockstream's Jade works only through swaps, which Bitcoin.com News says Blockstream switched off in August 2026. We also found no broad range of apps beyond payments.

Score limits that apply: an unfixed security problem (4.0 at most); a serious incident in the last 24 months that has been fixed (8.0 at most). How the limits work

How we score networks

Good

  • Fast. A Fidelity Digital Assets report, relayed by Bitcoin.com News on February 21, 2025, says almost all payments under 1 million sats (0.01 bitcoin) finalize in under a second. Larger ones took about 7.64 seconds.
  • Small forwarding fees. The median fee rate that channels advertise is about 100 to 136 parts per million, roughly 0.01% of the amount, for each node a payment passes through (mempool.space and 1ML, November 4, 2026). Wallet and exchange fees come on top.
  • Anyone can run a node. Lightning Labs says its LND program needs at minimum 2 GB of memory, a 1 GHz quad-core processor and 5 GB of storage. The BOLT rules say protocol changes need two independent programs that work together.
  • Funds sit in a shared account that needs both sides to sign, and either side can close the channel alone, says Bitcoin Layers. It rates the risks to custody, data availability, node operators and finality as Low.
  • Square sellers in the US can take Lightning payments, and Kraken supports Lightning deposits and withdrawals for BTC. Availability depends on where you live.

Watch out for

  • On August 7, 2026, attackers used a flaw in BTCPay Server, separate payment software, to steal funds from Lightning nodes running LND. BTCPay says users lost funds and has not said how many or how much.
  • In September 2026, operators reported losing funds through two bugs in Core Lightning, a main node program. Maintainers say version 26.06.8 fixes them, and on October 2 the team urged upgrades after reports of attackers targeting unpatched nodes. No total loss has been published.
  • Running your own node is hard. Bitcoin Layers says non-technical users often end up with custodial services, and it relays a 2024 River figure that 80% of Lightning liquidity sits in channels run by centralized providers.
  • You are responsible for your channel data. Bitcoin Layers says losing it could mean a complete loss of the funds in the channel.
  • Payments don't always go through. The Fidelity report, as relayed, puts success at 75% to 95% for almost all payments. Coinbase says success falls as payments get bigger.
  • Hardware wallets mostly can't use it. Trezor says it can't manage Lightning funds, and Blockstream's Jade route relies on in-app swaps, which Bitcoin.com News says Blockstream switched off in August 2026.
  • Some weaknesses are cheap to use or only partly fixed. Bitcoin Optech says channel jamming lets an attacker block other nodes' funds at no cost, and a December 2024 fee attack that needs a miner's help is still possible in a limited form.

Best for: The Everyday Spender. Find your profile.

Who it’s for

The Lightning Network is a payment layer built on Bitcoin (the network your bitcoin moves on), and it has no coin of its own. It suits The Everyday Spender: someone who wants to pay and get paid in small amounts, quickly. It is a weaker fit for The Newcomer, because of the setup and backup duties below, and for The Long-Term Holder, because hardware wallets (devices that keep the keys to your crypto offline) mostly can’t manage Lightning funds.

Comparing networks isn’t advice to buy their coins. If you’re not sure what fits you, use the setup finder.

Fees and speed

A channel is a shared account between two people. It lets them pay each other without using the blockchain for every payment. The BOLT specification (the technical rules Lightning software follows) calls Lightning “a protocol for making fast payments with Bitcoin using a network of channels.”

Fees. Bitcoin Layers, a site that lists and rates networks built on Bitcoin, says that once a channel is open, payments happen off the blockchain without paying miners (the computers that add blocks to Bitcoin). It calls Lightning “well-suited for small, high frequency transactions.” But you do pay Bitcoin fees to miners when you open and close a channel.

Each node a payment passes through (a computer running Lightning software, called a hop) charges a small forwarding fee. A satoshi (sat) is one hundred-millionth of a bitcoin. Public trackers show what channels advertise:

  • mempool.space’s feed shows a median fee rate of 100 parts per million of the amount sent (0.01%) and a base fee (a flat charge per payment) under one sat. Its feed returned snapshots with different dates on different reads, so treat its numbers as rough.
  • 1ML showed a median fee rate of about 135 parts per million and a base fee of about a quarter of a sat on November 4, 2026. It shows no data date.

These are advertised fees, not fees people actually paid. We found no public source for those.

For a rough picture, we started from River’s estimate of about $212 for an average payment. That is our division of its November 2025 figures, an estimated $1.1 billion across 5.2 million payments, as reported by Cointelegraph on February 19, 2026. At mempool.space’s exchange rate on November 4, 2026, the advertised forwarding fee on that payment is about 2 to 3 US cents per hop. This is our own estimate, and the dollar figure moves with the exchange rate.

Wallet and exchange fees come on top, and they can be larger:

  • Phoenix (a wallet). Its FAQ says sending over Lightning costs 0.4% plus 4 sat. Receiving is free with enough room in your channel, and costs 1% plus mining fees without it. Creating a channel costs 1,000 sat.
  • Coinbase. The Block reported on April 30, 2024 a 0.1% processing fee on sends and a $2,000 withdrawal cap at launch. Those are launch terms and may have changed. Datawallet, a third-party fee guide, listed a 0.2% fee on August 20, 2026. Coinbase’s own fee page didn’t load for our research tools, so check the fee in the app.
  • Square. For sellers, its help page lists a 0% processing fee until December 31, 2026 and 1% after. It sets a $600 maximum per transaction and $20,000 a day.
  • Kraken. Its help article lists no Lightning fees or limits.

A fixed fee takes a bigger share of a small payment, so check the fee before you confirm.

Speed. A Fidelity Digital Assets report, relayed by Bitcoin.com News on February 21, 2025, quotes an analyst: “Almost all transactions below one million sats finalize in less than one second.” One million sats is 0.01 bitcoin. Larger amounts took about 7.64 seconds.

The same article says almost all payments have a success rate “within a range of 75-95%”. It doesn’t say whether that counts retries. The analyst said a 99% or better success rate is possible with proper configurations, and named payment retries as a key factor.

Coinbase’s Lightning lead told The Block in 2024 that the average success rate falls as payments get larger. He gave that as the reason for its conservative launch cap.

The report’s own charts match the article. They use a sample of payments supplied by Voltage, a Lightning payment provider, and are dated October 22, 2024. Average success ran from about 95% for the smallest payments to about 75% for payments over 1 million sats. That is one provider’s sample, not the whole network.

Bitcoin Layers says Lightning payments settle instantly and are irreversible once settled. It also says “Finality on Bitcoin occurs only when a channel is closed.” In plain terms, the payment is done between you and the person you pay. It reaches the blockchain only when a channel closes, which can be a long time later.

Our standard speed measure is the time until a payment is final on the base network. Our standard cost measure is the median fee people actually paid over 30 days. Neither exists for Lightning. So for payment-channel networks we use stand-ins. Speed is the time until a payment settles and can’t be reversed in practice. Cost is the advertised forwarding fee, converted to US dollars at mempool.space’s exchange rate on November 4, 2026. See how we score networks.

The project’s own site says payments take “milliseconds to seconds” and carry “exceptionally low fees.” It gives no figures, so those are the project’s claims.

How decentralized it is

Decentralization means how hard it would be for a small group to halt, censor or rewrite a network. Our Decentralization Index can’t be calculated for Lightning. It has no block producers (the miners or validators that add blocks) and no shared ledger of its own. So there is no index figure for it. We rated it from the evidence below, as our method allows for payment-channel networks.

  • Anyone can run a node. Lightning Labs’ guide says its LND program (software that runs a Lightning node) needs at minimum 2 GB of memory, a 1 GHz quad-core processor and 5 GB of storage, on a good-quality SSD. That is home-computer level. LND can also run in Neutrino mode, a light mode that doesn’t need your own Bitcoin node.
  • No company writes the rules alone. The BOLT contribution rules say protocol changes “require two independent implementations which successfully inter-operate.” Apart from typo fixes, changes are approved at a regular spec meeting.
  • There are several programs. Bitcoin Optech’s reports cover flaws in four: LND, Core Lightning, Eclair and LDK.
  • One may still dominate. Spark, which sells a competing Bitcoin layer, says LND runs “an estimated 90%+” of public nodes. It names no source and gives no date beyond “early 2026”. Treat that as an unverified estimate.
  • Money is concentrated. Bitcoin Layers cites a 2024 River report: “80% of Lightning Network liquidity resides in channels managed by centralized service providers.” We couldn’t open River’s report to check it.
  • Node counts disagree. On November 4, 2026, 1ML showed about 5,560 nodes. mempool.space’s feed showed 16,230 on November 10, 2026, in a snapshot dated August 30, 2026. Wikipedia, citing mempool.space data from March 2026, gives over 17,000 public nodes. Spark gives 17,438 for May 2026. Trackers count in different ways, and some count only public nodes. Read “thousands”, not an exact figure.
  • It leans on Bitcoin’s miners. Disputes between channel partners are settled on the Bitcoin blockchain. In mempool.space’s one-month mining data, read November 4, 2026, three pools found about 63% of blocks, by our calculation. See our Bitcoin review.

In short, no one company controls the written rules, and anyone can run a node. But many people reach Lightning through a few providers, and one program may run most nodes.

How it keeps you safe

  • A shared account with a way out. Bitcoin Layers says funds sit in a 2-of-2 multisig (a shared account that needs both sides to sign), and each side can exit alone. The project’s site says a channel can be closed “without any trust or custodianship” by putting the latest version on the blockchain. Bitcoin Layers rates the risks to custody, data availability, node operators and finality as Low. That is one site’s rating.
  • Settled payments can’t be reversed. That protects the person getting paid. It also means a payment to a scammer can’t be undone. Our 60-second scam check covers the warning signs.
  • The main risk is an old version of the account. Bitcoin Layers says “Users must watch for malicious channel closures.” A channel partner could try to close with an old version. It also says users are “solely responsible for preserving their channel state data” and that losing it “could result in a complete loss of funds stored in the channel.” A wallet app may handle this for you. Read how yours does.
  • Bugs are reported in public. Bitcoin Optech, a newsletter that follows Bitcoin and Lightning software, lists theft-capable flaws found and fixed in LND, Eclair and LDK from 2024 to 2026, plus crash and memory bugs in Core Lightning. Core Lightning’s changelog lists bugs that could lose funds, and operators on its GitHub issues report thefts, described below. Optech’s 2025 review doesn’t say whether any of the theft-capable flaws it lists were exploited.
  • Advisory pages are patchy. LND’s GitHub page lists two published advisories, both rated High, dated June 20, 2024 and November 17, 2022. Core Lightning’s page says “There aren’t any published security advisories”, yet its release notes describe security fixes. Read the release notes, not only the advisories page.

Reliability record

We found no report of the whole Lightning network stopping between November 2024 and November 2026. No public tracker records Lightning outages, so that is an absence of reports, not proof. Lightning has no single server, so one failed node doesn’t stop it.

Problems in that period hit individual services and software instead: Boltz, Zeus, Core Lightning and the BTCPay thefts, all below. A wallet that relies on one company’s node can stop working if that node does. Our Phoenix review explains one case.

Where it falls short

  • What this means for our score. Our method limits a score after any serious incident in the last 24 months, even a fixed one. The method also has a stricter limit for an unfixed security problem. The December 2024 fee attack, described below, is only partly fixed and still allows some theft, so that stricter limit applies and sets Lightning’s score. Lightning’s 2026 thefts count too. The method’s security measures describe attacks on a blockchain itself, such as rollbacks, and Lightning has no chain of its own. So we rated its security from thefts from Lightning nodes and bugs in the software they run. Repeated, recent thefts pulled that rating down.
  • Many people end up with a company holding their money. Bitcoin Layers says non-technical users can find it challenging to run their own Lightning node. It says this often drives them toward custodial services. Custodial means a company holds your money, so you trust it to pay you back. The 80% figure above points the same way. A wallet app is easier, but then you rely on the company behind it.
  • Setup and backups take some skill. We rate Lightning intermediate difficulty, which is our judgement. That is why it is a weaker fit for The Newcomer. You are responsible for your channel data, as the safety section above explains.
  • Payments don’t always go through. See the success rates above.
  • Hardware wallets mostly can’t use it. Trezor says Lightning needs a node online around the clock with “hot” keys (keys kept online), so its hardware wallets can’t manage Lightning funds. That is why it is a weaker fit for The Long-Term Holder. Details are in the wallets section below.
  • Opening and closing a channel costs a Bitcoin fee. Wallet fees come on top.
  • Some attacks are cheap or only partly fixed.
    • Channel jamming. Bitcoin Optech’s 2025 review calls it a weakness that “allows an attacker to costlessly prevent other nodes from using their funds.” A reputation-based fix was simulated in October 2025, and its authors felt it was ready to implement. We found no source saying it is in wide use.
    • Fee attack, December 2024. Bitcoin Optech reported a flaw found by David Harding. A channel opener, with a miner’s help, could take up to 98% of a channel’s value. They would use an old state that commits most of the balance to fees. Old Eclair, LDK and LND defaults were affected. Capping fees fixed the worst case, but some bounded theft is still possible. Optech says a complete solution needs more work. Optech didn’t say whether it was exploited.
    • Replacement cycling. This is a way to steal by pushing a victim’s waiting transactions out of the queue for the blockchain. Optech says it “would be difficult to sustain without being detected.” Optech doesn’t say whether it was exploited.
  • Past incidents.
    • August 7, 2026, BTCPay Server thefts. BTCPay’s advisory says a critical flaw in versions before 2.4.2 let an unauthenticated remote attacker (someone with no login) obtain credential files for LND. These files are called macaroons. They can control an LND node and move its funds. BTCPay says “We have confirmed that attackers exploited this vulnerability” and that users lost funds. CoinDesk reported on August 8 that Foundation, a hardware-wallet maker, said its Lightning node was drained. It also reported that the publication Citadel21 said its node was swept. BTCPay calls it a vulnerability in BTCPay Server. It says only nodes running LND were affected, and users of other Lightning programs were not exposed to this credential risk. It has not said how many servers were hit or how much was stolen. It announced a recovery bounty and said security work will come before new features.
    • BTCPay Server, since the fix. The fix was BTCPay Server 2.4.2, and BTCPay has since shipped security releases 2.4.4 (September 8) and 2.4.5 (October 5). On November 2, 2026, BTCPay reported that attackers used a different method to exploit the flaw fixed in 2.4.2. It says they stole Bitcoin and Litecoin from hot wallets (wallets whose keys sit on the server) on November 1, on servers running 2.4.1 or earlier. It says it has seen no impact on servers that were already on 2.4.2 or later when it warned users on November 1. It has not established when exploitation began, and the post doesn’t say whether Lightning funds were taken.
    • August 2026, other services. Boltz is a swap service several wallets rely on. It swaps bitcoin between Lightning and Liquid, a separate network with its own stand-in for bitcoin. Boltz suspended its swaps on August 3, saying “Attackers now iterate faster than a team our size can find and patch.” Bitcoin.com News reported no user fund losses, and that Boltz doesn’t hold user funds. Aqua, Bull Bitcoin, Zeus and Blockstream had features disrupted. The Zeus wallet took its infrastructure offline after a cybersecurity incident. Cointelegraph reported on August 6 that Zeus said no customer funds were lost. Zeus also said it had no evidence Lightning node software was affected. The nature of the attack wasn’t disclosed.
    • August to November 2026, Core Lightning. ForkLog reported that on August 23 the team told operators not ready to update to run their nodes offline while it prepared fixes. Security releases followed on August 28, September 22, October 7 and November 4, according to its GitHub releases page. The changelog dates the same releases one to three days differently (August 26, September 19, October 6 and November 5). The 26.06.10 release notes say “We strongly recommend upgrading to this release.” On September 4, Bitcoin Optech said none of the first set’s fixes were known to be actively exploited. The September reports below concern later bugs, fixed in 26.06.8. Optech also said Docker (a common way to install server software) users who pulled certain images between August 28 and September 1 may have received images without the fixes. Those users should pull again.
    • September 2026, Core Lightning thefts. Core Lightning is one of the main programs for running a node. Operators reported losing funds through two bugs. In issue 9498, opened September 12, operators on version 26.06.7 said a peer opened a channel and drained their liquidity. One said they were “robbed of almost 2Msats” (about 2 million sats), and the others gave no figure. A maintainer said the attack used a bug in how a replacement funding transaction was handled after the original had confirmed. It affects dual funding (a way for both sides to put money into a new channel), an experimental feature that is off by default. In issue 9578, opened September 28, an operator on 26.06.7 said channel funds were already gone after a splice (a way to resize a channel) and a forced close. They gave no amount. Another operator reported five similar incidents on 26.06.7, in which outputs totaling 4,878,032 sats were spent through the revocation path (the route that lets a channel partner take funds when an outdated state is published). A contributor said a sixth attempt, on 26.06.8, failed. Splicing, unlike dual funding, has been on by default since version 26.04. Maintainers say version 26.06.8 fixes both. The 26.06.8 changelog says a close after a splice “could broadcast a revoked commitment, losing the channel funds to a penalty.” In plain terms, the operator’s own node could publish an outdated channel state, and the peer could then take the funds. A maintainer also said the fix does not repair a channel that was already pointed at a funding transaction that doesn’t exist. On October 2, Cointelegraph reported that the team urged operators on 26.06.7 or earlier to upgrade after reports of attackers targeting unpatched nodes. The team didn’t say which flaws were targeted, and its post said nothing about losses. No total loss has been published. These are operator reports that maintainers acknowledged, and Core Lightning’s advisories page still lists nothing.
    • October 2026, a payment-request bug at LNP2PBot. Bitcoin Optech’s October 23 newsletter says a gap in the rules for invoices (the payment request a Lightning wallet creates) “was exploited against LNP2PBot.” An invoice carries a payment hash and a payment secret (two codes that identify a payment). The app’s parser and node picked different payment hashes, “allowing attackers to obtain duplicate payouts.” The rules now require invoice readers to reject invoices without exactly one payment hash and one payment secret. The newsletter doesn’t date the attack.
    • February 2025, an LND flaw. Protos reported a flaw in LND versions before 0.18.5 that let attackers drain nodes. It cited “a few real-world instances of actual theft of funds” but said “theft details were sparse.” It gave no amount. It relied on a developer alert and posts on X, so the evidence is thin.
    • October 30, 2026, a Linux flaw that affects LND. LND’s v0.21.6-beta release notes carry a security notice about a flaw in the Linux kernel (the core of the Linux operating system). The notice says a demonstrated remote attack needs a setting that Go (the programming language LND is built with) turns on by default from version 1.24. LND’s v0.21.6-beta release switches that setting off. The notes call this “a mitigation, not a fix” and tell Linux operators to patch their kernel. Windows and macOS are not affected. We found no report of the flaw being used against real nodes.
    • Found and fixed. Bitcoin Optech’s October 23, 2026 newsletter says Eclair 0.14.4 and 0.14.5 fix issues that could let a malicious payer or channel peer steal funds. It “strongly recommends upgrading.” Its August 21, 2026 issue says LND versions before 0.20.0 could let an attacker drain a channel after a blockchain reorganization (when the network drops recent blocks in favor of a competing chain). It quotes “To Teinturier’s knowledge, no one was affected.” Its disclosures index lists further 2026 bugs in Core Lightning, LND and Eclair. It doesn’t say whether any were exploited. For Core Lightning, see the September 2026 item above.

Which wallets and services support it

Bitcoin.org’s wallet page says “Some wallets support transactions on the Lightning Network” and calls the network “new and somewhat experimental”. It doesn’t say which of its listed wallets do. Availability of the services below depends on where you live.

Exchanges and payment apps.

  • Kraken. Its help article (updated December 11, 2025) describes Lightning deposits and withdrawals for BTC. Your account must be verified, and you need a Lightning wallet app. See our Kraken review.
  • Coinbase. The Block reported in April 2024 that Coinbase was rolling out Lightning sends, receives and payments, “not available in all regions just yet”. See our Coinbase review.
  • Square. Sellers can take Lightning payments, and the customer pays with a Lightning-enabled wallet. Square’s help page says this isn’t available to businesses in New York, and its October 8, 2025 press release says Square Bitcoin isn’t available outside the US.
  • Cash App. TechCrunch reported in January 2022 that Cash App was adding Lightning. Cash App’s own help page didn’t load for our research tools, so check its current terms in the app.

Phone wallets. A wallet is an app or device that holds the keys that control your crypto. Self-custody means you hold the keys. Custodial means a company does.

  • Phoenix. Its README describes a self-custodial wallet from ACINQ for Android and iOS, open source under Apache 2.0, with a 12-word recovery phrase only you have. See our Phoenix review.
  • Muun. Its site calls it “a self-custodial wallet for bitcoin and lightning,” a 2-of-2 multisig wallet for iOS and Android. It advertises Lightning fees “as low as 1 satoshi”, which is a best case.
  • Wallet of Satoshi. Its site says “Self Custody By Design” with a 12-word recovery phrase only you know, for iOS and Android, and it states no regions. Trezor’s page calls it custodial, so the two sources disagree. Check who holds the keys before you rely on it.
  • BlueWallet. Its README says “Lightning Network supported.” Our BlueWallet review says its Lightning wallet needs a server you run yourself and that BlueWallet calls it experimental.
  • Others. Wikipedia also names Zeus, Strike and Breez. Trezor calls Breez self-custodial. We haven’t checked whether the others are custodial. Wikipedia carries a notice that some of its sources may be unreliable, so treat its list as a lead.

Hardware wallets. A hardware wallet is a small device that keeps your keys offline. Trezor says it “cannot directly manage Lightning Network funds.” It suggests keeping most of your bitcoin on the Trezor and moving a small amount to a Lightning wallet by an ordinary on-chain transfer (a normal payment recorded on the Bitcoin blockchain).

Blockstream says Jade owners can send and receive Lightning payments in its app (version 5.2.0 or later) through swaps with Boltz into Liquid bitcoin (a stand-in for bitcoin on a separate network called Liquid). Funds land as Liquid bitcoin, not ordinary bitcoin, until swapped. Blockstream calls this a first, which is its own claim.

Bitcoin.com News reported on August 4, 2026 that Blockstream turned off in-app swaps because of its reliance on Boltz, which had suspended its swaps on August 3. Blockstream’s August 24, 2026 post about its desktop app says new swaps, including Liquid bitcoin via Lightning, are “temporarily disabled” because of “a service interruption”, and that existing funds are unaffected. That post doesn’t mention Jade.

On August 10, 2026, Blockstream announced its own swap service, as a beta for selected users. Its November 5, 2026 quarterly update says the service is still in beta. Neither post says Boltz has resumed, or that swaps in the app are back for everyone. We didn’t check other hardware wallet makers.

Setting it up safely

  • Get your wallet from the maker’s official site. Type the address yourself or use a bookmark. The FBI warned in December 2022 that criminals buy search ads that look like real results and lead to fake sites, including for crypto exchanges. Read the FBI notice. Check the seller’s name on the app store page too.
  • Find out who holds the keys. Read the wallet’s own pages. If a company holds them, you rely on that company to pay you.
  • Create your own recovery phrase. It is the 12 or 24 words that unlock your wallet, also called a seed phrase. Write it on paper or metal. Never type it into a website or share it. No real support agent will ask for it.
  • Ask how channels are backed up. Bitcoin Layers says you alone are responsible for your channel data. Before you add money, find out what happens if you lose your phone. The recovery phrase may not be the whole answer.
  • Start with a small amount. Send and receive a small test payment first. Read the fee before you confirm it.
  • Use it as a spending wallet. Lightning wallets keep keys online. Trezor suggests keeping most of your bitcoin on a hardware wallet and moving a small amount over by an ordinary on-chain transfer. Send a small test transfer first.
  • If you run your own node or BTCPay Server, update promptly to the latest release. BTCPay says this applies to anyone still on version 2.4.1 or earlier when it warned users on November 1, 2026. They should move to a fresh server, create a new wallet with a new recovery phrase and replace their passwords and keys. That holds even if they have updated since or noticed no theft. Updating alone can’t remove an attacker’s access. BTCPay gives the same steps for a server on any version that lost funds or shows signs of unauthorized access. Eclair and Core Lightning urge upgrades in their release notes. If you run Core Lightning, use 26.06.8 or later, and the latest security release if you can. Leave experimental features such as dual funding off unless you need them. That doesn’t protect you from the splice bug, because splicing is on by default, so the upgrade is what matters.
  • If you lose money to theft or a scam, report it to the FBI at ic3.gov and the FTC at reportfraud.ftc.gov. Outside the US, use your national fraud service. Ignore anyone who offers to recover your funds for a fee.
  • Not sure what fits you? Use the setup finder.

Alternatives

Bitcoin itself is the network Lightning runs on. Payments recorded directly on it take about an hour to count as final, according to our Bitcoin review. That review also lists the hardware wallets that support it. Pick it when a payment is large, when speed doesn’t matter, or when you use a hardware wallet.

Solana is a separate network with its own coin. It records payments on its own chain, so there are no channels to manage. Our Solana review covers its fees and its record of outages. We rate it intermediate difficulty too.

You can compare networks side by side on Measure.

This is a research-based review. It draws on the project’s site, the BOLT specification, Bitcoin Optech, vendor documentation, public data feeds and news coverage, not on trying the network ourselves. See how we score networks.

Use official wallets and websites only. Scammers set up fake wallets and fake "network support" accounts.

Sources

  1. Lightning Network: Official site (undated, read November 4, 2026)
  2. BOLT specification: Introduction
  3. BOLT specification: Contributing
  4. Bitcoin Layers: Lightning (read November 4, 2026)
  5. Bitcoin.org: Choose your wallet
  6. Bitcoin.com News: Lightning capacity and Fidelity report (February 21, 2025)
  7. Fidelity Digital Assets: The Lightning Network, Expanding Bitcoin Use Cases (February 19, 2025)
  8. Cointelegraph: Lightning monthly volume, citing River (February 19, 2026)
  9. The Block: Coinbase adds Lightning (April 30, 2024)
  10. Datawallet: Coinbase fees (updated August 20, 2026)
  11. mempool.space: Lightning statistics feed (read November 4 and November 10, 2026)
  12. 1ML: Lightning statistics (read November 4, 2026, no data date shown)
  13. mempool.space: Exchange rates (read November 4, 2026)
  14. mempool.space: Exchange rate history for November 4, 2026 (read November 10, 2026)
  15. mempool.space: Mining pools, one month (read November 4, 2026)
  16. Lightning Labs: Run LND
  17. Phoenix: FAQ (undated, read November 4, 2026)
  18. GitHub: Phoenix README (ACINQ)
  19. Muun: Website (read November 4, 2026)
  20. Wallet of Satoshi: Website (read November 4, 2026)
  21. GitHub: BlueWallet README
  22. Wikipedia: Lightning Network
  23. Kraken Support: Send bitcoin on the Lightning Network (updated December 11, 2025)
  24. Square Support: Accept and manage bitcoin payments
  25. Square: Square Bitcoin press release (October 8, 2025)
  26. TechCrunch: Cash App adopts Lightning (January 18, 2022)
  27. Trezor Learn: Lightning Network
  28. Blockstream: Jade Lightning payments (March 12, 2026)
  29. Blockstream: Desktop app 3.5.0 (August 24, 2026)
  30. Blockstream: Announcing Blockstream Swaps (August 10, 2026)
  31. Blockstream: Quarterly update, Q3 2026 (November 5, 2026)
  32. BTCPay Server: Security advisory for 2.4.2 (August 7, 2026)
  33. BTCPay Server: Incident response and next steps (August 10, 2026, updated November 2, 2026)
  34. BTCPay Server: Security incident affecting 2.4.1 and earlier (November 2, 2026)
  35. BTCPay Server: 2.4.4 security update (September 8, 2026)
  36. BTCPay Server: 2.4.5 security update (October 5, 2026)
  37. CoinDesk: Attacks drain merchant Lightning nodes (August 8, 2026)
  38. Bitcoin.com News: Boltz shuts down (August 4, 2026)
  39. Cointelegraph: Zeus offline after cyberattack (August 6, 2026)
  40. ForkLog: Core Lightning advises node operators to go offline (August 27, 2026)
  41. GitHub: Core Lightning releases
  42. GitHub: Core Lightning issue 9498 (opened September 12, 2026)
  43. GitHub: Core Lightning issue 9578 (opened September 28, 2026)
  44. GitHub: Core Lightning changelog (file at tag v26.06.10)
  45. Cointelegraph: Core Lightning urges upgrade (October 2, 2026)
  46. GitHub: Core Lightning security advisories
  47. GitHub: Eclair releases (v0.14.4 to v0.14.6, October 2026)
  48. GitHub: LND security advisories
  49. GitHub: LND v0.21.6-beta release notes (October 30, 2026)
  50. Protos: Bitcoin Lightning bug allows remote theft via LND nodes (February 19, 2025)
  51. Bitcoin Optech: Newsletter 2025 year in review (December 19, 2025)
  52. Bitcoin Optech: Newsletter (December 13, 2024)
  53. Bitcoin Optech: Newsletter (September 4, 2026)
  54. Bitcoin Optech: Newsletter (August 21, 2026)
  55. Bitcoin Optech: Newsletter 428 (October 23, 2026)
  56. Bitcoin Optech: Responsible disclosures index
  57. Spark: Lightning Network state of 2026 (June 3, 2026), a competitor
  58. Spark: Lightning node comparison, a competitor
  59. FBI IC3: Criminals impersonating brands using search engine ads (December 21, 2022)