4 Commits

Author	SHA1	Message	Date
Graham Krizek	e0fc5bb234	lnencrypt: Moves the crypto functions in the chanbackup package into its own package called lnencrypt ... The functions inside of the crypto.go file in chanbackup (like EncryptPayloadToWriter and DecryptPayloadFromReader) can be used by a lot of things outside of just the chanbackup package. We can't just reference them directly from the chanbackup package because it's likely that it would generate circular dependencies. Therefore we need to move these functions into their own package to be referenced by chanbackup and whatever new functionality that needs them	2022-09-30 01:53:45 -05:00
Tommy Volk	9a10c80bcb	multi: move many t.Fatalf calls to require.NoError	2022-06-17 04:26:55 +00:00
Oliver Gugger	7dfe4018ce	multi: use btcd's btcec/v2 and btcutil modules ... This commit was previously split into the following parts to ease review: - 2d746f68: replace imports - 4008f0fd: use ecdsa.Signature - 849e33d1: remove btcec.S256() - b8f6ebbd: use v2 library correctly - fa80bca9: bump go modules	2022-03-09 19:02:37 +01:00
Olaoluwa Osuntokun	7fcab83bb4	chanbackup: add functions to allow recovery of existing channel backups ... In this commit, we add a series of functions that will allow users to recover existing channel backups. We do this using two primary interfaces: the ChannelRestorer, and the PeerConnector. The first interfaces allows us to abstract away the details w.r.t exactly how a channel is restored. Instead, we simply expect that the channel backup will be inserted as a sort of "channel shell" which contains only the data required to initiate the data loss protection protocol. The second interface is how we instruct the Lightning node to connect out to the channel peer given its known addresses.	2019-01-23 18:11:29 -08:00