lnd 0.19.0-beta.rc3 #9760
guggero
announced in
Announcements
lnd 0.19.0-beta.rc3
#9760
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Database Migrations
There are mandatory database migrations in this version. Downgrading to previous versions will not be possible.
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:Once you have the required PGP keys, you can verify the release (assuming
manifest-roasbeef-v0.19.0-beta.rc3.sigandmanifest-v0.19.0-beta.rc3.txtare in the current directory) with:You should see the following if the verification was successful:
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.19.0-beta.rc3.txt.asc.ots.Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands:
Alternatively, 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.23.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_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.Finally, you can also verify the tag itself with the following command:
Verifying the Docker Images
To verify the
lndandlnclibinaries 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):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.gzandlnd-source-v0.19.0-beta.rc3.tar.gzare in the current directory, follow these steps:The
-mod=vendorflag tells thego buildcommand 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.shscript to bundle a release for a specific system like so:⚡️⚡️⚡️ OK, now to the rest of the release notes! ⚡️⚡️⚡️
Release Notes
https://github.com/lightningnetwork/lnd/blob/master/docs/release-notes/release-notes-0.19.0.md
Contributors (Alphabetical Order)
This discussion was created from the release lnd 0.19.0-beta.rc3.
Beta Was this translation helpful? Give feedback.
All reactions