PackageTrack
Sign in Get early access

github.com/lightningnetwork/lnd

v0.0.2 #483 most downloaded on Go modules lightningnetwork/lnd

What this package is like to depend on

Last release 3 days ago

20 Aug 2026

Ships on a steady schedule

a new release about every 8 days

No release notes found

nothing matched a version

Nothing withdrawn

no release was ever pulled

11 years old

15067 releases · first in 2016

564 releases in the last 12 months

see the full history below

Release timeline

15067 releases · Nov 2023 to Aug 2026
2024 2025 2026
Release Pre-release 13867 older releases not drawn

Releases

latest 60 of 15067
  1. v0.21.2-beta.rc1 07 Aug 2026 pre-release
    Release notes

    Database Migrations

    This release introduces no new database migrations, but includes two important fixes to existing migration paths:

    • The KV-to-SQL payment migration now handles historical routes containing an orphaned blinded total amount, preventing affected nodes from failing during startup.

    • The channeldb migration recovery now detects databases missing the persisted version key and safely runs the previously skipped v0.21 waiting-proof migration.

    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.21.2-beta.rc1.sig and manifest-v0.21.2-beta.rc1.txt are in the current directory) with:

    gpg --verify manifest-roasbeef-v0.21.2-beta.rc1.sig manifest-v0.21.2-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.21.2-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.21.2-beta.rc1.sig.ots -f manifest-roasbeef-v0.21.2-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.26.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.21.2-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.21.2-beta.rc1 /verify-install.sh v0.21.2-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.21.2-beta.rc1.tar.gz are in the current directory, follow these steps:

    tar -xvzf lnd-source-v0.21.2-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.21.2-beta.rc1" ./cmd/lnd
go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.21.2-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

    https://github.com/lightningnetwork/lnd/blob/master/docs/release-notes/release-notes-0.21.2.md

    Contributors (Alphabetical Order)

    • bitromortac
    • Jared Tobin
    • Olaoluwa Osuntokun
    • Ziggie
    Open source →
  2. v0.21.2-beta 12 Aug 2026 pre-release
    Release notes

    Database Migrations

    This release introduces no new database migrations, but includes two important fixes to existing migration paths:

    • The #10982 now handles historical routes containing an orphaned blinded total amount, preventing affected nodes from failing during startup.

    • The #10985 now detects databases missing the persisted version key and safely runs the previously skipped v0.21 waiting-proof migration.

    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.21.2-beta.sig and manifest-v0.21.2-beta.txt are in the current directory) with:

    gpg --verify manifest-roasbeef-v0.21.2-beta.sig manifest-v0.21.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.21.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.21.2-beta.sig.ots -f manifest-roasbeef-v0.21.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.26.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.21.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.21.2-beta /verify-install.sh v0.21.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.21.2-beta.tar.gz are in the current directory, follow these steps:

    tar -xvzf lnd-source-v0.21.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.21.2-beta" ./cmd/lnd
go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.21.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

    https://github.com/lightningnetwork/lnd/blob/master/docs/release-notes/release-notes-0.21.2.md

    Contributors (Alphabetical Order)

    • bitromortac
    • Jared Tobin
    • Olaoluwa Osuntokun
    • Ziggie
    Open source →
  3. v0.21.1-beta 26 Jun 2026 pre-release
    Release notes

    Database Migrations

    There are no migrations in this 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://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.21.1-beta.sig and manifest-v0.21.1-beta.txt are in the current directory) with:

    gpg --verify manifest-roasbeef-v0.21.1-beta.sig manifest-v0.21.1-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.21.1-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.21.1-beta.sig.ots -f manifest-roasbeef-v0.21.1-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.26.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.21.1-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.21.1-beta /verify-install.sh v0.21.1-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.21.1-beta.tar.gz are in the current directory, follow these steps:

    tar -xvzf lnd-source-v0.21.1-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.21.1-beta" ./cmd/lnd
go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.21.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:

    make release sys="linux-arm64 darwin-amd64"

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

    Release Notes

    https://github.com/lightningnetwork/lnd/blob/master/docs/release-notes/release-notes-0.21.1.md

    Contributors (Alphabetical Order)

    • Erick Cestari
    • Ziggie
    Open source →
  4. v0.21.0-beta.rc3 28 May 2026 pre-release

    Nothing published for this version

  5. v0.21.0-beta.rc2.0.20260820190730-90ea05d5a7f9 20 Aug 2026 pre-release

    Nothing published for this version

  6. v0.21.0-beta.rc2.0.20260819140541-eac5a5b8fbd5 19 Aug 2026 pre-release

    Nothing published for this version

  7. v0.21.0-beta.rc2.0.20260818235104-155683c41e0c 18 Aug 2026 pre-release

    Nothing published for this version

  8. v0.21.0-beta.rc2.0.20260818163642-ae9e86a50b4e 18 Aug 2026 pre-release

    Nothing published for this version

  9. v0.21.0-beta.rc2.0.20260818012441-d157ed3e86de 18 Aug 2026 pre-release

    Nothing published for this version

  10. v0.21.0-beta.rc2.0.20260817104937-47c70ae62fa2 17 Aug 2026 pre-release

    Nothing published for this version

  11. v0.21.0-beta.rc2.0.20260817103841-b309be586718 17 Aug 2026 pre-release

    Nothing published for this version

  12. v0.21.0-beta.rc2.0.20260815150944-4045fc9f70ec 15 Aug 2026 pre-release

    Nothing published for this version

  13. v0.21.0-beta.rc2.0.20260814234958-cfde18d9822a 14 Aug 2026 pre-release

    Nothing published for this version

  14. v0.21.0-beta.rc2.0.20260814192939-00d006f83475 14 Aug 2026 pre-release

    Nothing published for this version

  15. v0.21.0-beta.rc2.0.20260814114107-1be0e4111ff7 14 Aug 2026 pre-release

    Nothing published for this version

  16. v0.21.0-beta.rc2.0.20260813015540-8ea98fd52268 13 Aug 2026 pre-release

    Nothing published for this version

  17. v0.21.0-beta.rc2.0.20260811052332-8464116a051a 11 Aug 2026 pre-release

    Nothing published for this version

  18. v0.21.0-beta.rc2.0.20260807191813-d932f4867822 07 Aug 2026 pre-release

    Nothing published for this version

  19. v0.21.0-beta.rc2.0.20260807043057-7f56541dc9fb 07 Aug 2026 pre-release

    Nothing published for this version

  20. v0.21.0-beta.rc2.0.20260806161620-99457a272c7b 06 Aug 2026 pre-release

    Nothing published for this version

  21. v0.21.0-beta.rc2.0.20260806111451-18f930a5f20e 06 Aug 2026 pre-release

    Nothing published for this version

  22. v0.21.0-beta.rc2.0.20260806012518-f4ae56561974 06 Aug 2026 pre-release

    Nothing published for this version

  23. v0.21.0-beta.rc2.0.20260805181314-61f3b5a74fda 05 Aug 2026 pre-release

    Nothing published for this version

  24. v0.21.0-beta.rc2.0.20260803222044-afdfd1948424 03 Aug 2026 pre-release

    Nothing published for this version

  25. v0.21.0-beta.rc2.0.20260730123059-f4a444184dd1 30 Jul 2026 pre-release

    Nothing published for this version

  26. v0.21.0-beta.rc2.0.20260728164620-530dca19b313 28 Jul 2026 pre-release

    Nothing published for this version

  27. v0.21.0-beta.rc2.0.20260724171613-2c3e6ffccebc 24 Jul 2026 pre-release

    Nothing published for this version

  28. v0.21.0-beta.rc2.0.20260723172338-dcacdfe0e1c5 23 Jul 2026 pre-release

    Nothing published for this version

  29. v0.21.0-beta.rc2.0.20260722204628-d7d2aad11d61 22 Jul 2026 pre-release

    Nothing published for this version

  30. v0.21.0-beta.rc2.0.20260722165357-0f4b9c9a1892 22 Jul 2026 pre-release

    Nothing published for this version

  31. v0.21.0-beta.rc2.0.20260718015747-046356759a3b 18 Jul 2026 pre-release

    Nothing published for this version

  32. v0.21.0-beta.rc2.0.20260717013942-f02cf4c470c9 17 Jul 2026 pre-release

    Nothing published for this version

  33. v0.21.0-beta.rc2.0.20260714190524-6f65644448ad 14 Jul 2026 pre-release

    Nothing published for this version

  34. v0.21.0-beta.rc2.0.20260713143107-02f4116926e2 13 Jul 2026 pre-release

    Nothing published for this version

  35. v0.21.0-beta.rc2.0.20260710162359-404f2c27abbb 10 Jul 2026 pre-release

    Nothing published for this version

  36. v0.21.0-beta.rc2.0.20260709123604-e9a8b3f9c8f9 09 Jul 2026 pre-release

    Nothing published for this version

  37. v0.21.0-beta.rc2.0.20260707214707-31168557c3a8 07 Jul 2026 pre-release

    Nothing published for this version

  38. v0.21.0-beta.rc2.0.20260707020939-530301c19bc3 07 Jul 2026 pre-release

    Nothing published for this version

  39. v0.21.0-beta.rc2.0.20260630214209-40c64f9db30d 30 Jun 2026 pre-release

    Nothing published for this version

  40. v0.21.0-beta.rc2.0.20260630174553-c4a67b68b735 30 Jun 2026 pre-release

    Nothing published for this version

  41. v0.21.0-beta.rc2.0.20260630132723-d4f875218297 30 Jun 2026 pre-release

    Nothing published for this version

  42. v0.21.0-beta.rc2.0.20260626165931-cbe77749cde7 26 Jun 2026 pre-release

    Nothing published for this version

  43. v0.21.0-beta.rc2.0.20260626085929-0cad457be1b3 26 Jun 2026 pre-release

    Nothing published for this version

  44. v0.21.0-beta.rc2.0.20260626015746-5e1e827f01da 26 Jun 2026 pre-release

    Nothing published for this version

  45. v0.21.0-beta.rc2.0.20260625024837-0dbe2b10291b 25 Jun 2026 pre-release

    Nothing published for this version

  46. v0.21.0-beta.rc2.0.20260624222005-cea51aa07506 24 Jun 2026 pre-release

    Nothing published for this version

  47. v0.21.0-beta.rc2.0.20260624152800-c6768ca4ff10 24 Jun 2026 pre-release

    Nothing published for this version

  48. v0.21.0-beta.rc2.0.20260623112816-b927e03a2086 23 Jun 2026 pre-release

    Nothing published for this version

  49. v0.21.0-beta.rc2.0.20260622234332-1e8b76a579f2 22 Jun 2026 pre-release

    Nothing published for this version

  50. v0.21.0-beta.rc2.0.20260619050626-2e6e61d30803 19 Jun 2026 pre-release

    Nothing published for this version

  51. v0.21.0-beta.rc2.0.20260618185803-918b94d0d6c7 18 Jun 2026 pre-release

    Nothing published for this version

  52. v0.21.0-beta.rc2.0.20260617133112-f771e141912e 17 Jun 2026 pre-release

    Nothing published for this version

  53. v0.21.0-beta.rc2.0.20260616011031-1f23a119d091 16 Jun 2026 pre-release

    Nothing published for this version

  54. v0.21.0-beta.rc2.0.20260615041941-0b3e3aefe3f5 15 Jun 2026 pre-release

    Nothing published for this version

  55. v0.21.0-beta.rc2.0.20260615022959-a067468f0f45 15 Jun 2026 pre-release

    Nothing published for this version

  56. v0.21.0-beta.rc2.0.20260610231426-1a6ecebcbf49 10 Jun 2026 pre-release

    Nothing published for this version

  57. v0.21.0-beta.rc2.0.20260610053945-afeb9e121111 10 Jun 2026 pre-release

    Nothing published for this version

  58. v0.21.0-beta.rc2.0.20260609161550-036d1e0a5f0f 09 Jun 2026 pre-release

    Nothing published for this version

  59. v0.21.0-beta.rc2.0.20260609013118-1d4c753bf54d 09 Jun 2026 pre-release

    Nothing published for this version

  60. v0.21.0-beta.rc2.0.20260606181154-6b27461f001a 06 Jun 2026 pre-release

    Nothing published for this version

Every package, every release, already written down.

The archive is open and free. Watching your own project is what we are building next.

Browse the archive