Weekly Edition for Thursday, Aug 18
- Bitcoin Optech: Bitcoin Optech Newsletter #213 (August 17, 2022)
|BTC Pay Server||v1.6.9
|BTC Pay Server||v1.6.8
This marks the first minor release of the 0.15.x cyle! This release includes support for zero conf channels, scid alisases (random scid values in the invoice), switches to using taproot addresses everywhere applicable by default, and also includes an optional database migration that can potential reclaim GBs of disk space for old or large lnd nodes.
This release contains an optional migration to delete old revocation log space. The v0.15 release contained an "on the fly" migration that will start to write items in the revocation log in a more efficient manner. This release allows users to reclaim all the old disk space by converting historical records to the new format, with the old records being deleted.
The migration can be activated with a new CLI command:
Verifying the Release
In 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 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:
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 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
Finally, you can also verify the tag itself with the following command:
Verifying the Docker Images
To verify the
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
Additionally, it's now possible to use the enclosed
⚡️⚡️⚡️ OK, now to the rest of the release notes! ⚡️⚡️⚡️
Contributors (Alphabetical Order)
bitromortac Carsten Otto Elle Mouton ErikEk Eugene Siegel Jordi Montes Matt Morehouse Slyghtning Oliver Gugger Olaoluwa Osuntokun Priyansh Rastogi Tommy Volk Yong Yu Ziggie /email@example.comfirstname.lastname@example.org