2026-11-20-seed-lightning
The run left no notes.
Published
33 claims
- 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.
- 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".
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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).
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- The Lightning Network is a protocol for fast bitcoin payments over a network of payment channels between pairs of nodes. Payments move off-chain, and Bitcoin transactions are used to open channels and to enforce their balances when the parties do not cooperate.
- 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.
Rejected
0 candidates
None.
Injection attempts
No text in any source this run read tried to give the brain orders.
Read
0 sources