Skip to content

@Roasbeef Roasbeef released this Dec 12, 2019 · 696 commits to master since this release

This release marks the second minor release in the v0.8.x series and contains no major new features. This release includes a number of fixes for SCB (Static Channel Backup) recovery, additional logging in the ChainNotifier, and a consistency fix to the SendToRoute RPC call.

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://keybase.io/roasbeef/pgp_keys.asc | gpg --import

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

gpg --verify manifest-v0.8.2-beta.txt.sig

You should see the following if the verification was successful:

gpg: assuming signed data in 'manifest-v0.8.2-beta.txt'
gpg: Signature made Wed Dec 11 17:18:41 2019 PST
gpg:                using RSA key 4AB7F8DA6FAEBB3B70B1F903BC13F65E2DC84465
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 Binaries

As of this release, our release binaries are fully reproducible thanks to go1.13! Third parties are now 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.4, which is required by verifiers to arrive at the same ones. They include the following build tags: autopilotrpc, signrpc, walletrpc, chainrpc, invoicesrpc, routerrpc, and watchtowerrpc. Note that these are already included in the release script, so they do not need to be provided.

Finally, you can also verify the tag itself with the following command:

git verify-tag v0.8.2-beta

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.8.2-beta.tar.gz are in the current directory, follow these steps:

tar -xvzf vendor.tar.gz
tar -xvzf lnd-source-v0.8.2-beta.tar.gz
GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.8.2-beta" ./cmd/lnd
GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.8.2-beta" ./cmd/lncli

The -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:

LNDBUILDSYS="linux-arm64 darwin-amd64" ./build/release/release.sh

⚡️⚡️⚡️ OK, now to the rest of the release notes! ⚡️⚡️⚡️

Release Notes

It's now possible to use an SCB to recover the funds of an unconfirmed channel. Before this fix, if one attempted to recover an SCB for a channel which was unconfirmed at . the time of SCB creation, then the process would fail. We'll node encode a special short channel ID to detect this case to ensure the channel funds can be recovered as normal.

We'll now warn a user that is using the lncli unlock or lncli create calls to recover an SCB. The new warning message now makes it more clear that in order to recover the funds of the channel, we need to close the channel on chain, resulting in additional chain fees.

If some or all of the channels in a Multi SCB backup have already been received, then we'll no longer exit early. Instead, this case will be detected allowing a user to re-issue an SCB recovery CLI or RPC command.

The SendToRoute RPC call has been updated to properly check the current max payment size parameter of the registered router backend, just as all the other payment RPC calls do.

Changelog

The full list of changes since v0.8.1-beta can be found here:

Contributors (Alphabetical Order)

Andreas M. Antonopoulos
Johan T. Halseth
Olaoluwa Osuntokun
Oliver Gugger

Assets 37
You can’t perform that action at this time.