This marks the second minor release in the
v0.10.0 series! This release allows
lnd to be compatible with
bitcoind 0.20, and fixes an important bug related to an on disk Static Channel Backups (SCB).
Verifying the Release
In order to verify the release, you’ll need to have
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://keybase.io/roasbeef/pgp_keys.asc | gpg --import
Once you have the required PGP keys, you can verify the release (assuming
manifest-v0.10.2-beta.rc1.txt.sig are in the current directory) with:
gpg --verify manifest-v0.10.2-beta.rc1.txt.sig
You should see the following if the verification was successful:
gpg: assuming signed data in 'manifest-v0.10.2-beta.rc1.txt' gpg: Signature made Thu Jun 18 17:50:06 2020 PDT gpg: using RSA key 4AB7F8DA6FAEBB3B70B1F903BC13F65E2DC84465 gpg: Good signature from "Olaoluwa Osuntokun <email@example.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 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.13.10, which is required by verifiers to arrive at the same ones. They include the following build tags:
watchtowerrpc. Note that these are already included in the release script, so they do not need to be provided.
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.
Finally, you can also verify the tag itself with the following command:
git verify-tag v0.10.2-beta.rc1
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
lnd-source-v0.10.2-beta.tar.gz are in the current directory, follow these steps:
tar -xvzf vendor.tar.gz tar -xvzf lnd-source-v0.10.2-beta.tar.gz GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.10.2-beta" ./cmd/lnd GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.10.2-beta" ./cmd/lncli
-mod=vendor flag tells the
go build command that it doesn’t need to fetch the dependencies, and instead, they’re all enclosed in the local vendor directory.
Additionally, it’s now possible to use the enclosed
release.sh script to bundle a release for a specific system like so:
make release sys="linux-arm64 darwin-amd64"
⚡️⚡️⚡️ OK, now to the rest of the release notes! ⚡️⚡️⚡️
With this new release,
lnd can now be used with
bitcoind 0.20 as it’s full-node chain backend.
SCB Bug Fix
This release includes an important bug fix for static channel backups. Before this release, if a new
lnd node was started with a data directory that contained an existing SCB file, then that existing file would be completely overridden by whatever channel state the new
lnd node started with.
With this new release, of
lnd, we’ll fail to start if we’re unable to read an existing SCB file on disk. Additionally, we’ll always combine the contents of the SCB file with our in-memory channel state.
The full list of changes since
v0.10.1-beta can be found here:
Contributors (Alphabetical Order)