fundingmanager: bump max non-initiator funding timeout to 2 weeks
The previous value was set to two days, which may not be enough to handle large fee spikes where users still which to submit channels with a low fee and don't mind lowering their time preference. Since the timeout is only applied to channels that we don't initiate, there's real downside since it's not our funds that are locked up.
This commit is contained in:
2 files changed
+7
-7
No files matched your search
+3
-3
@@ -49,9 +49,9 @@ const (
|
||||
maxLtcRemoteDelay uint16 = 8064
|
||||
|
||||
// maxWaitNumBlocksFundingConf is the maximum number of blocks to wait
|
||||
// for the funding transaction to be confirmed before forgetting about
|
||||
// the channel. 288 blocks is ~48 hrs
|
||||
maxWaitNumBlocksFundingConf = 288
|
||||
// for the funding transaction to be confirmed before forgetting
|
||||
// channels that aren't initiated by us. 2016 blocks is ~2 weeks.
|
||||
maxWaitNumBlocksFundingConf = 2016
|
||||
|
||||
// minChanFundingSize is the smallest channel that we'll allow to be
|
||||
// created over the RPC interface.
|
||||
|
||||
Reference in new issue
Block a user