contractcourt: fix doc of commitSweepResolver
It is used for sweeping time-locked outputs as well as non time-locked outputs.
This commit is contained in:
1 file changed
+9
-3
@@ -20,9 +20,15 @@ import (
|
|||||||
)
|
)
|
||||||
|
|
||||||
// commitSweepResolver is a resolver that will attempt to sweep the commitment
|
// commitSweepResolver is a resolver that will attempt to sweep the commitment
|
||||||
// output paying to us, in the case that the remote party broadcasts their
|
// output paying to us (local channel balance). In the case that the local
|
||||||
// version of the commitment transaction. We can sweep this output immediately,
|
// party (we) broadcasts their version of the commitment transaction, we have
|
||||||
// as it doesn't have a time-lock delay.
|
// 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 {
|
type commitSweepResolver struct {
|
||||||
// localChanCfg is used to provide the resolver with the keys required
|
// localChanCfg is used to provide the resolver with the keys required
|
||||||
// to identify whether the commitment transaction was broadcast by the
|
// to identify whether the commitment transaction was broadcast by the
|
||||||
|
|||||||
Reference in new issue
Block a user