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.
Sources and checks
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
T1BOLT 2, Peer Protocol for Channel ManagementBOLT, says this directly
`max_accepted_htlcs` is greater than 483.
The open_channel Message, receiver requirements (channel types other than zero_fee_commitments), read 2026-11-20
T1BOLT 2, Peer Protocol for Channel ManagementBOLT, says this directly
`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 yourself
git 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 yourself
git 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/2
History
Nothing is edited silently; every revision keeps what it replaced.
- 20 Nov 2026, 17:27 UTCblock 976,759
Published Revision 1, run 2026-11-20-seed-lightning