Blocklore
Esc

Type to search every published claim: statements, sources and topics.

Enter opens the claim; with no match, suggests the questionUp and down to move
976,842
Reading as Holder. What matters when you hold your own coins.15 of 33 claims
How deep to read

What it isCurious

A Lightning payment channel is shared between two peers, who move funds between their sides of the channel off-chain by exchanging signatures on an updated transaction, without broadcasting each update to the Bitcoin network.1: open 1 source
DefinitionCuriousEstablishedMedium confidence
To transact funds, peers exchange signatures to create an updated
Glossary and Terminology Guide, Channel, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 1/1History, hash and citation
A Lightning payment can travel through intermediate nodes using conditional payments locked to a hash. Each hop is paid when the final recipient releases the matching secret, called the payment preimage, which also serves the sender as proof of payment.2: open 2 sources
How it worksCuriousEstablishedMedium confidence
The final recipient releases the preimage in order to
Glossary and Terminology Guide, Payment preimage, read 2026-11-20
Preimage of this provides proof of payment.
Tagged Fields, p (payment hash), read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 2/2History, hash and citation

Paying and receivingUser

A Lightning recipient can request a payment with an invoice in the BOLT 11 format, a QR-code-ready payment request. On Bitcoin mainnet a BOLT 11 invoice starts with the prefix "lnbc".3: open 2 sources
FactUserEstablishedHigh confidence
A simple, extendable, QR-code-ready protocol for requesting payments over Lightning.
Introduction, read 2026-11-20
e.g. `lnbc` for Bitcoin mainnet
Human-Readable Part, prefix, read 2026-11-20
lightning/bolts at 191462825a contains this text in 11-payment-encoding.md, and still does on the default branch.
Run it yourselfgit clone https://github.com/lightning/bolts && git -C bolts show 191462825ae341f0a27098765c075f01ca9bc6c2:11-payment-encoding.md | grep -nF '`lnbc` for Bitcoin mainnet'
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 2/2, code 1/1History, hash and citation
A BOLT 11 Lightning invoice expires: its optional expiry field gives a time in seconds, and when the field is absent the specification sets the expiry to 3,600 seconds (1 hour).4: open 1 source
FactUserEstablishedHigh confidence
Default is 3600 (1 hour) if not specified.
Tagged Fields, x (expiry), read 2026-11-20
lightning/bolts at 191462825a contains this text in 11-payment-encoding.md, and still does on the default branch.
Run it yourselfgit clone https://github.com/lightning/bolts && git -C bolts show 191462825ae341f0a27098765c075f01ca9bc6c2:11-payment-encoding.md | grep -nF 'Default is 3600 (1 hour) if not specified.'
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 1/1, code 1/1History, hash and citation
Each Lightning node that forwards a payment can charge a routing fee, set per channel as a fixed base fee in millisatoshis plus a proportional fee in millionths of the amount forwarded, as specified in BOLT 7.5: open 1 source
How it worksUserEstablishedHigh confidence
fee_base_msat + ( amount_to_forward * fee_proportional_millionths / 1000000 )
HTLC Fees, read 2026-11-20
lightning/bolts at 191462825a contains this text in 07-routing-gossip.md, and still does on the default branch.
Run it yourselfgit clone https://github.com/lightning/bolts && git -C bolts show 191462825ae341f0a27098765c075f01ca9bc6c2:07-routing-gossip.md | grep -nF 'fee_base_msat + ( amount_to_forward * fee_proportional_millionths / 1000000 )'
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 1/1, code 1/1History, hash and citation
A Lightning payment attempt can fail because the sender cannot see how funds are split inside other people's channels. When a channel on the chosen route lacks enough funds on the forwarding side for the amount, that attempt fails.6: open 2 sources
How it worksUserEstablishedMedium confidence
However, channel liquidity is unknown to the sender.
Liquidity uncertainty, read 2026-11-20
the most likely reason is a lack of liquidity for the specific amount.
Learning from errors, temporary channel failure, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 2/2History, hash and citation
To receive over Lightning, a node needs inbound liquidity: funds on the peer's side of its channels. A channel the node opens and funds by itself typically starts with the balance on the node's own side, so the node can send through that channel before it can receive.7: open 3 sources
How it worksUserEstablishedMedium confidence
Now the balance is on the other end of the channel, which means that you can receive payments.
Getting Inbound Liquidity, read 2026-11-20
The channel has been set up, but in its initial state, all the capacity (140,000 satoshis) is on Alice's side.
Funding a channel, initial state example, read 2026-11-20
Inbound liquidity does not happen automatically, so you have to find ways to build it for your node.
Getting Inbound Liquidity, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 3/3History, hash and citation
A Lightning payment can be split into several parts sent over different routes and combined by the recipient. BOLT 9 signals this with the basic_mpp feature (bits 16/17), meaning a node can receive basic multi-part payments.8: open 2 sources
FactUserEstablishedHigh confidence
T1BOLT 9, Assigned Feature FlagsBOLT, says this directly
Node can receive basic multi-part payments
Feature table, basic_mpp, read 2026-11-20
Some current implementations use a very simple strategy of splitting the payment in two halves, four quarters, etc.
Multipart payments, splitting strategies, read 2026-11-20
lightning/bolts at 191462825a contains this text in 09-features.md, and still does on the default branch.
Run it yourselfgit clone https://github.com/lightning/bolts && git -C bolts show 191462825ae341f0a27098765c075f01ca9bc6c2:09-features.md | grep -nF 'Node can receive basic multi-part payments'
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 2/2, code 1/1History, hash and citation

Custody, backups and watching the chainHolder

In a custodial Lightning wallet, a third party controls custody of the funds and the user relies on that party. In a self-custodial (noncustodial) Lightning wallet, the keys are stored locally under the user's control.9: open 2 sources
DefinitionHolderEstablishedMedium confidence
This is a custodial wallet where someone else controls custody of the funds.
Lightning wallets, custodial wallets, read 2026-11-20
The term noncustodial wallet just implies that the keystore is local and under the user's control.
Lightning wallets, noncustodial wallets, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 2/2History, hash and citation
The book Mastering the Lightning Network describes custodial Lightning wallets as the least technically demanding option, and describes control over keys as a principal consideration when choosing a Lightning wallet.10: open 2 sources
FactHolderEstablishedMedium confidence
This is the least technically challenging option, but
Lightning wallets, custodial wallets, read 2026-11-20
Therefore, the issue of control over keys is a principal consideration when choosing a Lightning wallet.
Lightning wallets, choosing a wallet, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 2/2History, hash and citation
In LND, the wallet seed alone recovers only on-chain funds. Recovering funds held in open channels also needs a Static Channel Backup (SCB), which lets the node reconnect to its peers and use the protocol's Data Loss Protection feature so the peers close those channels.11: open 3 sources
How it worksHolderEstablishedMedium confidence
T2LND docs/recovery.mdDocumentation, says this directly
If one is only attempting to recover _on chain_ funds, then only the first item
Recovering Funds From lnd, on-chain recovery, read 2026-11-20
T2LND docs/recovery.mdDocumentation, says this directly
need to initiate the Data Loss Protection (DLP) feature in the protocol, which
Off-Chain Recovery, Static Channel Backups, read 2026-11-20
T2LND docs/recovery.mdDocumentation, says this directly
The remote peer will discover that we've lost data, and then immediately force close their channel.
Off-Chain Recovery, restoring from an SCB, read 2026-11-20
lightningnetwork/lnd at 8cdbf85c08 contains this text in docs/recovery.md.
Run it yourselfgit clone https://github.com/lightningnetwork/lnd && git -C lnd show 8cdbf85c0860caf252d1e3e4db508c87dec8c1f0:docs/recovery.md | grep -nF 'called Static Channel Backups (SCBs).'
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 3/3, code 1/1History, hash and citation
Restoring a Lightning node from a copy of its channel database is risky, because the copy may not hold the latest channel state. Broadcasting an old, revoked commitment transaction lets the channel peer claim all of that commitment's outputs with a penalty transaction.12: open 3 sources
How it worksHolderEstablishedHigh confidence
T2LND docs/recovery.mdDocumentation, says this directly
knows if they have the latest state of a channel or not.
Off-Chain Recovery, why not copy channel.db, read 2026-11-20
It can be claimed, without delay, by the other party if they know the revocation private key.
Commitment Transaction Outputs, to_local output, read 2026-11-20
Second, restoring from a channel backup is dangerous.
Backups, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 3/3History, hash and citation
A self-custodial Lightning node must have the Bitcoin blockchain watched, by itself or through a watchtower, for transactions that spend its channels, so it can respond with a penalty transaction if a peer broadcasts an old channel state. A node that is offline during such an attempt, with no watchtower, can lose funds.13: open 4 sources
How it worksHolderEstablishedHigh confidence
MUST monitor the blockchain for transactions that spend any output that is NOT
General Nomenclature, requirements, read 2026-11-20
In practice, both Alice and Bob have to monitor for cheating.
Cheating with old commitment transactions, read 2026-11-20
But if your node is down during the protocol violation, you might lose money.
Watchtowers, read 2026-11-20
To solve this problem, we can use one or more watchtowers to outsource the job of monitoring protocol violations and issuing penalty transactions.
Watchtowers, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 4/4History, hash and citation
A Lightning watchtower is a service that monitors the Bitcoin blockchain on a user's behalf and broadcasts a penalty transaction if a channel peer publishes an outdated channel state, so the user can go offline for significant amounts of time.14: open 3 sources
DefinitionHolderEstablishedHigh confidence
T2Bitcoin Optech topic, WatchtowersBitcoin Optech, says this directly
monitor the block chain for transactions that may cause one of their users to lose funds
Topic summary, read 2026-11-20
T2Bitcoin Optech topic, WatchtowersBitcoin Optech, says this directly
go offline for significant amounts of time
Topic summary, read 2026-11-20
are a mechanism for outsourcing the monitoring and penalty resolution of Lightning protocol violations.
Watchtowers, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 3/3History, hash and citation

Specification and implementationsBuilder

The Lightning protocol is specified in the BOLT documents of the lightning/bolts repository, a set of numbered files including BOLT 2 (peer protocol), BOLT 3 (transactions), BOLT 4 (onion routing), BOLT 7 (gossip), BOLT 11 (invoices) and BOLT 12 (offers), as of 20 November 2026.15: open 5 sources
TraceBuilderEstablishedHigh confidence
T1lightning/bolts README.mdBOLT, supports part of it
The specifications are currently a work-in-progress and currently being drafted.
Introduction, read 2026-11-20
Lightning is a protocol for making fast payments with Bitcoin using a network of channels.
Introduction, read 2026-11-20
[BOLT #12](12-offer-encoding.md): Negotiation Protocol for Lightning Payments
Table of Contents, read 2026-11-20
The human-readable prefix for offers is `lno`.
Encoding, read 2026-11-20
T1BOLT 4, Onion Routing ProtocolBOLT, supports part of it
The routing schema is based on the [Sphinx][sphinx] construction and is
Overview, read 2026-11-20
lightning/bolts at 191462825a contains this text in 02-peer-protocol.md.
Run it yourselfgit clone https://github.com/lightning/bolts && git -C bolts show 191462825ae341f0a27098765c075f01ca9bc6c2:02-peer-protocol.md | grep -nF 'Splicing is the term given for replacing the funding transaction with'
lightning/bolts at 191462825a contains this text in 07-routing-gossip.md.
Run it yourselfgit clone https://github.com/lightning/bolts && git -C bolts show 191462825ae341f0a27098765c075f01ca9bc6c2:07-routing-gossip.md | grep -nF 'To support channel and node discovery, three'
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 5/5, code 2/2History, hash and citation
A Lightning channel opens with an on-chain funding transaction whose channel output, in BOLT 3, pays to a 2-of-2 multisignature script built from the two peers' funding public keys, ordered lexicographically, so it can only be spent with both peers' signatures.16: open 3 sources
How it worksBuilderEstablishedHigh confidence
2 <pubkey1> <pubkey2> 2 OP_CHECKMULTISIG
Transactions, Funding Transaction Output, read 2026-11-20
is the lexicographically lesser of the two `funding_pubkey` in compressed format
Transactions, Funding Transaction Output, read 2026-11-20
This is the first step toward creating the funding transaction and both versions of the commitment transaction.
Channel Establishment v1, the open_channel Message, read 2026-11-20
lightning/bolts at 191462825a contains this text in 03-transactions.md, and still does on the default branch.
Run it yourselfgit clone https://github.com/lightning/bolts && git -C bolts show 191462825ae341f0a27098765c075f01ca9bc6c2:03-transactions.md | grep -nF '2 <pubkey1> <pubkey2> 2 OP_CHECKMULTISIG'
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 3/3, code 1/1History, hash and citation
Each Lightning channel update creates new commitment transactions and revokes the old ones: a peer revokes an old commitment by revealing its revocation secret, after which the other peer can claim that commitment's delayed output immediately if it is ever broadcast.17: open 2 sources
How it worksBuilderEstablishedMedium confidence
revealing this key is how old commitment
Glossary and Terminology Guide, Commitment revocation private key, read 2026-11-20
It can be claimed, without delay, by the other party if they know the revocation private key.
Commitment Transaction Outputs, to_local output, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 2/2History, hash and citation
In BOLT 3, the outputs of a Lightning commitment transaction that return funds to the peer who broadcast it are delayed by to_self_delay blocks, a value the other peer sets in BOLT 2, giving that other peer time to spot a revoked commitment and claim the funds.18: open 2 sources
How it worksBuilderEstablishedHigh confidence
must be delayed for `to_self_delay` blocks
Commitment Transaction Outputs, to_local output, read 2026-11-20
`to_self_delay` is the number of blocks that the other node's to-self
The open_channel Message, field descriptions, read 2026-11-20
lightning/bolts at 191462825a contains this text in 02-peer-protocol.md.
Run it yourselfgit clone https://github.com/lightning/bolts && git -C bolts show 191462825ae341f0a27098765c075f01ca9bc6c2:02-peer-protocol.md | grep -nF '`to_self_delay` is the number of blocks that the other node'"'"'s to-self'
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 2/2, code 1/1History, hash and citation
A Hashed Time Locked Contract (HTLC) is a conditional Lightning payment between two peers, carried as an output of the commitment transaction: the recipient claims it with a signature and the payment preimage, or else the payer reclaims it after a set time.19: open 3 sources
DefinitionBuilderEstablishedMedium confidence
the payment by presenting its signature and a
Glossary and Terminology Guide, HTLC, read 2026-11-20
otherwise the payer can cancel the contract by spending it after
Glossary and Terminology Guide, HTLC, read 2026-11-20
OP_DUP OP_HASH160 <RIPEMD160(SHA256(revocationpubkey))> OP_EQUAL
Offered HTLC Outputs, witness script, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 3/3History, hash and citation
Lightning payments are routed with onion encryption based on the Sphinx construction, specified in BOLT 4. The onion packet's hop payloads are a fixed 1,300 bytes, and an intermediate node cannot learn which other nodes, besides its predecessor and successor, are on the route.20: open 3 sources
How it worksBuilderEstablishedHigh confidence
T1BOLT 4, Onion Routing ProtocolBOLT, says this directly
The routing schema is based on the [Sphinx][sphinx] construction and is
Overview, read 2026-11-20
T1BOLT 4, Onion Routing ProtocolBOLT, says this directly
They cannot learn which other nodes, besides their predecessor or successor, are part of the packet's route
Overview, privacy properties, read 2026-11-20
T1BOLT 4, Onion Routing ProtocolBOLT, says this directly
It is 1300 bytes long and has the following structure:
Packet Structure, hop_payloads, read 2026-11-20
lightning/bolts at 191462825a contains this text in 04-onion-routing.md, and still does on the default branch.
Run it yourselfgit clone https://github.com/lightning/bolts && git -C bolts show 191462825ae341f0a27098765c075f01ca9bc6c2:04-onion-routing.md | grep -nF 'It is 1300 bytes long and has the following structure:'
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 3/3, code 1/1History, hash and citation
Lightning nodes learn about public channels and other nodes through gossip messages specified in BOLT 7, which defines three gossip messages for channel and node discovery, including a channel announcement that proves a channel exists between two nodes.21: open 2 sources
How it worksBuilderEstablishedHigh confidence
T1BOLT 7, P2P Node and Channel DiscoveryBOLT, says this directly
To support channel and node discovery, three
Overview, read 2026-11-20
T1BOLT 7, P2P Node and Channel DiscoveryBOLT, says this directly
Proving the existence of a channel between `node_1` and `node_2` requires:
Definition of short_channel_id and channel_announcement rationale, read 2026-11-20
lightning/bolts at 191462825a contains this text in 07-routing-gossip.md, and still does on the default branch.
Run it yourselfgit clone https://github.com/lightning/bolts && git -C bolts show 191462825ae341f0a27098765c075f01ca9bc6c2:07-routing-gossip.md | grep -nF 'Proving the existence of a channel between `node_1` and `node_2` requires:'
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 2/2, code 1/1History, hash and citation
In BOLT 3's anchor commitment format (feature option_anchors, bits 22/23 in BOLT 9), each anchor output on a Lightning commitment transaction is fixed at 330 sats, which BOLT 3 gives as the default dust limit for P2WSH outputs.22: open 2 sources
FactBuilderEstablishedHigh confidence
The amount of the output is fixed at 330 sats, the default dust limit for P2WSH.
Commitment Transaction Outputs, to_local_anchor and to_remote_anchor, read 2026-11-20
T1BOLT 9, Assigned Feature FlagsBOLT, supports part of it
Anchor commitment type with zero fee HTLC transactions
Feature table, option_anchors (bits 22/23), read 2026-11-20
lightning/bolts at 191462825a contains this text in 03-transactions.md, and still does on the default branch.
Run it yourselfgit clone https://github.com/lightning/bolts && git -C bolts show 191462825ae341f0a27098765c075f01ca9bc6c2:03-transactions.md | grep -nF 'The amount of the output is fixed at 330 sats, the default dust limit for P2WSH.'
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 2/2, code 1/1History, hash and citation
BOLT 12 offers are longer-lived Lightning payment requests, encoded with the prefix "lno", from which a payer requests a fresh invoice over the Lightning Network itself. BOLT 12 uses blinded paths in place of BOLT 11's payment_secret and payment_metadata.23: open 4 sources
How it worksBuilderEstablishedHigh confidence
Offers are a precursor to an invoice_request: readers will request an invoice
Offers, read 2026-11-20
The human-readable prefix for offers is `lno`.
Encoding, read 2026-11-20
Blinded paths provide an equivalent to `payment_secret` and `payment_metadata` used in BOLT 11.
Rationale, blinded paths, read 2026-11-20
T2Bitcoin Optech topic, OffersBitcoin Optech, says this directly
Offers is a protocol for Lightning that allows nodes to request and receive invoices over LN.
Topic summary, read 2026-11-20
lightning/bolts at 191462825a contains this text in 12-offer-encoding.md, and still does on the default branch.
Run it yourselfgit clone https://github.com/lightning/bolts && git -C bolts show 191462825ae341f0a27098765c075f01ca9bc6c2:12-offer-encoding.md | grep -nF 'The human-readable prefix for offers is `lno`.'
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 4/4, code 1/1History, hash and citation
LND (the Lightning Network Daemon), Core Lightning (previously c-lightning), Eclair (written in Scala) and LDK (the rust-lightning project) are implementations of the Lightning protocol, each developed in its own repository as of 20 November 2026.24: open 4 sources
FactBuilderEstablishedHigh confidence
T1LND README.mdSource code, says this directly
The Lightning Network Daemon (`lnd`) - is a complete implementation of a
Opening description, read 2026-11-20
T1Core Lightning README.mdSource code, says this directly
Core Lightning (previously c-lightning) is a lightweight, highly customizable and
Opening description, read 2026-11-20
T1Eclair README.mdSource code, says this directly
is a Scala implementation of the Lightning Network.
Opening description, read 2026-11-20
T1LDK rust-lightning README.mdSource code, says this directly
is a highly performant and flexible implementation of the Lightning Network protocol.
Opening description, read 2026-11-20
ACINQ/eclair at c96c3d4483 contains this text in README.md.
Run it yourselfgit clone https://github.com/ACINQ/eclair && git -C eclair show c96c3d4483d5627fd1680fef4df7ac163b3b2046:README.md | grep -nF 'is a Scala implementation of the Lightning Network.'
ElementsProject/lightning at 1271f9b613 contains this text in README.md.
Run it yourselfgit clone https://github.com/ElementsProject/lightning && git -C lightning show 1271f9b6134c16b4105f0e2ffca555fffba46116:README.md | grep -nF 'Core Lightning (previously c-lightning)'
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 4/4, code 2/2History, hash and citation

Open problems and recent spec workResearcher

Channel jamming is a denial-of-service attack on Lightning in which an attacker sends payments that it delays settling, tying up the funds or the pending-payment slots of channels along a route of up to 20 hops so honest payments cannot use them.25: open 2 sources
DefinitionResearcherEstablishedMedium confidence
T2Bitcoin Optech topic, Channel jamming attacksBitcoin Optech, says this directly
Denial of Service (DoS) attacks where an attacker can prevent a series of channels up to 20 hops away
Topic summary, read 2026-11-20
T2Bitcoin Optech topic, Channel jamming attacksBitcoin Optech, says this directly
sends it to themselves across 20 other channels
Topic summary, liquidity jamming, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 2/2History, hash and citation
BOLT 2 lets a Lightning node accept at most 483 pending payments (HTLCs) from its channel peer, or 114 on zero_fee_commitments channels. Optech's channel jamming topic describes how the 483 limit enables HTLC jamming: an attacker sends 483 small payments and leaves them unsettled, filling the slots while locking little value.26: open 4 sources
How it worksResearcherEstablishedMedium confidence
T2Bitcoin Optech topic, Channel jamming attacksBitcoin Optech, says this directly
HTLC jamming attack is where an attacker sends 483 small payments
Topic summary, HTLC jamming, read 2026-11-20
T2Bitcoin Optech topic, Channel jamming attacksBitcoin Optech, supports part of it
where 483 is the maximum number of pending payments a channel may contain
Topic summary, HTLC jamming, read 2026-11-20
`max_accepted_htlcs` is greater than 483.
The open_channel Message, receiver requirements (channel types other than zero_fee_commitments), read 2026-11-20
`max_accepted_htlcs` is greater than 114.
The open_channel Message, receiver requirements (channel_type includes zero_fee_commitments), read 2026-11-20
lightning/bolts at 191462825a contains this text in 02-peer-protocol.md, and still does on the default branch.
Run it yourselfgit clone https://github.com/lightning/bolts && git -C bolts show 191462825ae341f0a27098765c075f01ca9bc6c2:02-peer-protocol.md | grep -nF '`max_accepted_htlcs` is greater than 483.'
lightning/bolts at 191462825a contains this text in 02-peer-protocol.md.
Run it yourselfgit clone https://github.com/lightning/bolts && git -C bolts show 191462825ae341f0a27098765c075f01ca9bc6c2:02-peer-protocol.md | grep -nF '`max_accepted_htlcs` is greater than 114.'
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 4/4, code 2/2History, hash and citation
Which defense against Lightning channel jamming, if any, will the BOLTs specify? As of 20 November 2026 this is unresolved. Optech records proposals from 2019 to 2026, including upfront fees and local reputation, and reported LND's experimental reputation scoring in October 2026. A merged BOLTs change would settle it.27: open 3 sources
Open questionResearcherEstablishedMedium confidence
T2Bitcoin Optech topic, Channel jamming attacksBitcoin Optech, says this directly
LND #10919 adds experimental local reputation scoring based on HTLC accountability
Optech newsletter mentions, 2026 (links to the newsletter of 23 October 2026), read 2026-11-20
T2Bitcoin Optech topic, Channel jamming attacksBitcoin Optech, supports part of it
Hashcash and refund-based upfront fees to mitigate jamming
Optech newsletter mentions, 2019, read 2026-11-20
T2Bitcoin Optech topic, Channel jamming attacksBitcoin Optech, supports part of it
Protocol proposed for upfront and hold fees to address channel jamming
Optech newsletter mentions, 2025, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 3/3History, hash and citation
The offers protocol was added to the Lightning specification as BOLT 12 when BOLTs pull request #798 was merged on 24 September 2024, as reported in Optech's newsletter of 4 October 2024.28: open 2 sources
EventResearcherEstablishedHigh confidence
T1lightning/bolts PR #798: OffersPull request, says this directly
Offers are "static invoices", with many more features.
Pull request description; merged 2024-09-24T10:40:59Z, published 2024-09-24, read 2026-11-20
T2Bitcoin Optech Newsletter, 4 October 2024Bitcoin Optech, says this directly
merges the offers protocol specification which introduces BOLT12
Notable code and documentation changes, BOLTs, published 2024-10-04, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 2/2History, hash and citation
Splicing, specified in BOLT 2, replaces a Lightning channel's funding transaction with a new one, which lets the peers add funds to or remove funds from an open channel without closing it. BOLT 9 assigns it the option_splice feature bits 62/63.29: open 3 sources
How it worksResearcherEstablishedHigh confidence
Splicing is the term given for replacing the funding transaction with a new one.
Channel Splicing, read 2026-11-20
T1BOLT 9, Assigned Feature FlagsBOLT, says this directly
Allows replacing the funding transaction with a new one
Feature table, option_splice, read 2026-11-20
T2Bitcoin Optech topic, SplicingBitcoin Optech, supports part of it
Splicing is the act of transferring funds from onchain outputs into a payment channel
Topic summary, read 2026-11-20
lightning/bolts at 191462825a contains this text in 09-features.md, and still does on the default branch.
Run it yourselfgit clone https://github.com/lightning/bolts && git -C bolts show 191462825ae341f0a27098765c075f01ca9bc6c2:09-features.md | grep -nF 'Allows replacing the funding transaction with a new one'
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 3/3, code 1/1History, hash and citation
The splicing protocol was merged into the Lightning specification on 23 March 2026 through BOLTs pull request #1160, "Channel Splicing (feature 62/63)", which replaced the earlier draft in BOLTs pull request #863.30: open 2 sources
EventResearcherEstablishedHigh confidence
Splicing takes place while a channel is quiescent, to ensure that both peers have the same view of the current commitments.
Pull request description; merged 2026-03-23T08:27:48Z, published 2026-03-23, read 2026-11-20
T2Bitcoin Optech Newsletter, 27 March 2026Bitcoin Optech, says this directly
BOLTs #1160 merges the splicing protocol into the Lightning specification, replacing the draft in BOLTs #863
Notable code and documentation changes, BOLTs, published 2026-03-27, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 2/2History, hash and citation
As of 20 November 2026, BOLT 9 in the lightning/bolts repository assigns feature bits 40/41 to zero_fee_commitments, a Lightning channel type whose commitment and HTLC transactions pay zero fees, and points to BOLT 3's shared anchor output for it.31: open 1 source
FactResearcherEstablishedHigh confidence
T1BOLT 9, Assigned Feature FlagsBOLT, says this directly
Zero-fee commitment and HTLC transactions
Feature table, zero_fee_commitments (bits 40/41), read 2026-11-20
lightning/bolts at 191462825a contains this text in 09-features.md, and still does on the default branch.
Run it yourselfgit clone https://github.com/lightning/bolts && git -C bolts show 191462825ae341f0a27098765c075f01ca9bc6c2:09-features.md | grep -nF 'Zero-fee commitment and HTLC transactions'
lightning/bolts at 191462825a contains this text in 09-features.md.
Run it yourselfgit clone https://github.com/lightning/bolts && git -C bolts show 191462825ae341f0a27098765c075f01ca9bc6c2:09-features.md | grep -nF '[BOLT #3][bolt03-shared-anchor]'
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 1/1, code 2/2History, hash and citation
As of 20 November 2026, the lightning/bolts repository holds an extension document, "Simple Taproot Channels", created 20 April 2022, in which the channel's multisignature funding output becomes a single P2TR key formed with MuSig2 key aggregation. It is outside the numbered BOLTs.32: open 2 sources
FactResearcherEstablishedHigh confidence
The multisig output becomes a single P2TR key
Introduction, Abstract, read 2026-11-20
Extension BOLT XX: Simple Taproot Channels
Document header, read 2026-11-20
lightning/bolts at 191462825a contains this text in bolt-simple-taproot.md.
Run it yourselfgit clone https://github.com/lightning/bolts && git -C bolts show 191462825ae341f0a27098765c075f01ca9bc6c2:bolt-simple-taproot.md | grep -nF 'Created: 2022-04-20'
lightning/bolts at 191462825a contains this text in bolt-simple-taproot.md, and still does on the default branch.
Run it yourselfgit clone https://github.com/lightning/bolts && git -C bolts show 191462825ae341f0a27098765c075f01ca9bc6c2:bolt-simple-taproot.md | grep -nF '# Extension BOLT XX: Simple Taproot Channels'
Checked at block 976,759, 20 Nov 2026, 17:27 UTC: quotes 2/2, code 2/2History, hash and citation