You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a minor release that contains mainly bug fixes, and contains no new database migrations.
This release fixes a series of bugs related to fee estimation with taproot outputs/inputs, a bug fix to ensure new channels are always properly announced, and fixes an edge case related to zero conf channels.
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:
Once you have the required PGP keys, you can verify the release (assuming manifest-roasbeef-v0.15.3-beta.sig and manifest-v0.15.3-beta.txt are in the current directory) with:
You should see the following if the verification was successful:
gpg: Signature made Mon Oct 17 15:18:02 2022 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.15.3-beta.txt.asc.ots.
Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands:
Alternatively, the open timestamps 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.18.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, and kvdb_etcd. 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.15.3-beta
gpg: Signature made Mon 17 Oct 2022 05:55:01 PM UTC using RSA key ID 9B280306
gpg: Good signature from "Olaoluwa Osuntokun <[email protected]>"
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.15.3-beta /verify-install.sh v0.15.3-beta
$ OK=$?
$ if [ "$OK"-ne"0" ];thenecho"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.15.3-beta.tar.gz are in the current directory, follow these steps:
tar -xvzf vendor.tar.gz
tar -xvzf lnd-source-v0.15.3-beta.tar.gz
GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.15.3-beta" ./cmd/lnd
GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.15.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.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
This is a minor release that contains mainly bug fixes, and contains no new database migrations.
This release fixes a series of bugs related to fee estimation with taproot outputs/inputs, a bug fix to ensure new channels are always properly announced, and fixes an edge case related to zero conf channels.
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.15.3-beta.sigandmanifest-v0.15.3-beta.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.15.3-beta.txt.asc.ots.Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands:
Alternatively, the open timestamps 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.18.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, andkvdb_etcd. 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.15.3-beta.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/v0-15-3-branch/docs/release-notes/release-notes-0.15.3.md
Contributors (Alphabetical Order)
This discussion was created from the release lnd v0.15.3-beta.
Beta Was this translation helpful? Give feedback.
All reactions