build(deps): bump github.com/lightningnetwork/lnd from 0.20.0-beta.rc2 to 0.20.0-beta.rc4

[dependabot]

Bumps github.com/lightningnetwork/lnd from 0.20.0-beta.rc2 to 0.20.0-beta.rc4.

Release notes

Sourced from github.com/lightningnetwork/lnd's releases.

lnd v0.20.0-beta.rc4

Database Migrations

• SQL migration of the graph store: This migrates the graph store from the KV format to native SQL. This migration will only run if the --db.use-native-sql flag is set along with the --db.backend option set to sqlite or postgres. Users may opt out of this migration by setting the --db.skip-native-sql-migration flag.

Verifying the Release

In order to verify the release, you'll need to have gpg or gpg2 installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

curl https://raw.githubusercontent.com/lightningnetwork/lnd/master/scripts/keys/roasbeef.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming manifest-roasbeef-v0.20.0-beta.rc4.sig and manifest-v0.20.0-beta.rc4.txt are in the current directory) with:

gpg --verify manifest-roasbeef-v0.20.0-beta.rc4.sig manifest-v0.20.0-beta.rc4.txt

You should see the following if the verification was successful:

gpg: Signature made Wed Sep 30 17:35:20 2020 PDT
gpg:                using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306
gpg: Good signature from "Olaoluwa Osuntokun <laolu32@gmail.com>" [ultimate]

That will verify the signature of the manifest file, which ensures integrity and authenticity of the archive you've downloaded locally containing the binaries. Next, depending on your operating system, you should then re-compute the sha256 hash of the archive with shasum -a 256 <filename>, compare it with the corresponding one in the manifest file, and ensure they match exactly.

Verifying the Release Timestamp

From this new version onwards, in addition time-stamping the git tag with OpenTimestamps, we'll also now timestamp the manifest file along with its signature. Two new files are now included along with the rest of our release artifacts: manifest-roasbeef-v0.20.0-beta.rc4.txt.asc.ots.

Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands:

ots verify manifest-roasbeef-v0.20.0-beta.rc4.sig.ots -f manifest-roasbeef-v0.20.0-beta.rc4.sig

Alternatively, the OpenTimestamps website can be used to verify timestamps if one doesn't have a bitcoind instance accessible locally.

These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.

Verifying the Release Binaries

Our release binaries are fully reproducible. Third parties are able to verify that the release binaries were produced properly without having to trust the release manager(s). See our reproducible builds guide for how this can be achieved. The release binaries are compiled with go1.25.3, which is required by verifiers to arrive at the same ones. They include the following build tags: autopilotrpc, signrpc, walletrpc, chainrpc, invoicesrpc, neutrinorpc, routerrpc, watchtowerrpc, monitoring, peersrpc, kvdb_postrgres, kvdb_etcd and kvdb_sqlite. Note that these are already included in the release script, so they do not need to be provided.

The make release command can be used to ensure one rebuilds with all the same flags used for the release. If one wishes to build for only a single platform, then make release sys=<OS-ARCH> tag=<tag> can be used.

... (truncated)

Commits

• aeac338 Merge pull request #10345 from Roasbeef/v7-rc4
• 2ddb630 build: bump version to v0.7.0 rc4
• 4131a8e Merge pull request #10330 from Roasbeef/fix-error-handling-gossiper
• adaa893 docs: add release notes entry
• b8ca876 discovery/test: add comprehensive tests for state handler error exits
• 06c7d60 discovery: fix endless loop in gossip syncer on context cancellation
• c7c8073 Merge pull request #10334 from ziggie1984/fix-decoding-extra-tlv-data
• 870d603 multi: allow invalid tlv data when decoding payment fail info
• f938e40 Merge pull request #10324 from Roasbeef/v-20-branch-rc3
• 9f5094c Merge pull request #10315 from saubyk/db-migration-guide
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)