Sourced from github.com/lightningnetwork/lnd's releases.
lnd v0.17.0-beta
Database Migrations
There is a single database migration in this release. This migration deletes some space on disk that previously stored the last sweep transaction in the sweeper.
Verifying the Release
In order to verify the release, you'll need to have
gpgorgpg2installed 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 --importOnce you have the required PGP keys, you can verify the release (assuming
manifest-roasbeef-v0.17.0-beta.sigandmanifest-v0.17.0-beta.txtare in the current directory) with:gpg --verify manifest-roasbeef-v0.17.0-beta.sig manifest-v0.17.0-beta.txtYou should see the following if the verification was successful:
gpg: Signature made Tue Oct 3 11:03:53 2023 PDT gpg: using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306 gpg: Good signature from "Olaoluwa Osuntokun <laolu32@gmail.com>" [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
sha256hash of the archive withshasum -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.17.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.17.0-beta.sig.ots -f manifest-roasbeef-v0.17.0-beta.sigAlternatively, the OpenTimestamps website can be used to verify timestamps if one doesn't have a
bitcoindinstance 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.21.0, 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_etcdandkvdb_sqlite. Note that these are already included in the release script, so they do not need to be provided.The
make releasecommand 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, thenmake release sys=<OS-ARCH> tag=<tag>can be used.
... (truncated)
2fb150c
build: bump version to v0.17.0caa9bf9
Merge pull request #8043
from Roasbeef/0-17-rc64e6bb71
build: bump version to v0.17.0 rc6bb7a257
Merge pull request #8037
from yyforyongyu/fix-weight-calcedeb0d7
Merge pull request #8041
from Roasbeef/background-peer-prune5225189
lnwallet+rpcserver: fix weight calculation for taproot channels62d240b
itest: add testSendDirectPaymenteae9dd0
peer: launch persistent peer pruning in background goroutine1ebfe95
Merge pull request #8035
from Roasbeef/0-17-rc5f63a2b9
build: bump version to v0.17.0 rc5