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.
Sources and checks
T1BOLT 3, Bitcoin Transaction and Script FormatsBOLT, says this directly
must be delayed for `to_self_delay` blocks
Commitment Transaction Outputs, to_local output, read 2026-11-20
T1BOLT 2, Peer Protocol for Channel ManagementBOLT, says this directly
`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 yourself
git 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/1
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