Are you referring to a stale channel state that's been published that is now outside of the CSV timelock period? Yes, competing for confirmation in a block in that case would be paramount.
But prior to that you'd still have plenty of time (days) to penalize a stale force close attempt due to the to_self_delay that you set for the channel when you opened it. A time-locked transaction wouldn't validate on any node prior to that.
Tyler Burns
npub1d3…xynp3
2025-05-05 15:10:00
in reply to nevent1q…cglr
Author Public Key
npub1d30mhvhd0sagmu83wdm26wqk00heptfn05xvgmfx7r9xscstnfcs7xynp3Published at
2025-05-05 15:10:00Event JSON
{
"id": "8ed99b69f18be0543797b8c5d2975ee5e0d510d4586c0c0b8efc8e67a27314db",
"pubkey": "6c5fbbb2ed7c3a8df0f17376ad38167bef90ad337d0cc46d26f0ca68620b9a71",
"created_at": 1746457800,
"kind": 1,
"tags": [
[
"e",
"8f2e2e84dfcaa59d1879f360791ed370d1fcb36b77f86dcd74837be51a0ff674",
"",
"root"
],
[
"p",
"f728d9e6e7048358e70930f5ca64b097770d989ccd86854fe618eda9c8a38106"
]
],
"content": "Are you referring to a stale channel state that's been published that is now outside of the CSV timelock period? Yes, competing for confirmation in a block in that case would be paramount. \n\nBut prior to that you'd still have plenty of time (days) to penalize a stale force close attempt due to the to_self_delay that you set for the channel when you opened it. A time-locked transaction wouldn't validate on any node prior to that.",
"sig": "f86b6f004a6fd0df04ff76d8a3b9342dd405eff8f1a427ef28d707965ad14a5bc09f5d07dffe91da596fd3cf023de5a7645dbd9cac59f3b8212f2f35c0dbc316"
}