lnd v0.20.8-beta

Release notes

Database Migrations

There are no migrations in this release.

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 -fsSL https://raw.githubusercontent.com/lightningnetwork/lnd/v0.20.8-beta/scripts/keys/roasbeef.asc | gpg --import

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

gpg --verify manifest-roasbeef-v0.20.8-beta.sig manifest-v0.20.8-beta.txt

A successful verification reports a good signature from the expected signer.

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

Use OpenTimestamps to verify an OpenTimestamps proof supplied with a manifest signature, such as manifest-roasbeef-v0.20.8-beta.sig.ots.

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

ots verify manifest-roasbeef-v0.20.8-beta.sig.ots -f manifest-roasbeef-v0.20.8-beta.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.

Use go1.27.3 when reproducing this release.

The release build tags are autopilotrpc, signrpc, walletrpc, chainrpc, invoicesrpc, watchtowerrpc, neutrinorpc, monitoring, peersrpc, kvdb_postgres, kvdb_etcd, kvdb_sqlite. The release script includes these tags automatically.

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.

The release tag is signed by Ziggie. Import the tag signer's public key and verify the tag:

curl -fsSL https://raw.githubusercontent.com/lightningnetwork/lnd/v0.20.8-beta/scripts/keys/ziggie1984.asc | gpg --import

git verify-tag v0.20.8-beta

Verifying the Docker Images

To verify the lnd and lncli binaries inside the docker images against the signed, reproducible release binaries, there is a verification script in the image that can be called (before starting the container for example):

$ docker run --rm --entrypoint="" lightninglabs/lnd:v0.20.8-beta /verify-install.sh v0.20.8-beta

$ OK=$?

$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done

$ docker run lightninglabs/lnd:v0.20.8-beta [command-line options]

Building the Contained Release

Users are able to rebuild the target release themselves without having to fetch any of the dependencies. In order to do so, assuming

that vendor.tar.gz and lnd-source-v0.20.8-beta.tar.gz are in the current directory, follow these steps:

tar -xvzf lnd-source-v0.20.8-beta.tar.gz

mv vendor.tar.gz lnd-source/

cd lnd-source

tar -xvzf vendor.tar.gz

go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.20.8-beta" ./cmd/lnd

go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.20.8-beta" ./cmd/lncli

The -mod=vendor flag tells the go build command that it doesn't need to…