From e7776a4c1ed3b5c205133469de6fe7f0055af0ef Mon Sep 17 00:00:00 2001 From: Boris Nagaev Date: Sun, 15 Oct 2023 15:49:02 +0200 Subject: [PATCH] contractcourt: fix doc of commitSweepResolver It is used for sweeping time-locked outputs as well as non time-locked outputs. --- contractcourt/commit_sweep_resolver.go | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/contractcourt/commit_sweep_resolver.go b/contractcourt/commit_sweep_resolver.go index 8f1169580..4b47a3429 100644 --- a/contractcourt/commit_sweep_resolver.go +++ b/contractcourt/commit_sweep_resolver.go @@ -20,9 +20,15 @@ import ( ) // commitSweepResolver is a resolver that will attempt to sweep the commitment -// output paying to us, in the case that the remote party broadcasts their -// version of the commitment transaction. We can sweep this output immediately, -// as it doesn't have a time-lock delay. +// output paying to us (local channel balance). In the case that the local +// party (we) broadcasts their version of the commitment transaction, we have +// to wait before sweeping it, as it has a CSV delay. For anchor channel +// type, even if the remote party broadcasts the commitment transaction, +// we have to wait one block after commitment transaction is confirmed, +// because CSV 1 is put into the script of UTXO representing local balance. +// Additionally, if the channel is a channel lease, we have to wait for +// CLTV to expire. +// https://docs.lightning.engineering/lightning-network-tools/pool/overview type commitSweepResolver struct { // localChanCfg is used to provide the resolver with the keys required // to identify whether the commitment transaction was broadcast by the