This is the 3rd minor release in the `v0.10.0-beta-series`. Unlike `v0.10.2-beta` which only includes bug-fixes, this release also includes some refactoring to the main `lnd` package that allows `lnd` to more easily be embedded as a normal struct (by importing the package) on other Go projects. # 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 | gpg --import ``` Once you have the required PGP keys, you can verify the release (assuming `manifest-v0.10.3-beta.txt` and `manifest-v0.10.3-beta.txt.sig` are in the current directory) with: ``` gpg --verify manifest-v0.10.3-beta.txt.sig ``` You should see the following if the verification was successful: ``` gpg: assuming signed data in 'manifest-v0.10.3-beta.txt' gpg: Signature made Mon Jul 6 12:59:00 2020 PDT gpg: using RSA key 4AB7F8DA6FAEBB3B70B1F903BC13F65E2DC84465 gpg: Good signature from "Olaoluwa Osuntokun " [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 `, 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.12`, 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. 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= tag=` can be used. Finally, you can also verify the _tag_ itself with the following command: ``` git verify-tag v0.10.3-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.10.3-beta.tar.gz` are in the current directory, follow these steps: ``` tar -xvzf vendor.tar.gz tar -xvzf lnd-source-v0.10.3-beta.tar.gz GO111MODULE=on go install -v -mod=vendor -ldflags "-X" ./cmd/lnd GO111MODULE=on go install -v -mod=vendor -ldflags "-X" ./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 `` 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! ⚡️⚡️⚡️ # Release Notes ## `lnd` Package Refactoring In prior releases, we've started to refactor the way `lnd` is initialized and started to make it easier to emebdd `lnd` in other Go applications. The primary consumer of these APIs so far has been our mobile bindings for `lnd`. In this release [we continue the process to further abstract the `lnd` package]( with a series of PRs that [remove a number of global variables, allow external sub-server registration](, and [external logging hooks]( The full list of changes since `v0.10.2-beta` can be found here: * # Contributors (Alphabetical Order) Oliver Gugger