Releases: lightningnetwork/lnd
lnd v0.10.1-beta.rc3
lnd v0.10.1-beta.rc3
v0.10.1-beta.rc2
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.rc2.txt and manifest-v0.10.1-beta.rc2.txt.sig are in the current directory) with:
gpg --verify manifest-v0.10.1-beta.rc2.txt.sig
You should see the following if the verification was successful:
gpg: assuming signed data in 'manifest-v0.10.1-beta.rc2.txt'
gpg: Signature made Mon May 18 20:07:59 2020 PDT
gpg: using RSA key 4AB7F8DA6FAEBB3B70B1F903BC13F65E2DC84465
gpg: Good signature from "Olaoluwa Osuntokun <[email protected]>" [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: 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=<OS-ARCH> tag=<tag> can be used.
Finally, you can also verify the tag itself with the following command:
git verify-tag v0.10.1-beta.rc2
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.rc2.tar.gz are in the current directory, follow these steps:
tar -xvzf vendor.tar.gz
tar -xvzf lnd-source-v0.10.1-beta.rc2.tar.gz
GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.10.1-beta.rc2" ./cmd/lnd
GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.10.1-beta.rc2" ./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:
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, 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. 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 teh response if the server has not yet been started. 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 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 if a user attempted to use the ChainNotifier sub-server before the server has been fully started.
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. 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.
Watchtower Bug Fixes
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. 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:
Contributors (Alphabetical Order)
Carla Kirkk-Cohen
Conner Fromknecht
Joost Jager
Olaoluwa Osuntokun
Roei Erez
Wilmer Paulino
lnd v0.10.1-beta.rc1
lnd v0.10.1-beta.rc1
lnd v0.10.0-beta
This marks the first major release in the v0.10.0 series! This release contains several new features including support for sender-side MPP payment splitting, PSBT channel funding, and much more. Notably, this release also includes a new experimental commitment type (anchor commitments). As usual, this release also contains a number of optimizations and bug fixes.
Database Migrations
This release contains a single migration which modifies the structure of the on-disk representation of payments for the sake of the new MPP payment splitting feature. This migration should look something like this upon initial start up:
2020-04-15 18:19:18.113 [INF] LTND: Version: 0.10.0-beta. commit=v0.10.0-beta, build=development, logging=default
2020-04-15 18:19:18.376 [INF] LTND: Opening the main database, this might take a few minutes..
2020-04-15 18:19:18.380 [INF] CHDB: Checking for schema update: latest_version=13, db_version=12
2020-04-15 18:19:18.381 [INF] CHDB: Performing database schema migration
2020-04-15 18:19:18.381 [INF] CHDB: Applying migration #13
2020-04-15 18:19:18.381 [INF] CHDB: Migrating payments to mpp structure
2020-03-15 18:19:18.391 [INF] LTND: Database now open (time_to_open=15.651683ms)
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.9.2-beta.txt and manifest-v0.10.0-beta.txt.sig are in the current directory) with:
gpg --verify manifest-v0.10.0-beta.txt.sig
You should see the following if the verification was successful:
gpg: assuming signed data in 'manifest-v0.10.0-beta.txt'
gpg: Signature made Wed Apr 29 11:02:38 2020 PDT
gpg: using RSA key 4AB7F8DA6FAEBB3B70B1F903BC13F65E2DC84465
gpg: Good signature from "Olaoluwa Osuntokun <[email protected]>" [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: 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=<OS-ARCH> tag=<tag> can be used.
Finally, you can also verify the tag itself with the following command:
git verify-tag v0.10.0-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.0-beta.tar.gz are in the current directory, follow these steps:
tar -xvzf vendor.tar.gz
tar -xvzf lnd-source-v0.10.0-beta.tar.gz
GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.10.0-beta" ./cmd/lnd
GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.10.0-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:
make release sys="linux-arm64 darwin-amd64"
⚡️⚡️⚡️ OK, now to the rest of the release notes! ⚡️⚡️⚡️
Release Notes
Architectural Changes
As is today, the default database for lnd is bbolt, an embedded key-value store based on a B+Tree. In the future, we'd like to enable users to be able to swap out bbolt for any arbitrary strongly consistent database. In this release, we've made a step towards this goal by introducing a new KV-store database abstraction. This new interface allows any database implementation which can adhere to the interface to be dropped into lnd.
In the upcoming versions of lnd, the first new database we plan to support is etcd, a strongly consistent distributed key-value store which is used as the basis of projects such as Kubernetes. etcd actually uses bbolt underneath the hood, so it won't be a drastic departure. Once this issue to further abstract the initialization of lnd is complete, then users will be able to "build their own lnd", attaching a database implementation at runtime which adhere to the the primary interface.
Wallet Bug Fixes
A bug was fixed in btcwallet that would at times (non-deterministically) result in change addresses not being picked up doing a full wallet recovery instance. A bug related to map iteration order would at times cause a change address to be placed a "non-default scope" (where we store all the keys for contracts: multi-sig keys, etc), rather than the main "default scope". The end result is that due to this bug, it's possible that prior instances of full wallet recovery (seed import) missed some funds on chain. If you've ever recovered an existing lnd wallet, then ceased using it, we strongly recommend that you attempt the seed import process again, as there may be funds that weren't picked up the first time around.
Payments
Multi-Path Payments Sending Support
Receiving multi-path payments was already possible since version 0.9. Today we are pleased to announce that this release completes the circle by adding support for multi-path payment sending.
Preparatory changes for the send functionality that were implemented during the development process are database support for multiple htlcs per payment and a payment loop that is aware of partial sends.
The splitting algorithm that is employed is a variation of "divide and conquer". First, lnd will try to complete the payment in a single shot. If that is not possible - because channel capacities aren't sufficient or other constraints like the fee limit are hit - an attempt is made for half the payment amount. After that htlc has been launched, a second path is searched for to pay the remaining amount (the other half). If further failures happen, amounts are repeatedly split until a minimum amount limit is reached or the payment succeeds.
We opted for this relatively simple strategy to begin with. It is expected to address various basic liquidity problems that arose in the past, but it is unlikely to always execute payments in a way that is optimal. The field of multi-path planning is still mostly uncharted and contains lots of challenges. Therefore we hope to collect valuable feedback with this release and use that to drive further development.
Multi-path payments can only be initiated through the routerrpc.SendPayment rpc. Payments will be single-shot by default unless the new parameter max_shards is set to a value greater than one. max_shards controls the maximum number of paths that will be used for the payment.
The following lncli command can be used to make a multi-path payment:
lncli payinvoice --max_shards 5 <payreq>
Additionally, the payment limit has now be removed for calls to the new MPP-enabled payment API. This allows users to now send payments that fully utilize all their outgoing payment bandwidth.
Payment tracking
Improvements have been made to provide more fine-grained information about the status of payments.
A list of per-payment htlcs was already added in a prior release. This has now been extended with the exact failure reason for failed htlcs.
Furthermore the payment status stream that is returned by routerrpc.SendPayment and routerrpc.TrackPayment now also contains intermediate state updates. An example of this is the launch of an additional htlc. This will result in a state update on the stream.
The proto message on these update streams has been aligned to match the main rpc Payment message. This is a breaking change in the sub-server API.
Invoices
Lifted Invoice Limit
As part of the mpp changes, the invoice limit has been lifted from 4.2 million satoshis. With this change, receivers will now be able to create invoices that can be used in tandem with mpp at the sender, to fully utilize the channel bandwidth at both the sender and receiver to complete pay...
lnd v0.10.0-beta.rc6
lnd v0.10.0-beta.rc6
lnd v0.10.0-beta.rc5
lnd v0.10.0-beta.rc5
lnd v0.10.0-beta.rc4
lnd v0.10.0-beta.rc4
lnd v0.10.0-beta.rc2
lnd v0.10.0-beta.rc2
v0.10.0-beta.rc1
lnd v0.10.0-beta.rc1
lnd v0.9.2-beta
This marks the second minor release in the v0.9.0 series. This release fixes a single bug that affects 32-bit ARM machines. If you run lnd on any other architecture, then you can safely skip this release, and get ready for our upcoming v0.10 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 https://keybase.io/roasbeef/pgp_keys.asc | gpg --import
Once you have the required PGP keys, you can verify the release (assuming manifest-v0.9.2-beta.txt and manifest-v0.9.2-beta.txt.sig are in the current directory) with:
gpg --verify manifest-v0.9.2-beta.txt.sig
You should see the following if the verification was successful:
gpg: assuming signed data in 'manifest-v0.9.2-beta.txt'
gpg: Signature made Thu Mar 12 17:55:15 2020 PDT
gpg: using RSA key 4AB7F8DA6FAEBB3B70B1F903BC13F65E2DC84465
gpg: Good signature from "Olaoluwa Osuntokun <[email protected]>" [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.7, 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.9.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.9.2-beta.tar.gz are in the current directory, follow these steps:
tar -xvzf vendor.tar.gz
tar -xvzf lnd-source-v0.9.2-beta.tar.gz
GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.9.2-beta" ./cmd/lnd
GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.9.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
Bug Fixes
In this release, we update to a new version of x/crypto that drops broken ARM assembly that can cause a segfault in systems like Raspberry Pis. The broken assembly was removed in this commit to the runtime: golang/go@8b77410.
The full list of changes since v0.9.1-beta can be found here:
Contributors (Alphabetical Order)
Olaoluwa Osuntokun