bulletin
- ledger-live-common: 2 releases, latest is v18.3.3
- release: BTC Pay Server v1.0.6.8
- 22 RFC updates
bulletin
- c-lightning: 2 releases, latest is v0.9.3
- ledger-live-common: 3 releases, latest is v18.1.0
- ledgerjs: 2 releases, latest is v5.39.1
- release: Bitcoin Core v0.21.0
- BTC Pay Server: 2 releases, latest is v1.0.6.7
- release: lnd v0.12.0-beta.rc6
- 5 RFC updates
bulletin
bulletin
- ledger-live-common: 3 releases, latest is v17.7.0
- release: ledgerjs v5.38.0
- release: lnd v0.12.0-beta.rc3
- release: trezor-link v1.7.3
- 4 RFC updates
bulletin
bulletin
Releases
project | release | date |
---|---|---|
libwally-core | release_0.8.2
Note: This release is not binary compatible with 0.8.1. See https://github.com/ElementsProject/libwally-core/blob/master/CHANGES.md for details. |
2021-02-12 |
ledger-live-common | v18.5.5
|
2021-02-22 |
ledger-live-common | v18.5.4
|
2021-02-22 |
ledger-live-common | v18.5.3
|
2021-02-22 |
ledger-live-common | v18.5.2
|
2021-02-22 |
ledger-live-common | v18.5.1
Libraries update: - @walletconnect/client 1.3.5 -> 1.3.6. (it's a patch, nothing really changes) - babel, typescript, ledgerjs |
2021-02-11 |
ledger-live-desktop | v2.22.0 | 2021-02-16 |
ledgerjs | v5.44.1
|
2021-02-22 |
ledgerjs | v5.44.0
|
2021-02-11 |
lib-ledger-core | 4.0.0-rc1
|
2021-02-12 |
lnd | v0.12.1-beta.rc6 Database MigrationsThere are no database migrations in 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 NotesSpec Compatibility
Gossip Propagation ImprovementsThis release reverts the removal of the premature channel update cache that was removed in 0.12.0-beta. Absence of the cache was seen to cause issues with channel update propagation, so the change is reverted to restore the pre-0.12.0-beta behavior and stability. The current plan is to reschedule the cache's removal for 0.13 after performing more extensive investigation. In addition, the gossip throttling adding in v0.12.0 has been refactored to be less aggressive with respect to non-keepalive channel updates, i.e. channel updates that differ in more than just the timestamp. Previously The new throttling logic now employs a directional token bucket rate limiter, the same approach used by No Gossip ModeThis release includes support for a no-graph sync mode which can be enabled by setting This mode is especially helpful to wallet developers that choose to outsource pathfinding via their own service, or purely forwarding nodes that never need to perform pathfinding. Pinned Gossip SyncersTypically To provide more control, a new configuration option has been added allowing users to pin their nodes into an ActiveSync with particular nodes. Each time a connection is established with a pinned syncer,
This can be especially useful for services that run multiple, well-connected RPC Changes
Deterministic Build / Release Verification
Developer Toolchain
Bug Fixes
Full Changelog
Contributors (Alphabetical Order)Andras Banki-Horvath Carla Kirk-Cohen Conner Fromknecht Eugene Siegel Jake Sylvestre Johan T. Halseth Joost Jager Juan Pablo Civile Olaoluwa Osuntokun Oliver Gugger rockstardev Umar Bolatov Vlad Stan Wilmer Paulino/conner@lightning.engineering/conner@lightning.engineering |
2021-02-19 |
lnd | v0.12.1-beta.rc5 Database MigrationsThere are no database migrations in 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 NotesSpec Compatibility
Gossip Propagation ImprovementsThis release reverts the removal of the premature channel update cache that was removed in 0.12.0-beta. Absence of the cache was seen to cause issues with channel update propagation, so the change is reverted to restore the pre-0.12.0-beta behavior and stability. The current plan is to reschedule the cache's removal for 0.13 after performing more extensive investigation. In addition, the gossip throttling adding in v0.12.0 has been refactored to be less aggressive with respect to non-keepalive channel updates, i.e. channel updates that differ in more than just the timestamp. Previously The new throttling logic now employs a directional token bucket rate limiter, the same approach used by No Gossip ModeThis release includes support for a no-graph sync mode which can be enabled by setting This mode is especially helpful to wallet developers that choose to outsource pathfinding via their own service, or purely forwarding nodes that never need to perform pathfinding. Pinned Gossip SyncersTypically To provide more control, a new configuration option has been added allowing users to pin their nodes into an ActiveSync with particular nodes. Each time a connection is established with a pinned syncer,
This can be especially useful for services that run multiple, well-connected RPC Changes
Deterministic Build / Release Verification
Developer Toolchain
Bug Fixes
Full Changelog
Contributors (Alphabetical Order)Andras Banki-Horvath Carla Kirk-Cohen Conner Fromknecht Eugene Siegel Jake Sylvestre Johan T. Halseth Joost Jager Juan Pablo Civile Olaoluwa Osuntokun Oliver Gugger rockstardev Umar Bolatov Vlad Stan Wilmer Paulino/conner@lightning.engineering/conner@lightning.engineering |
2021-02-18 |
lnd | v0.12.1-beta.rc4 Database MigrationsThere are no migrations in 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 NotesSpec Compatibility
Gossip Propagation ImprovementsThis release reverts the removal of the premature channel update cache that was removed in 0.12.0-beta. Absence of the cache was seen to cause issues with channel update propagation, so the change is reverted to restore the pre-0.12.0-beta behavior and stability. The current plan is to reschedule the cache's removal for 0.13 after performing more extensive investigation. In addition, the gossip throttling adding in v0.12.0 has been refactored to be less aggressive with respect to non-keepalive channel updates, i.e. channel updates that differ in more than just the timestamp. Previously The new throttling logic now employs a directional token bucket rate limiter, the same approach used by No Gossip ModeThis release includes support for a no-graph sync mode which can be enabled by setting This mode is especially helpful to wallet developers that choose to outsource pathfinding via their own service, or purely forwarding nodes that never need to perform pathfinding. Pinned Gossip SyncersTypically To provide more control, a new configuration option has been added allowing users to pin their nodes into an ActiveSync with particular nodes. Each time a connection is established with a pinned syncer,
This can be especially useful for services that run multiple, well-connected RPC Changes
Deterministic Build / Release Verification
Developer Toolchain
Bug Fixes
Full Changelog
Contributors (Alphabetical Order)Andras Banki-Horvath Carla Kirk-Cohen Conner Fromknecht Eugene Siegel Jake Sylvestre Johan T. Halseth Joost Jager Juan Pablo Civile Olaoluwa Osuntokun Oliver Gugger rockstardev Umar Bolatov Vlad Stan Wilmer Paulino /conner@lightning.engineering/conner@lightning.engineering |
2021-02-17 |
lnd | v0.12.1-beta.rc3 Database MigrationsThere are no migrations in 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 NotesSpec Compatibility
Gossip Propagation ImprovementsThis release reverts the removal of the premature channel update cache that was removed in 0.12.0-beta. Absence of the cache was seen to cause issues with channel update propagation, so the change is reverted to restore the pre-0.12.0-beta behavior and stability. The current plan is to reschedule the cache's removal for 0.13 after performing more extensive investigation. In addition, the gossip throttling adding in v0.12.0 has been refactored to be less aggressive with respect to non-keepalive channel updates, i.e. channel updates that differ in more than just the timestamp. Previously The new throttling logic now employs a directional token bucket rate limiter, the same approach used by No Gossip ModeThis release includes support for a no-graph sync mode which can be enabled by setting This mode is especially helpful to wallet developers that choose to outsource pathfinding via their own service, or purely forwarding nodes that never need to perform pathfinding. Pinned Gossip SyncersTypically To provide more control, a new configuration option has been added allowing users to pin their nodes into an ActiveSync with particular nodes. Each time a connection is established with a pinned syncer,
This can be especially useful for services that run multiple, well-connected RPC Changes
Deterministic Build / Release Verification
Developer Toolchain
Bug Fixes
Full Changelog
Contributors (Alphabetical Order)Andras Banki-Horvath Carla Kirk-Cohen Conner Fromknecht Eugene Siegel Jake Sylvestre Johan T. Halseth Joost Jager Juan Pablo Civile Olaoluwa Osuntokun Oliver Gugger rockstardev Umar Bolatov Vlad Stan Wilmer Paulino/conner@lightning.engineering/conner@lightning.engineering |
2021-02-12 |
WalletWasabi | v1.1.12.4 SummaryThis silent release contains an updated Tor client that has the fix for the DDoS vulnerability. Users who encountered Tor connection problems should update their Wasabi.
Newbie GuideWhile setting up Wasabi is straightforward, even a Linux wizard with the longest beard can get stuck on the most basic tasks. Consider taking a look at the Installation Instructions guide. Advanced GuideIf you want to build Wasabi from source code or update the source code check out these instructions. From version 1.1.3 Wasabi also introduces reproducible builds: Deterministic Build Guide Build with .NET Core 3.1.403-win-x64. FAQ
Release Notes
|
2021-02-16 |