From bf7f79fc90272144823114599a14a76564ab4844 Mon Sep 17 00:00:00 2001 From: ismaelsadeeq Date: Wed, 15 Jul 2026 11:06:02 +0100 Subject: [PATCH] docs: merge UTXO/script level rows in timelocks table The table listed "UTXO Level" and "(or Script Level)" as two separate rows, making it look like three distinct enforcement levels and like CLTV/CSV were different mechanisms from CheckLockTimeVerify/ CheckSequenceVerify. Merge them into a single row since script level is just another name for the UTXO level and CLTV/CSV are abbreviations. --- the-lightning-network/multihop-payments/timelocks.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/the-lightning-network/multihop-payments/timelocks.md b/the-lightning-network/multihop-payments/timelocks.md index 051925d4..b340e756 100644 --- a/the-lightning-network/multihop-payments/timelocks.md +++ b/the-lightning-network/multihop-payments/timelocks.md @@ -8,11 +8,10 @@ description: >- A time-locked Bitcoin transaction is one that is only valid after a certain period of time. Such timelocks are used extensively in the Lightning Network and broadly fall under two categories, absolute timelocks and relative timelocks. -|


| Absolute Timelock | Relative Timelock | -| ----------------- | ------------------- | ------------------- | -| Transaction Level | nLockTime | nSequence | -| UTXO Level | CheckLockTimeVerify | CheckSequenceVerify | -| (or Script Level) | CLTV | CSV | +|


| Absolute Timelock | Relative Timelock | +| ----------------------------- | -------------------------- | -------------------------- | +| Transaction Level | nLockTime | nSequence | +| UTXO (or Script) Level | CheckLockTimeVerify (CLTV) | CheckSequenceVerify (CSV) | ## Absolute timelocks