PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Choose Lightning for a small, frequent payment when your wallet can find a route with enough channel liquidity. Choose an on-chain transaction when you need a direct Bitcoin blockchain transfer, are moving a larger or infrequent amount, or are sending bitcoin to long-term storage. There is no universal satoshi or dollar cutoff. The right choice depends on the live fee, settlement urgency, route availability, privacy expectations, and how you will hold the keys.
This guide explains how the two rails work, what can make either payment fail or take longer, and a practical decision process you can apply in your wallet before every send.
The short decision
| Use case | Usually the better fit | Reason and checks |
|---|---|---|
| Frequent, small payments | Lightning | Payments can settle near-instantly when a route succeeds and fees are usually minimal. Confirm that your wallet supports Lightning and shows a viable route and liquidity. |
| Large or infrequent transfer | On-chain | The transfer is recorded directly on Bitcoin’s blockchain and does not depend on a Lightning path. Set a fee appropriate for current block demand. |
| Moving bitcoin into long-term savings | On-chain | On-chain transfer is the normal way to fund a cold-storage wallet. Confirm the receiving address and keep the signing keys offline. |
| Paying an invoice that specifically requests Lightning | Lightning | A Lightning invoice contains payment data for the Lightning network; an ordinary Bitcoin address cannot be paid through that invoice flow. |
| Recipient gives only a Bitcoin address | On-chain | Use an on-chain transaction unless the recipient can provide a Lightning invoice or other Lightning payment request. |
These are typical use cases, not hard rules. A small on-chain payment can be sensible when you need a permanent blockchain record, while a Lightning payment can be unsuitable for a large amount if your wallet cannot source enough route liquidity.
Recommended Free Tools
How the two payment rails settle
Lightning: an off-chain balance update
Lightning is a payment layer built on top of Bitcoin. The recipient generally presents an invoice or another Lightning payment request. Your wallet checks the amount and estimated routing fee, finds a path through connected channels, and attempts to update balances along that path. When the path works, the recipient gets the payment without an individual transaction being written to Bitcoin’s blockchain. The Bitcoin Design Guide summarizes the key condition: “A successful lightning payment depends on lightning network liquidity and finding a path to the recipient.”
#1 Best Overall
- BITCOIN EXCLUSIVE, PHONE VERIFICATION: Bitkey is designed from the ground up exclusively for bitcoin — a dedicated hardware wallet for secure bitcoin storage. Approve transactions with a tap using your phone and NFC. No device screen is required.
- SELF-CUSTODY, NO EXCHANGE OR CUSTODIAN REQUIRED: You hold two of the three keys in the Bitkey system – one on your phone and one on your Bitkey device. The third is stored on Bitkey’s server and cannot move your bitcoin on its own.
- NO SEED PHRASE: Set up and use Bitkey without creating or storing a seed phrase.
- 2-of-3 MULTISIG: Three keys are stored separately across your phone, Bitkey device, and Bitkey’s server. Any two keys are required to move your bitcoin.
- BUILT-IN RECOVERY: Encrypted backup and recovery tools can help you regain access if you lose your phone or Bitkey device. You can also designate a Recovery Contact.
Lightning channels are ultimately anchored to Bitcoin’s blockchain. Opening or closing a channel uses on-chain transactions; payments made while the channel is open update its off-chain balances. A payment can therefore feel immediate while still relying on the channel’s on-chain funding and settlement arrangements.
On-chain: a transaction confirmed in blocks
An on-chain payment spends one or more spendable transaction outputs (UTXOs), creates outputs for the recipient and any change, and broadcasts the signed transaction to the Bitcoin network. Miners include transactions in blocks. Your wallet normally displays a first confirmation once a block contains the transaction, followed by additional confirmations as more blocks are built.
Block timing is variable. Bitcoin’s commonly cited average interval is about ten minutes, but no individual confirmation is guaranteed to arrive on that schedule. A fee below what the network currently prioritizes can leave the transaction waiting longer. The Bitcoin.org guide for individuals and its FAQ explain that confirmation depends on fee conditions and network demand.
Compare the decision factors before you send
1. Amount and frequency
Lightning is designed for many small payments, such as repeated purchases or a service that bills you often. On-chain transfers are more commonly used for larger or less frequent movements and for funding savings. Do not turn those patterns into a fixed break-even amount: the sources do not establish a universal value where one rail always becomes cheaper.
Rank #2
- Unparalleled Security: Protect your assets NDA-free EAL 6+ Secure Element, offering robust defense and complete transparency
- Simple & Secure Interface: Manage your digital assets easily with a clear OLED screen for secure on-device confirmations
- Supports 1000s of Coins & Tokens: Securely handle thousands of assets, including Bitcoin, Ethereum, and more, all in one wallet
- Effortless Asset Management: Monitor and transact seamlessly with Trezor Suite, our intuitive desktop and mobile app
- Enhanced Backup Solution: Rest assured with Multi-share Backup, eliminating single points of failure for secure cold wallet recovery
2. Urgency and certainty of settlement
A successfully routed Lightning payment normally completes quickly. That speed is conditional: the wallet must find a path and every relevant channel must have sufficient capacity. On-chain settlement waits for block inclusion, and a low fee can extend the wait. If a recipient needs a payment immediately, Lightning is attractive only after your wallet shows that the route is available.
3. Fees at the moment of payment
On-chain fees are driven by the transaction’s signed data size and competition for block space, not directly by the number of bitcoin being sent. A larger amount can fit in a relatively small transaction, while a smaller amount can require more inputs and therefore more bytes. Lightning fees are generally low, but your wallet’s route estimate can change with the path it selects, and a payment may fail if liquidity is insufficient. Check the fee shown on the confirmation screen rather than relying on a remembered average.
4. Route and liquidity requirements
A Lightning payment needs a compatible wallet, a valid invoice or payment request, a path to the recipient, and enough channel liquidity in the direction of payment. The available balance on your side of a channel may be enough for spending but not for receiving, or vice versa. The recipient’s node or service also needs to be reachable. On-chain payments require spendable UTXOs and a valid Bitcoin address; they do not require a Lightning route.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →5. Privacy expectations
On-chain transaction data is public and permanent. Addresses are pseudonymous rather than automatically tied to a legal name, but address reuse and other usage patterns can make activity easier to connect. Lightning payments are not each published as ordinary on-chain transactions, which reduces the public blockchain record of individual payments, but that fact alone does not make Lightning anonymous. What a particular wallet provider, routing node, or service can observe depends on its implementation and operating role.
Rank #3
- Unparalleled Security: Protect your assets with EAL 6+ Secure Element, offering robust defense and complete transparency
- Simple & Secure Interface: Manage your digital assets easily with a clear OLED screen for secure on-device confirmations
- Supports 1000s of Coins & Tokens: Securely handle thousands of assets, including Bitcoin, Ethereum, and more, all in one wallet
- Effortless Asset Management: Monitor and transact seamlessly with Trezor Suite, our intuitive desktop and mobile app
- Enhanced Backup Solution: Multi-share Backup eliminates single points of failure for secure cold wallet recovery
6. How you will custody the bitcoin
A hot wallet keeps keys available for convenient spending and is practical for an active Lightning balance. Cold storage keeps keys offline, including through a hardware wallet, and is commonly used for long-term savings. A hardware wallet is a storage option, not a requirement for Lightning and not a guarantee that a particular model supports Lightning channels. Verify the wallet’s features before moving funds.
Lightning requirements and payment flow
What you need
- A wallet that supports Lightning payments.
- The recipient’s Lightning invoice or payment request, usually supplied as a QR code, text string, or application link.
- Enough spendable Lightning balance and a route with sufficient liquidity.
- An internet connection while the wallet contacts the network and attempts the payment.
Send a Lightning payment
- Request the invoice. Ask the recipient for a current Lightning invoice or payment request. Do not paste an ordinary Bitcoin address into a Lightning-only field.
- Scan or paste it into the wallet. Check the displayed recipient, amount, description, and any expiry or validity information your wallet shows.
- Review the route estimate. The wallet should show the amount that will leave your balance and an estimated routing fee. The estimate is path-dependent and can change before you approve.
- Confirm the payment. Approve only after checking the details. The wallet attempts to find a path through channels and update the balances.
- Wait for the result. A successful payment normally reports completion quickly. Save the wallet’s receipt or payment identifier if you need to reconcile the transaction.
- If it fails, retry deliberately. A wallet may try another path, but repeated failure can indicate insufficient liquidity, an unavailable peer, or a route that cannot carry the amount. Ask the recipient for a different invoice or use an on-chain payment if that is acceptable.
Receiving over Lightning
To get paid, generate an invoice for the exact amount and give it to the sender. Your ability to receive depends on inbound channel liquidity and the wallet’s design. If a sender cannot complete a payment, generating a new invoice does not by itself create more inbound capacity; the wallet or its connected service may need a different route or liquidity arrangement.
On-chain requirements and payment flow
What you need
- A wallet with spendable UTXOs.
- The recipient’s Bitcoin address, preferably transferred by a method that lets you verify it.
- A fee setting or fee recommendation from the wallet based on current network conditions.
- Enough balance to cover both the amount and the transaction fee.
Send an on-chain transaction
- Verify the address. Compare the complete address on your device with the recipient’s original instruction. A valid-looking address can still belong to the wrong person.
- Enter the amount. Confirm the unit (bitcoin or satoshis) and the destination. If the wallet supports it, use a fresh receiving address supplied for this payment.
- Review the transaction size and fee. The fee is related to the transaction’s data size and current block-space demand, not simply to the amount being sent. A fee chosen below prevailing demand may delay the first confirmation.
- Sign and broadcast. Approve the transaction in the wallet. It should provide a transaction ID after broadcasting.
- Monitor confirmations. A broadcast transaction can be visible to the network before it is in a block. Follow the recipient’s required confirmation policy and do not assume that a ten-minute average guarantees a particular arrival time.
- Record the transaction ID. Keep it with your payment records so you can distinguish a delayed transaction from one that was never broadcast.
Bitcoin transactions are irreversible once confirmed; as Bitcoin.org’s FAQ puts it, “once confirmed, they can only be refunded by the person receiving the funds.” Treat address verification and amount review as the last opportunity to prevent a permanent mistake.
Fees: why a universal Lightning-versus-chain cutoff does not work
| Fee question | Lightning | On-chain |
|---|---|---|
| Primary driver | The route selected, routing policy, and available liquidity. | Signed transaction size and competition for block space. |
| Relation to amount sent | The amount must fit the available route capacity; the fee is not a simple percentage of value. | Sending more bitcoin does not by itself make the transaction larger or the fee higher. |
| What can change before approval | The wallet may find a different path or revise its route estimate. | The recommended fee rate can change as the mempool and miner priorities change. |
| What happens when the fee is inadequate | The payment can fail because no usable route is found; increasing the amount or trying again may expose a liquidity limit. | The transaction can remain unconfirmed longer while it waits for sufficient fee priority. |
Because these drivers differ, there is no defensible fixed dollar or satoshi point at which Lightning always beats on-chain. Compare the live wallet quote, the expected settlement behavior, and the value you place on a direct blockchain record. For a small payment, an on-chain fee can be disproportionate to the amount; for a large payment, a Lightning route may not have enough capacity even if its quoted fee looks low.
Rank #4
- Dual-chip architecture for maximum protection: The next-gen, fully auditable TROPIC01 chip works alongside a certified EAL6+ Secure Element—completely NDA-free—to deliver radically transparent, industry-leading defense against physical attacks.
- Quantum-ready security: Get protection against future threats with the first-ever hardware wallet designed with quantum-ready architecture.
- See every detail with confidence: Our largest high-resolution color touchscreen makes it easy to navigate your assets, review transactions and manage your coins with clarity.
- Wireless freedom with encrypted Bluetooth control: Manage, buy, swap and stake securely using Trezor Suite on desktop or mobile. Qi2-compatible wireless charging keeps your Trezor powered up. No cables required—security meets convenience.
- Works seamlessly with Android, iOS and desktop: Connect wirelessly or via USB-C to your phone or computer. Manage your crypto anywhere with our companion Trezor Suite app.
Availability and failure modes
Lightning shows no route or the payment fails
- Likely cause: insufficient channel liquidity, an unavailable routing peer, or no path that can carry the payment.
- What to do: confirm the invoice details, wait briefly if the wallet indicates a transient peer problem, and retry if the wallet offers another route. Ask the recipient for a new payment request or a different way to pay. For a larger amount, split the payment only if the recipient and wallet support it; otherwise use an on-chain transfer.
The recipient cannot receive over Lightning
- Likely cause: the recipient lacks inbound liquidity or is using a wallet/service with limited channel connectivity.
- What to do: ask the recipient to provide an invoice from a wallet with available receiving capacity, or switch to an on-chain address. Do not keep retrying an unchanged invoice and assume that attempts create capacity.
An on-chain transaction is unconfirmed
- Likely cause: the fee rate is below current demand, or the network is processing many transactions.
- What to do: verify that the wallet broadcast the transaction and retain the transaction ID. Check the wallet’s status and the recipient’s confirmation requirement. Avoid sending a second payment unless you have established that the first transaction was not broadcast and understand the risk of paying twice.
The wrong address or amount was used
Once an on-chain transaction is confirmed, it cannot be reversed by the network. Contact the recipient if you know who controls the destination, but a refund depends on that person’s cooperation. Lightning payments are also not a general chargeback system; resolve an error with the recipient or service directly.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Choosing by real-world scenario
Getting paid for frequent small sales
Offer Lightning invoices when customers already use Lightning wallets and your receiving setup has adequate inbound liquidity. This avoids creating a separate on-chain transaction for every sale and gives customers a fast payment experience when routes succeed. Keep an on-chain address available for customers whose wallets do not support Lightning.
Paying a merchant at checkout
Use the rail requested by the merchant. If the checkout displays a Lightning invoice, pay it from a Lightning wallet and verify the amount before approval. If it displays a Bitcoin address, pay on-chain and tell the merchant that confirmation time depends on the fee and block conditions.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Moving a substantial balance between your own wallets
Use an on-chain transaction when you need a direct, independently verifiable transfer or when the destination is a savings wallet. Lightning can be appropriate for moving a working balance between compatible wallets, but first confirm that the route can carry the amount and that both wallets’ custody models are acceptable.
Best Value
- Effortlessly build your crypto portfolio via the all in one Ledger Wallet app: buy, sell, send, receive, swap, stake and more across popular blockchains. 15,000+ coins & tokens in a single dashboard. Keep a close eye on the market. Compare service providers. Track performance. Get timely alerts. Build your portfolio with confidence.
- Enjoy Bluetooth connectivity, iOS access, and hours of battery use with this mobile-first, secure backup signer. Freedom you can depend on.
- Genuine Check: confirm your signer is authentic during setup with the Ledger Wallet app.
- Protect your signer: keep it in mint condition at all times with a bespoke Pod or Case to avoid scratches and everyday wear and tear.
Funding long-term savings
On-chain is the typical choice for a cold wallet or other offline storage. Verify the receiving address on the cold-storage device, send a test amount only if your own security procedure calls for one, and then wait for the confirmation policy you use. Keep spending funds in a separate hot wallet so a routine payment does not require exposing long-term keys.
Privacy and custody in more detail
What the public blockchain reveals
On-chain transactions, amounts, inputs, outputs, and timestamps are recorded in a public ledger. Even without a name attached to an address, transactions can be correlated with address reuse, spending patterns, public disclosures, or information held by services. Use a fresh receiving address when your wallet and recipient support it, and assume that every on-chain payment leaves a durable public record.
What Lightning does and does not hide
Individual Lightning payments are not each published as ordinary blockchain transactions. That can reduce the amount of payment activity visible in a simple chain explorer, but it is not proof of anonymity or total confidentiality. Different wallet designs, routing nodes, and service operators may have different visibility into invoices, paths, timing, or balances. Choose a wallet whose privacy and data practices you understand rather than treating the rail itself as a privacy guarantee.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Hot and cold custody
Hot wallets keep keys available for quick spending and are convenient for everyday Lightning use. Cold storage keeps keys offline and is commonly used for savings; a hardware wallet is one implementation of that approach. Hardware-wallet compatibility with Lightning varies, and some devices are intended only for signing on-chain transactions. Confirm support, channel-management requirements, backup procedures, and recovery behavior before committing funds.
A repeatable decision checklist
- Identify the recipient format: Lightning invoice/payment request means Lightning; a Bitcoin address means on-chain.
- Classify the payment: frequent working payment favors Lightning; larger, infrequent, or savings transfer favors on-chain.
- Check urgency: Lightning can be near-instant only if a route succeeds; on-chain timing depends on block inclusion.
- Inspect the live fee: compare the wallet’s current Lightning route estimate or on-chain fee recommendation.
- Confirm capacity: ensure your Lightning balance and route can carry the amount, or that your on-chain wallet has enough spendable UTXOs plus the fee.
- Review privacy and custody: decide whether a public permanent record is acceptable and whether the funds belong in a hot or cold wallet.
- Verify before signing: recheck the invoice or address, amount, currency unit, and destination description.
- Keep evidence: save the Lightning receipt or on-chain transaction ID and monitor the result.
Sources and terminology
The Bitcoin Design Guide’s transactions chapter explains invoice handling, route attempts, and liquidity. Lightning Labs’ liquidity guide provides additional context on channel balance and the ability to send or receive. Bitcoin.org’s individuals guide and FAQ describe Lightning’s low-fee, fast-payment goal, public on-chain records, and wallet custody choices. The Bitcoin Developer Guide documents transaction size, signatures, UTXOs, and fee mechanics.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
