bulletin
Newsletters
- Bitcoin Optech: Bitcoin Optech Newsletter #225 (November 09, 2022)
- Bitcoin Optech: Bitcoin Optech Newsletter #224 (November 02, 2022)
Releases
project | release | date |
---|---|---|
lib-ledger-core | 4.4.1 What's Changed
Full Changelog: https://github.com/LedgerHQ/lib-ledger-core/compare/4.4.0...4.4.1 |
2022-11-10 |
btcd | v0.23.3 Verifying the ReleaseIn order to verify the release, you'll need to have
Once you have the required PGP keys, you can verify the release (assuming
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 What's Changed
New Contributors
Full Changelog: https://github.com/btcsuite/btcd/compare/v0.23.2...v0.23.3/gugger@gmail.com |
2022-11-01 |
lnd | v0.14.5-beta This release is a back port of the second chain synchronization bug fix to the Database MigrationsThis release contains no database migrations. Verifying the ReleaseIn order to verify the release, you'll need to have
Once you have the required PGP keys, you can verify the release (assuming
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 Verifying the Release TimestampFrom 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: 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 These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires. Verifying the Release BinariesOur 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 The Finally, you can also verify the tag itself with the following command:
Verifying the Docker ImagesTo verify the
Building the Contained ReleaseUsers are able to rebuild the target release themselves without having to fetch any of the dependencies. In order to do so, assuming
that
The Additionally, it's now possible to use the enclosed
⚡️⚡️⚡️ OK, now to the rest of the release notes! ⚡️⚡️⚡️ Release Notes
Contributors (Alphabetical Order)
|
2022-11-01 |
lnd | v0.15.4-beta This is an emergency hot fix release to fix a bug that can cause lnd nodes to be unable to parse certain transactions that have a very large number of witness inputs. This release contains no major features, and is instead just a hotfix applied on top of v0.15.3. Verifying the ReleaseIn order to verify the release, you'll need to have
Once you have the required PGP keys, you can verify the release (assuming
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 Verifying the Release TimestampFrom 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: 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 These timestamps should give users confidence in the integrity of this release even after the key that signed the release expires. Verifying the Release BinariesOur 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 The Finally, you can also verify the tag itself with the following command:
Verifying the Docker ImagesTo verify the
Building the Contained ReleaseUsers are able to rebuild the target release themselves without having to fetch any of the dependencies. In order to do so, assuming
that
The Additionally, it's now possible to use the enclosed
⚡️⚡️⚡️ OK, now to the rest of the release notes! ⚡️⚡️⚡️ Release Noteshttps://github.com/lightningnetwork/lnd/blob/v0-15-4-branch/docs/release-notes/release-notes-0.15.4.md /gugger@gmail.com/gugger@gmail.com |
2022-11-01 |