2 HN users recommended this explainer2 months2017–2018score 2
Years with an HN recommendation, 2007–2026
Commenters point to it as a short, high-level overview of how Lightning payment channels work.
An 8-minute explainer on the Lightning Network and how it relates to Segwit, Bitcoin and Litecoin. It covers how off-chain payment channels route payments to scale blockchain transactions.
“This video gives a high-level overview” (HN, 2018)
> partly because these off-chain networks would quickly form large central "hubs" which would obviate many of the benefits of Bitcoin The Lightning Network is open-source and decentralized. It has no "hubs", but rather just peers that route payments to each-other using a payment routing algorithm. Lightning has no counterparty risk, as no one can ever steal your bitcoins and you're always in full control. The best way to describe Lightning is as an write-cache layer. It improves the scalability properties of Bitcoin by many factors, makes micro- and nano- payments a reality, reduces fees to fractions of a cent, and even improves privacy (using a Tor-like onion routing for anonymized payments). [this video] [link]
Explains how Lightning scales Bitcoin via off-chain payment routing.
Each transaction spending the locked funds bears the signature of the party making the payment. The other party can then provide the counter-signature making the transaction valid on the Bitcoin network. The main security problem to solve is preventing one party from publishing a previous channel state (half-signed transaction) giving themselves more money than they actually have by rights. For example, Alice and Bob might start with a channel giving each of them 5 bitcoin. Then Alice makes two one-bitcoin payments to Bob: A | B ------ 4 | 6 3 | 7 Alice decides she wants to take back her last payment and instead publish the earlier transaction (signed by Bob) giving herself 4 bitcoin rather than the one giving herself 3. This problem is solved with hashed timelock contracts (HTLCs). Without getting too technical, HTLCs make it possible for a party who spots a counterparty attempting to publish an invalid transaction to take all of the money in the channel (i.e., Bob would take all 10 bitcoin). The main idea is that cryptographic hash functions are one-way. If I make a payment contingent on knowing a preimage to a hash value, I can cause the payment to become valid by revealing the preimage. Along with the signature to a transaction, Alice must also give Bob the preimage for the previous transaction before he will accept it. When she does, Bob knows that if Alice tries to play games, he can take all of her money. This video gives a high-level overview: [this video]
High-level overview of how Lightning payment channels work.
I would modify that slightly and say Litecoin is back because of the Lightning Network, which benefits greatly from features provided by Segwit, and which itself leverages payment channels backed by multi-sig addresses. While Lightning can be enabled without Segwit, it's far more trustworthy with it, than without it. [this video]
Video list and Hacker News comment labels from HackerTube (prompted by @karpathy), released under ODC-By 1.0, built on the open-index/hacker-news archive. Hacker News data is provided by Y Combinator; comments remain the work of their authors. Video titles, channel names and thumbnails belong to their creators and are shown via YouTube. HackerTube Watch is an unofficial edition. Data export of 2026-10-31.
3 Hacker News comments
From the HN archive; up to 20 kept per video, favoring different commenters. Recommendations first.
Read more
Read more
Citations, criticism and jokes