Merge pull request #161 from starius/update-lnd-v0.18.3-beta

go.mod: update lnd to v0.18.3-beta

Author: guggero

cmd/chantools/fakechanbackup.go

@@ -347,13 +347,15 @@ func newSingle(fundingOutPoint wire.OutPoint, shortChanID lnwire.ShortChannelID,
 
 func fakeChanCfg(nodePubkey *btcec.PublicKey) channeldb.ChannelConfig {
 	return channeldb.ChannelConfig{
-		ChannelConstraints: channeldb.ChannelConstraints{
-			DustLimit:        500,
+		ChannelStateBounds: channeldb.ChannelStateBounds{
 			ChanReserve:      5000,
 			MaxPendingAmount: 1,
 			MinHTLC:          1,
 			MaxAcceptedHtlcs: 200,
-			CsvDelay:         144,
+		},
+		CommitmentParams: channeldb.CommitmentParams{
+			DustLimit: 500,
+			CsvDelay:  144,
 		},
 		MultiSigKey: keychain.KeyDescriptor{
 			PubKey: nodePubkey,

cmd/chantools/root.go

@@ -36,7 +36,8 @@ const (
 
 	// lndVersion is the current version of lnd that we support. This is
 	// shown in some commands that affect the database and its migrations.
-	lndVersion = "v0.18.0-beta"
+	// Run "make docs" after changing this value.
+	lndVersion = "v0.18.3-beta"
 
 	Commit = ""
 )

doc/chantools_deletepayments.md

@@ -10,7 +10,7 @@ If only the failed payments should be deleted (and not the successful ones), the
 
 CAUTION: Running this command will make it impossible to use the channel DB
 with an older version of lnd. Downgrading is not possible and you'll need to
-run lnd v0.18.0-beta or later after using this command!'
+run lnd v0.18.3-beta or later after using this command!'
 
 ```
 chantools deletepayments [flags]

doc/chantools_dropchannelgraph.md

@@ -12,7 +12,7 @@ without removing any other data.
 
 CAUTION: Running this command will make it impossible to use the channel DB
 with an older version of lnd. Downgrading is not possible and you'll need to
-run lnd v0.18.0-beta or later after using this command!'
+run lnd v0.18.3-beta or later after using this command!'
 
 ```
 chantools dropchannelgraph [flags]

doc/chantools_dropgraphzombies.md

@@ -12,7 +12,7 @@ be helpful to fix a graph that is out of sync with the network.
 
 CAUTION: Running this command will make it impossible to use the channel DB
 with an older version of lnd. Downgrading is not possible and you'll need to
-run lnd v0.18.0-beta or later after using this command!'
+run lnd v0.18.3-beta or later after using this command!'
 
 ```
 chantools dropgraphzombies [flags]

doc/chantools_fakechanbackup.md

@@ -61,7 +61,7 @@ chantools fakechanbackup --from_channel_graph lncli_describegraph.json \
       --channelpoint string         funding transaction outpoint of the channel to rescue (<txid>:<txindex>) as it is displayed on 1ml.com
       --from_channel_graph string   the full LN channel graph in the JSON format that the 'lncli describegraph' returns
   -h, --help                        help for fakechanbackup
-      --multi_file string           the fake channel backup file to create (default "results/fake-2024-06-18-10-55-31.backup")
+      --multi_file string           the fake channel backup file to create (default "results/fake-2024-09-20-09-53-53.backup")
       --remote_node_addr string     the remote node connection information in the format pubkey@host:port
       --rootkey string              BIP32 HD root key of the wallet to use for encrypting the backup; leave empty to prompt for lnd 24 word aezeed
       --short_channel_id string     the short channel ID in the format <blockheight>x<transactionindex>x<outputindex>

doc/chantools_migratedb.md

@@ -11,7 +11,7 @@ needs to read the database content.
 
 CAUTION: Running this command will make it impossible to use the channel DB
 with an older version of lnd. Downgrading is not possible and you'll need to
-run lnd v0.18.0-beta or later after using this command!'
+run lnd v0.18.3-beta or later after using this command!'
 
 ```
 chantools migratedb [flags]

doc/chantools_removechannel.md

@@ -11,7 +11,7 @@ channel was never confirmed on chain!
 
 CAUTION: Running this command will make it impossible to use the channel DB
 with an older version of lnd. Downgrading is not possible and you'll need to
-run lnd v0.18.0-beta or later after using this command!
+run lnd v0.18.3-beta or later after using this command!
 
 ```
 chantools removechannel [flags]

doc/chantools_rescueclosed.md

@@ -58,6 +58,7 @@ chantools rescueclosed --fromsummary results/summary-xxxxxx.json \
   -h, --help                      help for rescueclosed
       --listchannels string       channel input is in the format of lncli's listchannels format; specify '-' to read from stdin
       --lnd_log string            the lnd log file to read to get the commit_point values when rescuing multiple channels at the same time
+      --num_keys uint32           the number of keys to derive for the brute force attack (default 5000)
       --pendingchannels string    channel input is in the format of lncli's pendingchannels format; specify '-' to read from stdin
       --rootkey string            BIP32 HD root key of the wallet to use for decrypting the backup; leave empty to prompt for lnd 24 word aezeed
       --walletdb string           read the seed/master root key to use fro decrypting the backup from an lnd wallet.db file instead of asking for a seed or providing the --rootkey flag

doc/chantools_sweeptimelockmanual.md

@@ -56,7 +56,7 @@ chantools sweeptimelockmanual \
       --listchannels string         channel input is in the format of lncli's listchannels format; specify '-' to read from stdin
       --maxcsvlimit uint16          maximum CSV limit to use (default 2016)
       --maxnumchanstotal uint16     maximum number of keys to try, set to maximum number of channels the local node potentially has or had (default 500)
-      --maxnumchanupdates uint      maximum number of channel updates to try, set to maximum number of times the channel was used (default 500)
+      --maxnumchanupdates uint      maximum number of channel updates to try, set to maximum number of times the channel was used (default 1000)
       --pendingchannels string      channel input is in the format of lncli's pendingchannels format; specify '-' to read from stdin
       --publish                     publish sweep TX to the chain API instead of just printing the TX
       --remoterevbasepoint string   remote node's revocation base point, can be found in a channel.backup file