fundingmanager: adds default ltc funding constraints

This commit is contained in:
Conner Fromknecht 2018-03-14 14:54:04 -07:00
parent 0c6a85d5f7
commit 8cecdc54cf
No known key found for this signature in database
GPG Key ID: 39DE78FBE6ACB0EF
1 changed files with 13 additions and 6 deletions

View File

@ -42,12 +42,19 @@ const (
// TODO(roasbeef): add command line param to modify // TODO(roasbeef): add command line param to modify
maxFundingAmount = btcutil.Amount(1 << 24) maxFundingAmount = btcutil.Amount(1 << 24)
// minRemoteDelay and maxRemoteDelay is the extremes of the CSV delay // minBtcRemoteDelay and maxBtcRemoteDelay is the extremes of the
// we will require the remote to use for its commitment transaction. // Bitcoin CSV delay we will require the remote to use for its
// The actual delay we will require will be somewhere between these // commitment transaction. The actual delay we will require will be
// values, depending on channel size. // somewhere between these values, depending on channel size.
minRemoteDelay = 144 minBtcRemoteDelay uint16 = 144
maxRemoteDelay = 2016 maxBtcRemoteDelay uint16 = 2016
// minLtcRemoteDelay and maxLtcRemoteDelay is the extremes of the
// Litecoin CSV delay we will require the remote to use for its
// commitment transaction. The actual delay we will require will be
// somewhere between these values, depending on channel size.
minLtcRemoteDelay uint16 = 576
maxLtcRemoteDelay uint16 = 8064
// maxWaitNumBlocksFundingConf is the maximum number of blocks to wait // maxWaitNumBlocksFundingConf is the maximum number of blocks to wait
// for the funding transaction to be confirmed before forgetting about // for the funding transaction to be confirmed before forgetting about