Beginner Lightning Network Certification

Examine Bitcoin’s scalability limits from one megabyte blocks and ten-minute times, compare forks like Litecoin and Bitcoin Cash, and explore solutions including segregated witness and the lightning network.

Examine the block size debate from Satoshi's megabyte limit to the Bitcoin Cash fork, highlighting spam prevention, decentralization, and throughput—from seven to over a hundred transactions per second.

Explains SegWit by contrasting hard forks and soft forks in Bitcoin, including block size limit, consensus rules, 51% miners, backward compatibility, and blockchain continuity.

SegWit moves the unlocking script into a new witness field, freeing block space for more transactions. The 1 MB limit remains, but witness data increases throughput and introduces block weight.

Examine how SegWit introduces block weight to cap witness data within four million weight units, balancing a four megabyte theoretical block with practical limits to prevent spam and centralization.

Demonstrate how SegWit relates to transaction malleability by presenting an unconfirmed Bitcoin transaction whose ID changes yet remains valid, invalidating dependent transactions and illustrating attack consequences.

Explore how transaction malleability affects transaction IDs by altering scriptsig and signatures, and how SegWit removes scriptsig from the txid calculation to prevent it.

Examine how SegWit excludes the marker, flag, and witness from transaction IDs, mitigating malleability and enabling the Lightning Network's unconfirmed, unique, and secure peer transactions since 2017.

Learn how payment channels power the lightning network as a layer two Bitcoin solution, using a multi-signature vault to open, fund, and close channels with low fees.

Explore how the Lightning Network liquidity powers payments by balancing inbound and outbound funds across channels, including funding, channel capacity, and rebalance strategies among routing nodes, merchants, and wallets.

Explore the wallet user role in the Lightning Network, detailing automated channel creation, end-of-path channels, and strategies to secure inbound liquidity via custodial or non-custodial setups.

Merchants open and fund lightning channels with inbound liquidity from providers, using BTC Pay servers, then connect to reputable routing nodes for reliable payments.

Understand how routing nodes open and fund channels to provide liquidity and connectivity, balancing capital, centrality, and fees in the Lightning Network.

Learn the standard funding protocol for lightning network channels: a single participant funds a 2-of-2 multisignature output and creates commitment transactions as insurance.

Learn how payment channels open with a funding transaction in a two-of-two multisignature address, update balances with commitment transactions, and close to settle and redeem funds.

Update the lightning channel balance via a commitment transaction that spends the funding transaction, with both parties signing to reallocate funds between Alice and Bob.

Explore how balance update transactions use timelocks and one-time keys to prevent cheating, detailing the first and second commitment transactions, mutual ten-day response periods, and key exchanges.

Close a lightning network payment channel through mutual closing, unilateral closing with a time lock, or revocation closing to deter cheating, including revocable sequence maturity contracts and breach remedy transactions.

Explore how the lightning network routes payments across multiple hops using htlcs and commitment transactions. See how hashes, preimages, and time locks secure routing with balances updated without on-chain transactions.

Explore htlc spending conditions as commitment transactions updating channel balances for multi-hop payments, detailing the retention, refund, and revocation parts and the redemption deadline.

Explore how the HTLC redemption condition uses a hash function and a secret preimage to route a payment through intermediaries in the Lightning Network, ensuring only the recipient can claim.

Learn how htlc refund works: time-locked checks ensure funds return if the secret isn't presented within two days, protecting Alice when a partner goes offline.

Explain how htlc revocation keys secure off chain lightning channels by preventing old states from being redeemed, and describe the three spending conditions using revocation, preimage, and time-based clauses.

Explore bitcoin script fundamentals, including scriptpubkey and scriptsig, and how inputs unlock outputs in bitcoin transactions. Learn pay-to-pubkey-hash, opcodes, and the stack-based execution that validates scripts.

Demonstrate how opcodes manipulate the stack in a pay to public key hash script, using dup, hash160, equalverify, and checksig to verify signatures.

Explore bitcoin script locking mechanisms beyond simple key checks, enabling multisignature wallets, the Lightning Network, ordinals, and standard scripts like pay to public key hash.

Examine standard scripts used in bitcoin transactions, including pay to pubkey, pubkey hash, and multi-signature. Understand script hash and null data scripts for efficient, private, and a lightweight blockchain presence.

Explore absolute and relative time locks, check lock time verify, check sequence verify, and the revocation key to prevent cheating in the Hptlc commitment transactions.

Analyze how Alice and Bob build commitment transactions, revealing a mirror-like structure where time locks and revocation keys protect each peer, local and remote nodes, and preserve incentives.

Explore the htlc spending outline—revocation, redemption with a preimage, and refund timelocks—plus how revocation keys and asymmetric commitment transactions govern the offerer/receiver roles and channel funds.

Explain how timeout transactions use revocation keys, absolute and relative time locks, and htlc mechanisms to protect peers in intra- and inter-channel payments, with htlc timeout and check-sequence-verify safeguards.

Explains how the htlc offerer script implements spending conditions in bitcoin script, including revocation, absolute timeouts, and the required signatures and preimage for secure redemption.

Explore the htlc receiver script in the lightning network, comparing it with the offer side, detailing preimage, payment hash, revocation, check lock time verify, and secure spending paths.