lnd v0.10.1-beta

This marks the first minor release in the `v0.10.0` series! This release contains no major new features. Instead this release packages a series of bug fixes, a new dry run migration mode (to test out migrations before they're applied permanently), and an enhancement to the channel selection/restrictions in the router sub-server. # 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.10.1-beta.txt` and `manifest-v0.10.1-beta.txt.sig` are in the current directory) with: ``` gpg --verify manifest-v0.10.1-beta.txt.sig ``` You should see the following if the verification was successful: ``` pg: assuming signed data in 'manifest-v0.10.1-beta.txt' gpg: Signature made Wed Jun 3 11:32:57 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](https://github.com/lightningnetwork/lnd/tree/master/build/release) 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: `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.1-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.1-beta.tar.gz` are in the current directory, follow these steps: ``` tar -xvzf vendor.tar.gz tar -xvzf lnd-source-v0.10.1-beta.tar.gz GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.10.1-beta" ./cmd/lnd GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.10.1-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](https://github.com/lightningnetwork/lnd/pull/2191): ``` make release sys="linux-arm64 darwin-amd64" ``` ⚡️⚡️⚡️ OK, now to the rest of the release notes! ⚡️⚡️⚡️ # Release Notes ## btcd Compatability With this release, [`lnd` is now compatible with the current master branch of `btcd`](https://github.com/lightningnetwork/lnd/pull/4291), which included some changes to certain RPCs to sync them up with the latest iteration of them in `bitcoind`. ## Easier Migration Testing w/ Dry Run Migrations [In this release, a new flag has been added: `--dry-run-migration`](https://github.com/lightningnetwork/lnd/pull/2668). As regular users of `lnd` are aware, we typically have a set of migrations that are bundled with _major_ releases of `lnd`. Testing these new migrations can be tricky at times, since one a migration has been applied, one cannot go back. To make this process easier and less stressful for users (and also developers testing out migrations), the new `--dry-run-migration` flag will attempt to apply the migration as normal, but then rather than committing the database transaction, it'll perform an abort, leaving the database in the same state as before the migration. It's our hope that this new flag will make it easier for existing users to help us _test_ the release candidates of major releases. ## RPC Bug Fixes [The `ListChannels` command will now properly omit uptime in the response if the server has not yet been started](https://github.com/lightningnetwork/lnd/pull/4176). It's possible to execute this call before the server has been started (backend synced to the chain), but as we don't connect to peers before the server is fully started, the uptime information isn't available. [A bug in the new streaming HTLC forwarding RPC](https://github.com/lightningnetwork/lnd/pull/4234) has been fixed which could at times cause a panic if a link failure doesn't come along with the full details as expected. [A bug has been fixed that would cause a panic](https://github.com/lightningnetwork/lnd/pull/4226) if a user attempted to use the `ChainNotifier` sub-server before the server has been fully started. In order to make limits across the payment relate RPCs consistent, [`QueryRoutes` now also allows users to query for routes with a payment value larger than the previous max payment size](https://github.com/lightningnetwork/lnd/pull/4335). Note that the "true' max payment size along a route, is limited by the _smallest_ `max_htlc`for a channel along the route. ## RPC Enhancements [The `SendPayment` method on the new router rpc sub-server has been extended to allow users to specify a set of channels that the outgoing payments _must_ use](https://github.com/lightningnetwork/lnd/pull/4257). This is useful as when doing MPP, the users can ensure that only a set of channels are used, which can be helpful in more precise rebalancing operations, and services such as Lightning Loop. The old `outgoing_chan_id` has been deprecated in favor of a new `outgoing_chan_ids` field which accepts a series of channel IDs to pin path finding to. ## Pathfinding Bug Fixes [The main path finding loop will no longer treat an instance of "bad features" as a terminal error](https://github.com/lightningnetwork/lnd/pull/4327). ## Watchtower Bug Fixes [A bug has been fixed that would at times cause a panic when a user would switch towers using the `lncli wtclient` series of commands](https://github.com/lightningnetwork/lnd/pull/4274). ## Build Fixes A change that went into lnd `v0.10.0-beta` inadvertently broke the build for those users still using Go 1.12. As we support Go 1.13 and 1.12 primarily, [a fix has been made to ensure the project still builds with Go 1.12](https://github.com/lightningnetwork/lnd/pull/4253). We plan to "officially" support Go 1.14 for lnd `v0.11.0-beta`, pending some fixes to upstream packages we depend on. The full list of changes since `v0.10.0-beta` can be found here: * https://github.com/lightningnetwork/lnd/compare/v0.10.0-beta...v0.10.1-beta-branch # Contributors (Alphabetical Order) Carla Kirkk-Cohen Conner Fromknecht Joost Jager Olaoluwa Osuntokun Roei Erez Wilmer Paulino