Releases: lightningnetwork/lnd
lnd v0.20.0-beta
Roasbeef
Olaoluwa Osuntokun
Database Migrations
- SQL migration of the graph store: This migrates the graph store from the KV format to native SQL. This migration will only run if the
--db.use-native-sqlflag is set along with the--db.backendoption set tosqliteorpostgres. Users may opt out of this migration by setting the--db.skip-native-sql-migrationflag.
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://raw.githubusercontent.com/lightningnetwork/lnd/master/scripts/keys/roasbeef.asc | gpg --import
Once you have the required PGP keys, you can verify the release (assuming manifest-roasbeef-v0.20.0-beta.sig and manifest-v0.20.0-beta.txt are in the current directory) with:
gpg --verify manifest-roasbeef-v0.20.0-beta.sig manifest-v0.20.0-beta.txt
You should see the following if the verification was successful:
gpg: Signature made Wed Nov 12 17:00:13 2025 PST
gpg: using EDDSA key 296212681AADF05656A2CDEE90525F7DEEE0AD86
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 Timestamp
From this new version onwards, in addition time-stamping the git tag with OpenTimestamps, we'll also now timestamp the manifest file along with its signature. Two new files are now included along with the rest of our release artifacts: manifest-roasbeef-v0.20.0-beta.txt.asc.ots.
Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands:
ots verify manifest-roasbeef-v0.20.0-beta.sig.ots -f manifest-roasbeef-v0.20.0-beta.sig
Alternatively, the OpenTimestamps website can be used to verify timestamps if one doesn't have a bitcoind instance accessible locally.
These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.
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.25.3, which is required by verifiers to arrive at the same ones.
They include the following build tags: autopilotrpc, signrpc, walletrpc, chainrpc, invoicesrpc, neutrinorpc, routerrpc, watchtowerrpc, monitoring, peersrpc, kvdb_postrgres, kvdb_etcd and kvdb_sqlite. 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.20.0-beta
gpg: Signature made Tue Nov 11 14:38:36 2025 PST
gpg: using EDDSA key 296212681AADF05656A2CDEE90525F7DEEE0AD86
gpg: Good signature from "Olaoluwa Osuntokun <[email protected]>" [ultimate]
Verifying the Docker Images
To verify the lnd and lncli binaries inside the docker images against the signed, reproducible release binaries, there is a verification script in the image that can be called (before starting the container for example):
$ docker run --rm --entrypoint="" lightninglabs/lnd:v0.20.0-beta /verify-install.sh v0.20.0-beta
$ OK=$?
$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done
$ docker run lightninglabs/lnd [command-line options]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.20.0-beta.tar.gz are in the current directory, follow these steps:
tar -xvzf lnd-source-v0.20.0-beta.tar.gz
mv vendor.tar.gz lnd-source/
cd lnd-source
tar -xvzf vendor.tar.gz
go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.20.0-beta" ./cmd/lnd
go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.20.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
See the release notes for details on the changes in this release.
Contributors (Alphabetical Order)
- ⚡️2FakTor⚡️
- Abdullahi Yunus
- Alex Pilon
- András Bánki-Horváth
- bitromortac
- Boris Nagaev
- Calvin Zachman
- djkazic
- Elle Mouton
- Erick Cestari
- ffranr
- George Tsagkarelis
- Gustavo Stingelin Cardoso Filho
- hexcow
- Jared Tobin
- Keagan McClelland
- Mohamed Awnallah
- MPins
- Nishant Bansal
- Olaoluwa Osuntokun
- Oliver Gugger
- Shivam Chawla
- Slyghtning
- sputn1ck
- Torkel Rogstad
- Viktor Torstensson
- Yong Yu
- ziggie
- ZZiigguurraatt
lnd v0.20.0-beta.rc4
Roasbeef
Olaoluwa Osuntokun
Database Migrations
- SQL migration of the graph store: This migrates the graph store from the KV format to native SQL. This migration will only run if the
--db.use-native-sqlflag is set along with the--db.backendoption set tosqliteorpostgres. Users may opt out of this migration by setting the--db.skip-native-sql-migrationflag.
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://raw.githubusercontent.com/lightningnetwork/lnd/master/scripts/keys/roasbeef.asc | gpg --import
Once you have the required PGP keys, you can verify the release (assuming manifest-roasbeef-v0.20.0-beta.rc4.sig and manifest-v0.20.0-beta.rc4.txt are in the current directory) with:
gpg --verify manifest-roasbeef-v0.20.0-beta.rc4.sig manifest-v0.20.0-beta.rc4.txt
You should see the following if the verification was successful:
gpg: Signature made Wed Sep 30 17:35:20 2020 PDT
gpg: using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306
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 Timestamp
From this new version onwards, in addition time-stamping the git tag with OpenTimestamps, we'll also now timestamp the manifest file along with its signature. Two new files are now included along with the rest of our release artifacts: manifest-roasbeef-v0.20.0-beta.rc4.txt.asc.ots.
Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands:
ots verify manifest-roasbeef-v0.20.0-beta.rc4.sig.ots -f manifest-roasbeef-v0.20.0-beta.rc4.sig
Alternatively, the OpenTimestamps website can be used to verify timestamps if one doesn't have a bitcoind instance accessible locally.
These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.
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.25.3, which is required by verifiers to arrive at the same ones.
They include the following build tags: autopilotrpc, signrpc, walletrpc, chainrpc, invoicesrpc, neutrinorpc, routerrpc, watchtowerrpc, monitoring, peersrpc, kvdb_postrgres, kvdb_etcd and kvdb_sqlite. 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.20.0-beta.rc4
gpg: Signature made Tue Sep 15 18:55:00 2020 PDT
gpg: using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306
gpg: Good signature from "Olaoluwa Osuntokun <[email protected]>" [ultimate]
Verifying the Docker Images
To verify the lnd and lncli binaries inside the docker images against the signed, reproducible release binaries, there is a verification script in the image that can be called (before starting the container for example):
$ docker run --rm --entrypoint="" lightninglabs/lnd:v0.20.0-beta.rc4 /verify-install.sh v0.20.0-beta.rc4
$ OK=$?
$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done
$ docker run lightninglabs/lnd [command-line options]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.20.0-beta.rc4.tar.gz are in the current directory, follow these steps:
tar -xvzf lnd-source-v0.20.0-beta.rc4.tar.gz
mv vendor.tar.gz lnd-source/
cd lnd-source
tar -xvzf vendor.tar.gz
go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.20.0-beta.rc4" ./cmd/lnd
go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.20.0-beta.rc4" ./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
See the release notes for details on the changes in this release.
Contributors (Alphabetical Order)
- ⚡️2FakTor⚡️
- Abdullahi Yunus
- Alex Pilon
- András Bánki-Horváth
- bitromortac
- Boris Nagaev
- Calvin Zachman
- djkazic
- Elle Mouton
- Erick Cestari
- ffranr
- George Tsagkarelis
- Gustavo Stingelin Cardoso Filho
- hexcow
- Jared Tobin
- Keagan McClelland
- Mohamed Awnallah
- MPins
- Nishant Bansal
- Olaoluwa Osuntokun
- Oliver Gugger
- Shivam Chawla
- Slyghtning
- sputn1ck
- Torkel Rogstad
- Viktor Torstensson
- Yong Yu
- ziggie
- ZZiigguurraatt
lnd v0.20.0-beta.rc3
Roasbeef
Olaoluwa Osuntokun
Database Migrations
TODO
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://raw.githubusercontent.com/lightningnetwork/lnd/master/scripts/keys/roasbeef.asc | gpg --import
Once you have the required PGP keys, you can verify the release (assuming manifest-roasbeef-v0.20.0-beta.rc3.sig and manifest-v0.20.0-beta.rc3.txt are in the current directory) with:
gpg --verify manifest-roasbeef-v0.20.0-beta.rc3.sig manifest-v0.20.0-beta.rc3.txt
You should see the following if the verification was successful:
gpg: Signature made Wed Sep 30 17:35:20 2020 PDT
gpg: using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306
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 Timestamp
From this new version onwards, in addition time-stamping the git tag with OpenTimestamps, we'll also now timestamp the manifest file along with its signature. Two new files are now included along with the rest of our release artifacts: manifest-roasbeef-v0.20.0-beta.rc3.txt.asc.ots.
Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands:
ots verify manifest-roasbeef-v0.20.0-beta.rc3.sig.ots -f manifest-roasbeef-v0.20.0-beta.rc3.sig
Alternatively, the OpenTimestamps website can be used to verify timestamps if one doesn't have a bitcoind instance accessible locally.
These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.
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.25.3, which is required by verifiers to arrive at the same ones.
They include the following build tags: autopilotrpc, signrpc, walletrpc, chainrpc, invoicesrpc, neutrinorpc, routerrpc, watchtowerrpc, monitoring, peersrpc, kvdb_postrgres, kvdb_etcd and kvdb_sqlite. 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.20.0-beta.rc3
gpg: Signature made Tue Sep 15 18:55:00 2020 PDT
gpg: using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306
gpg: Good signature from "Olaoluwa Osuntokun <[email protected]>" [ultimate]
Verifying the Docker Images
To verify the lnd and lncli binaries inside the docker images against the signed, reproducible release binaries, there is a verification script in the image that can be called (before starting the container for example):
$ docker run --rm --entrypoint="" lightninglabs/lnd:v0.20.0-beta.rc3 /verify-install.sh v0.20.0-beta.rc3
$ OK=$?
$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done
$ docker run lightninglabs/lnd [command-line options]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.20.0-beta.rc3.tar.gz are in the current directory, follow these steps:
tar -xvzf lnd-source-v0.20.0-beta.rc3.tar.gz
mv vendor.tar.gz lnd-source/
cd lnd-source
tar -xvzf vendor.tar.gz
go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.20.0-beta.rc3" ./cmd/lnd
go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.20.0-beta.rc3" ./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
TODO
Contributors (Alphabetical Order)
TODO
lnd v0.20.0-beta.rc2
Roasbeef
Olaoluwa Osuntokun
Database Migrations
This release includes the following database migration:
- SQL migration of the graph store: This migrates the graph store from the KV format to native SQL. This migration will only run if the
--db.use-native-sqlflag is set along with the--db.backendoption set tosqliteorpostgres. Users may opt out of this migration by setting the--db.skip-native-sql-migrationflag.
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://raw.githubusercontent.com/lightningnetwork/lnd/master/scripts/keys/roasbeef.asc | gpg --import
Once you have the required PGP keys, you can verify the release (assuming manifest-roasbeef-v0.20.0-beta.rc2.sig and manifest-v0.20.0-beta.rc2.txt are in the current directory) with:
gpg --verify manifest-roasbeef-v0.20.0-beta.rc2.sig manifest-v0.20.0-beta.rc2.txt
You should see the following if the verification was successful:
gpg: Signature made Wed Sep 30 17:35:20 2020 PDT
gpg: using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306
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 Timestamp
From this new version onwards, in addition time-stamping the git tag with OpenTimestamps, we'll also now timestamp the manifest file along with its signature. Two new files are now included along with the rest of our release artifacts: manifest-roasbeef-v0.20.0-beta.rc2.txt.asc.ots.
Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands:
ots verify manifest-roasbeef-v0.20.0-beta.rc2.sig.ots -f manifest-roasbeef-v0.20.0-beta.rc2.sig
Alternatively, the OpenTimestamps website can be used to verify timestamps if one doesn't have a bitcoind instance accessible locally.
These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.
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.25.2, which is required by verifiers to arrive at the same ones.
They include the following build tags: autopilotrpc, signrpc, walletrpc, chainrpc, invoicesrpc, neutrinorpc, routerrpc, watchtowerrpc, monitoring, peersrpc, kvdb_postrgres, kvdb_etcd and kvdb_sqlite. 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.20.0-beta.rc2
gpg: Signature made Tue Sep 15 18:55:00 2020 PDT
gpg: using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306
gpg: Good signature from "Olaoluwa Osuntokun <[email protected]>" [ultimate]
Verifying the Docker Images
To verify the lnd and lncli binaries inside the docker images against the signed, reproducible release binaries, there is a verification script in the image that can be called (before starting the container for example):
$ docker run --rm --entrypoint="" lightninglabs/lnd:v0.20.0-beta.rc2 /verify-install.sh v0.20.0-beta.rc2
$ OK=$?
$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done
$ docker run lightninglabs/lnd [command-line options]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.20.0-beta.rc2.tar.gz are in the current directory, follow these steps:
tar -xvzf lnd-source-v0.20.0-beta.rc2.tar.gz
mv vendor.tar.gz lnd-source/
cd lnd-source
tar -xvzf vendor.tar.gz
go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.20.0-beta.rc2" ./cmd/lnd
go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.20.0-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
See the release notes for details on the changes in this release.
Contributors (Alphabetical Order)
- ⚡️2FakTor⚡️
- Abdullahi Yunus
- Alex Pilon
- András Bánki-Horváth
- bitromortac
- Boris Nagaev
- Calvin Zachman
- djkazic
- Elle Mouton
- Erick Cestari
- ffranr
- George Tsagkarelis
- Gustavo Stingelin Cardoso Filho
- hexcow
- Jared Tobin
- Keagan McClelland
- Mohamed Awnallah
- MPins
- Nishant Bansal
- Olaoluwa Osuntokun
- Oliver Gugger
- Shivam Chawla
- Slyghtning
- sputn1ck
- Torkel Rogstad
- Viktor Torstensson
- Yong Yu
- ziggie
- ZZiigguurraatt
lnd v0.20.0-beta.rc1
Roasbeef
Olaoluwa Osuntokun
Database Migrations
This release includes the following database migration:
- SQL migration of the graph store: This migrates the graph store from the KV format to native SQL. This migration will only run if the
--db.use-native-sqlflag is set along with the--db.backendoption set tosqliteorpostgres. Users may opt out of this migration by setting the--db.skip-native-sql-migrationflag.
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://raw.githubusercontent.com/lightningnetwork/lnd/master/scripts/keys/roasbeef.asc | gpg --import
Once you have the required PGP keys, you can verify the release (assuming manifest-roasbeef-v0.20.0-beta.rc1.sig and manifest-v0.20.0-beta.rc1.txt are in the current directory) with:
gpg --verify manifest-roasbeef-v0.20.0-beta.rc1.sig manifest-v0.20.0-beta.rc1.txt
You should see the following if the verification was successful:
gpg: Signature made Thu Oct 2 11:16:16 2025 PDT
gpg: using EDDSA key 296212681AADF05656A2CDEE90525F7DEEE0AD86
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 Timestamp
From this new version onwards, in addition time-stamping the git tag with OpenTimestamps, we'll also now timestamp the manifest file along with its signature. Two new files are now included along with the rest of our release artifacts: manifest-roasbeef-v0.20.0-beta.rc1.txt.asc.ots.
Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands:
ots verify manifest-roasbeef-v0.20.0-beta.rc1.sig.ots -f manifest-roasbeef-v0.20.0-beta.rc1.sig
Alternatively, the OpenTimestamps website can be used to verify timestamps if one doesn't have a bitcoind instance accessible locally.
These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.
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.24.6, which is required by verifiers to arrive at the same ones.
They include the following build tags: autopilotrpc, signrpc, walletrpc, chainrpc, invoicesrpc, neutrinorpc, routerrpc, watchtowerrpc, monitoring, peersrpc, kvdb_postrgres, kvdb_etcd and kvdb_sqlite. 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.20.0-beta.rc1
gpg: Signature made Mon Sep 29 20:35:01 2025 PDT
gpg: using EDDSA key 296212681AADF05656A2CDEE90525F7DEEE0AD86
gpg: Good signature from "Olaoluwa Osuntokun <[email protected]>" [ultimate]
Verifying the Docker Images
To verify the lnd and lncli binaries inside the docker images against the signed, reproducible release binaries, there is a verification script in the image that can be called (before starting the container for example):
$ docker run --rm --entrypoint="" lightninglabs/lnd:v0.20.0-beta.rc1 /verify-install.sh v0.20.0-beta.rc1
$ OK=$?
$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done
$ docker run lightninglabs/lnd [command-line options]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.20.0-beta.rc1.tar.gz are in the current directory, follow these steps:
tar -xvzf lnd-source-v0.20.0-beta.rc1.tar.gz
mv vendor.tar.gz lnd-source/
cd lnd-source
tar -xvzf vendor.tar.gz
go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.20.0-beta.rc1" ./cmd/lnd
go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.20.0-beta.rc1" ./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
See the release notes for details on the changes in this release.
Contributors (Alphabetical Order)
- ⚡️2FakTor⚡️
- Abdullahi Yunus
- Alex Pilon
- András Bánki-Horváth
- bitromortac
- Boris Nagaev
- Calvin Zachman
- djkazic
- Elle Mouton
- Erick Cestari
- ffranr
- George Tsagkarelis
- Gustavo Stingelin Cardoso Filho
- hexcow
- Jared Tobin
- Keagan McClelland
- Mohamed Awnallah
- MPins
- Nishant Bansal
- Olaoluwa Osuntokun
- Oliver Gugger
- Shivam Chawla
- Slyghtning
- sputn1ck
- Torkel Rogstad
- Viktor Torstensson
- Yong Yu
- ziggie
- ZZiigguurraatt
lnd v0.19.3-beta
Roasbeef
Olaoluwa Osuntokun
This third minor release contains important bug fixes to improve p2p stability, a retry bug in path finding, and adds improved isolation to anchor sweeping on chain.
The Go version the release is built with has also been updated to fix a reported CVE related to SQL database handling.
Database Migrations
An optional migration introduced with v0.19.2-beta garbage collects the "decayed log database" also known as sphinxreplay.db which lowers disk and memory requirements for nodes significantly.
The migration is optional but turned on by default. If you encounter issues, you can opt-out of the migration by setting no-gc-decayed-log=true in the config.
This migration does not prevent downgrading to earlier v0.19.x-beta versions.
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://raw.githubusercontent.com/lightningnetwork/lnd/master/scripts/keys/roasbeef.asc | gpg --import
Once you have the required PGP keys, you can verify the release (assuming manifest-roasbeef-v0.19.3-beta.sig and manifest-v0.19.3-beta.txt are in the current directory) with:
gpg --verify manifest-roasbeef-v0.19.3-beta.sig manifest-v0.19.3-beta.txt
You should see the following if the verification was successful:
gpg: Signature made Wed Sep 30 17:35:20 2020 PDT
gpg: using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306
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 Timestamp
From this new version onwards, in addition time-stamping the git tag with OpenTimestamps, we'll also now timestamp the manifest file along with its signature. Two new files are now included along with the rest of our release artifacts: manifest-roasbeef-v0.19.3-beta.txt.asc.ots.
Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands:
ots verify manifest-roasbeef-v0.19.3-beta.sig.ots -f manifest-roasbeef-v0.19.3-beta.sig
Alternatively, the OpenTimestamps website can be used to verify timestamps if one doesn't have a bitcoind instance accessible locally.
These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.
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.23.12, which is required by verifiers to arrive at the same ones.
They include the following build tags: autopilotrpc, signrpc, walletrpc, chainrpc, invoicesrpc, neutrinorpc, routerrpc, watchtowerrpc, monitoring, peersrpc, kvdb_postrgres, kvdb_etcd and kvdb_sqlite. 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.19.3-beta
gpg: Signature made Tue Sep 15 18:55:00 2020 PDT
gpg: using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306
gpg: Good signature from "Olaoluwa Osuntokun <[email protected]>" [ultimate]
Verifying the Docker Images
To verify the lnd and lncli binaries inside the docker images against the signed, reproducible release binaries, there is a verification script in the image that can be called (before starting the container for example):
$ docker run --rm --entrypoint="" lightninglabs/lnd:v0.19.3-beta /verify-install.sh v0.19.3-beta
$ OK=$?
$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done
$ docker run lightninglabs/lnd [command-line options]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.19.3-beta.tar.gz are in the current directory, follow these steps:
tar -xvzf lnd-source-v0.19.3-beta.tar.gz
mv vendor.tar.gz lnd-source/
cd lnd-source
tar -xvzf vendor.tar.gz
go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.19.3-beta" ./cmd/lnd
go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.19.3-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
Contributors (Alphabetical Order)
- Elle Mouton
- George Tsagkarelis
- Olaoluwa Osuntokun
- Oliver Gugger
- Yong Yu
- Ziggie
lnd v0.19.3-beta.rc2
guggero
Oli
This third minor release contains important bug fixes.
Database Migrations
An optional migration introduced with v0.19.2-beta garbage collects the "decayed log database" also known as sphinxreplay.db which lowers disk and memory requirements for nodes significantly.
The migration is optional but turned on by default. If you encounter issues, you can opt-out of the migration by setting no-gc-decayed-log=true in the config.
This migration does not prevent downgrading to earlier v0.19.x-beta versions.
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://raw.githubusercontent.com/lightningnetwork/lnd/master/scripts/keys/roasbeef.asc | gpg --import
Once you have the required PGP keys, you can verify the release (assuming manifest-roasbeef-v0.19.3-beta.rc2.sig and manifest-v0.19.3-beta.rc2.txt are in the current directory) with:
gpg --verify manifest-roasbeef-v0.19.3-beta.rc2.sig manifest-v0.19.3-beta.rc2.txt
You should see the following if the verification was successful:
gpg: Signature made Wed Sep 30 17:35:20 2020 PDT
gpg: using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306
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 Timestamp
From this new version onwards, in addition time-stamping the git tag with OpenTimestamps, we'll also now timestamp the manifest file along with its signature. Two new files are now included along with the rest of our release artifacts: manifest-roasbeef-v0.19.3-beta.rc2.txt.asc.ots.
Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands:
ots verify manifest-roasbeef-v0.19.3-beta.rc2.sig.ots -f manifest-roasbeef-v0.19.3-beta.rc2.sig
Alternatively, the OpenTimestamps website can be used to verify timestamps if one doesn't have a bitcoind instance accessible locally.
These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.
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.23.12, which is required by verifiers to arrive at the same ones.
They include the following build tags: autopilotrpc, signrpc, walletrpc, chainrpc, invoicesrpc, neutrinorpc, routerrpc, watchtowerrpc, monitoring, peersrpc, kvdb_postrgres, kvdb_etcd and kvdb_sqlite. 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.19.3-beta.rc2
gpg: Signature made Tue Sep 15 18:55:00 2020 PDT
gpg: using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306
gpg: Good signature from "Olaoluwa Osuntokun <[email protected]>" [ultimate]
Verifying the Docker Images
To verify the lnd and lncli binaries inside the docker images against the signed, reproducible release binaries, there is a verification script in the image that can be called (before starting the container for example):
$ docker run --rm --entrypoint="" lightninglabs/lnd:v0.19.3-beta.rc2 /verify-install.sh v0.19.3-beta.rc2
$ OK=$?
$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done
$ docker run lightninglabs/lnd [command-line options]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.19.3-beta.rc2.tar.gz are in the current directory, follow these steps:
tar -xvzf lnd-source-v0.19.3-beta.rc2.tar.gz
mv vendor.tar.gz lnd-source/
cd lnd-source
tar -xvzf vendor.tar.gz
go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.19.3-beta.rc2" ./cmd/lnd
go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.19.3-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
Contributors (Alphabetical Order)
- Elle Mouton
- George Tsagkarelis
- Olaoluwa Osuntokun
- Oliver Gugger
- Yong Yu
- Ziggie
lnd v0.19.3-beta.rc1
guggero
Oli
This third minor release contains important bug fixes.
Database Migrations
An optional migration introduced with v0.19.2-beta garbage collects the "decayed log database" also known as sphinxreplay.db which lowers disk and memory requirements for nodes significantly.
The migration is optional but turned on by default. If you encounter issues, you can opt-out of the migration by setting no-gc-decayed-log=true in the config.
This migration does not prevent downgrading to earlier v0.19.x-beta versions.
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://raw.githubusercontent.com/lightningnetwork/lnd/master/scripts/keys/roasbeef.asc | gpg --import
Once you have the required PGP keys, you can verify the release (assuming manifest-roasbeef-v0.19.3-beta.rc1.sig and manifest-v0.19.3-beta.rc1.txt are in the current directory) with:
gpg --verify manifest-roasbeef-v0.19.3-beta.rc1.sig manifest-v0.19.3-beta.rc1.txt
You should see the following if the verification was successful:
gpg: Signature made Wed Sep 30 17:35:20 2020 PDT
gpg: using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306
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 Timestamp
From this new version onwards, in addition time-stamping the git tag with OpenTimestamps, we'll also now timestamp the manifest file along with its signature. Two new files are now included along with the rest of our release artifacts: manifest-roasbeef-v0.19.3-beta.rc1.txt.asc.ots.
Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands:
ots verify manifest-roasbeef-v0.19.3-beta.rc1.sig.ots -f manifest-roasbeef-v0.19.3-beta.rc1.sig
Alternatively, the OpenTimestamps website can be used to verify timestamps if one doesn't have a bitcoind instance accessible locally.
These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.
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.23.9, which is required by verifiers to arrive at the same ones.
They include the following build tags: autopilotrpc, signrpc, walletrpc, chainrpc, invoicesrpc, neutrinorpc, routerrpc, watchtowerrpc, monitoring, peersrpc, kvdb_postrgres, kvdb_etcd and kvdb_sqlite. 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.19.3-beta.rc1
gpg: Signature made Tue Sep 15 18:55:00 2020 PDT
gpg: using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306
gpg: Good signature from "Olaoluwa Osuntokun <[email protected]>" [ultimate]
Verifying the Docker Images
To verify the lnd and lncli binaries inside the docker images against the signed, reproducible release binaries, there is a verification script in the image that can be called (before starting the container for example):
$ docker run --rm --entrypoint="" lightninglabs/lnd:v0.19.3-beta.rc1 /verify-install.sh v0.19.3-beta.rc1
$ OK=$?
$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done
$ docker run lightninglabs/lnd [command-line options]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.19.3-beta.rc1.tar.gz are in the current directory, follow these steps:
tar -xvzf lnd-source-v0.19.3-beta.rc1.tar.gz
mv vendor.tar.gz lnd-source/
cd lnd-source
tar -xvzf vendor.tar.gz
go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.19.3-beta.rc1" ./cmd/lnd
go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.19.3-beta.rc1" ./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
Contributors (Alphabetical Order)
- Elle Mouton
- Olaoluwa Osuntokun
- Oliver Gugger
- Yong Yu
- Ziggie
lnd v0.19.2-beta
This second minor release contains important bug fixes and performance improvements.
Database Migrations
An optional migration garbage collects the "decayed log database" also known as sphinxreplay.db which lowers disk and memory requirements for nodes significantly.
The migration is optional but turned on by default. If you encounter issues, you can opt-out of the migration by setting no-gc-decayed-log=true in the config.
This migration does not prevent downgrading to earlier v0.19.x-beta versions.
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://raw.githubusercontent.com/lightningnetwork/lnd/master/scripts/keys/roasbeef.asc | gpg --import
Once you have the required PGP keys, you can verify the release (assuming manifest-roasbeef-v0.19.2-beta.sig and manifest-v0.19.2-beta.txt are in the current directory) with:
gpg --verify manifest-roasbeef-v0.19.2-beta.sig manifest-v0.19.2-beta.txt
You should see the following if the verification was successful:
gpg: Signature made Wed Sep 30 17:35:20 2020 PDT
gpg: using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306
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 Timestamp
From this new version onwards, in addition time-stamping the git tag with OpenTimestamps, we'll also now timestamp the manifest file along with its signature. Two new files are now included along with the rest of our release artifacts: manifest-roasbeef-v0.19.2-beta.txt.asc.ots.
Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands:
ots verify manifest-roasbeef-v0.19.2-beta.sig.ots -f manifest-roasbeef-v0.19.2-beta.sig
Alternatively, the OpenTimestamps website can be used to verify timestamps if one doesn't have a bitcoind instance accessible locally.
These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.
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.23.9, which is required by verifiers to arrive at the same ones.
They include the following build tags: autopilotrpc, signrpc, walletrpc, chainrpc, invoicesrpc, neutrinorpc, routerrpc, watchtowerrpc, monitoring, peersrpc, kvdb_postrgres, kvdb_etcd and kvdb_sqlite. 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.19.2-beta
gpg: Signature made Tue Sep 15 18:55:00 2020 PDT
gpg: using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306
gpg: Good signature from "Olaoluwa Osuntokun <[email protected]>" [ultimate]
Verifying the Docker Images
To verify the lnd and lncli binaries inside the docker images against the signed, reproducible release binaries, there is a verification script in the image that can be called (before starting the container for example):
$ docker run --rm --entrypoint="" lightninglabs/lnd:v0.19.2-beta /verify-install.sh v0.19.2-beta
$ OK=$?
$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done
$ docker run lightninglabs/lnd [command-line options]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.19.2-beta.tar.gz are in the current directory, follow these steps:
tar -xvzf lnd-source-v0.19.2-beta.tar.gz
mv vendor.tar.gz lnd-source/
cd lnd-source
tar -xvzf vendor.tar.gz
go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.19.2-beta" ./cmd/lnd
go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.19.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:
make release sys="linux-arm64 darwin-amd64"
⚡️⚡️⚡️ OK, now to the rest of the release notes! ⚡️⚡️⚡️
Release Notes
Contributors (Alphabetical Order)
- Abdulkbk
- Calvin Zachman
- djkazic
- Elle Mouton
- ffranr
- George Tsagkarelis
- hieblmi
- Oliver Gugger
- Olaoluwa Osuntokun
- Yong Yu
- Ziggie
lnd v0.19.2-beta.rc2
guggero
Oli
This second minor release contains important bug fixes and performance improvements.
Database Migrations
An optional migration garbage collects the "decayed log database" also known as sphinxreplay.db which lowers disk and memory requirements for nodes significantly.
The migration is optional but turned on by default. If you encounter issues, you can opt-out of the migration by setting no-gc-decayed-log=true in the config.
This migration does not prevent downgrading to earlier v0.19.x-beta versions.
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://raw.githubusercontent.com/lightningnetwork/lnd/master/scripts/keys/roasbeef.asc | gpg --import
Once you have the required PGP keys, you can verify the release (assuming manifest-roasbeef-v0.19.2-beta.rc2.sig and manifest-v0.19.2-beta.rc2.txt are in the current directory) with:
gpg --verify manifest-roasbeef-v0.19.2-beta.rc2.sig manifest-v0.19.2-beta.rc2.txt
You should see the following if the verification was successful:
gpg: Signature made Wed Sep 30 17:35:20 2020 PDT
gpg: using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306
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 Timestamp
From this new version onwards, in addition time-stamping the git tag with OpenTimestamps, we'll also now timestamp the manifest file along with its signature. Two new files are now included along with the rest of our release artifacts: manifest-roasbeef-v0.19.2-beta.rc2.txt.asc.ots.
Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands:
ots verify manifest-roasbeef-v0.19.2-beta.rc2.sig.ots -f manifest-roasbeef-v0.19.2-beta.rc2.sig
Alternatively, the OpenTimestamps website can be used to verify timestamps if one doesn't have a bitcoind instance accessible locally.
These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires.
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.23.9, which is required by verifiers to arrive at the same ones.
They include the following build tags: autopilotrpc, signrpc, walletrpc, chainrpc, invoicesrpc, neutrinorpc, routerrpc, watchtowerrpc, monitoring, peersrpc, kvdb_postrgres, kvdb_etcd and kvdb_sqlite. 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.19.2-beta.rc2
gpg: Signature made Tue Sep 15 18:55:00 2020 PDT
gpg: using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306
gpg: Good signature from "Olaoluwa Osuntokun <[email protected]>" [ultimate]
Verifying the Docker Images
To verify the lnd and lncli binaries inside the docker images against the signed, reproducible release binaries, there is a verification script in the image that can be called (before starting the container for example):
$ docker run --rm --entrypoint="" lightninglabs/lnd:v0.19.2-beta.rc2 /verify-install.sh v0.19.2-beta.rc2
$ OK=$?
$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; exit 1; done
$ docker run lightninglabs/lnd [command-line options]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.19.2-beta.rc2.tar.gz are in the current directory, follow these steps:
tar -xvzf lnd-source-v0.19.2-beta.rc2.tar.gz
mv vendor.tar.gz lnd-source/
cd lnd-source
tar -xvzf vendor.tar.gz
go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.19.2-beta.rc2" ./cmd/lnd
go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.19.2-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
Contributors (Alphabetical Order)
- Abdulkbk
- Calvin Zachman
- djkazic
- Elle Mouton
- ffranr
- George Tsagkarelis
- hieblmi
- Oliver Gugger
- Olaoluwa Osuntokun
- Yong Yu
- Ziggie