Weekly Edition for Thursday, Sep 1



project release date
BTC Pay Server v1.6.10

Bug fixes:

  • Fix Wallet Transactions screen not loading in case of older payout labels (#4078) @Kukks
  • Fix missing route hints for LNURL (#4077) @dennisreimann
  • Fix API Docs url (#4061) @dennisreimann
  • Fix Pay button logo and url (#4054) @dennisreimann
btcd v0.23.1

What's Changed

New Contributors

Full Changelog: https://github.com/btcsuite/btcd/compare/v0.22.0-beta...v0.23.1

lnd v0.15.1-beta

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.

Database Migrations

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: --db.prune-revocation. This migration can be restart at any time, with the migration logic picking up from where it left off.

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:

curl https://raw.githubusercontent.com/lightningnetwork/lnd/master/scripts/keys/roasbeef.asc | gpg --import

Once you have the required PGP keys, you can verify the release (assuming manifest-roasbeef-v0.15.1-beta.sig and manifest-v0.15.1-beta.txt are in the current directory) with:

gpg --verify manifest-roasbeef-v0.15.1-beta.sig manifest-v0.15.1-beta.txt

You should see the following if the verification was successful:

gpg: Signature made Tue Aug 30 14:21:09 2022 PDT
gpg:                using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306
gpg: Good signature from &#34;Olaoluwa Osuntokun <laolu32@gmail.com>&#34; [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.1-beta.txt.asc.ots.

Assuming you have the opentimestamps client installed locally, the timestamps can be verified with the following commands:

ots verify manifest-roasbeef-v0.15.1-beta.sig.ots -f manifest-roasbeef-v0.15.1-beta.sig

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.1-beta
gpg: Signature made Tue 30 Aug 2022 08:19:04 PM UTC using RSA key ID 9B280306
gpg: Good signature from &#34;Olaoluwa Osuntokun <laolu32@gmail.com>&#34;

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=&#34;&#34; lightninglabs/lnd:v0.15.1-beta /verify-install.sh v0.15.1-beta
$ OK=$?
$ if [ &#34;$OK&#34; -ne &#34;0&#34; ]; then echo &#34;Verification failed!&#34;; 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.1-beta.tar.gz are in the current directory, follow these steps:

tar -xvzf vendor.tar.gz
tar -xvzf lnd-source-v0.15.1-beta.tar.gz
GO111MODULE=on go install -v -mod=vendor -ldflags &#34;-X github.com/lightningnetwork/lnd/build.Commit=v0.15.1-beta&#34; ./cmd/lnd
GO111MODULE=on go install -v -mod=vendor -ldflags &#34;-X github.com/lightningnetwork/lnd/build.Commit=v0.15.1-beta&#34; ./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.

Additionally, it's now possible to use the enclosed release.sh script to bundle a release for a specific system like so:

make release sys=&#34;linux-arm64 darwin-amd64&#34;

⚡️⚡️⚡️ OK, now to the rest of the release notes! ⚡️⚡️⚡️

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


python-bitcoinlib python-bitcoinlib-v0.11.2
  • Fixed one remaining use of OpenSSL for RIPEMD-160
python-bitcoinlib python-bitcoinlib-v0.11.1
  • Pure-python RIPEMD-160, for newer versions of OpenSSL without RIPEMD-160 support.
  • Signet support


type rfc # title date status
bip bip-0047 BIP47: Define address types explicitly 2022-08-28 Closed
bolt transactions bolt3: Clarify order of operations for HTLC amount calculation 2022-08-30 Merged
bolt X Add test vectors for option_anchors_zero_fee_htlc_tx 2022-08-30 Update
bolt peer protocol BOLT 2: forget the check about `update_*` messages, and check what must not happens during `shutdown` 2022-08-29 Closed
bolt X option_closing_rejected: turn-based fee_range coop close 2022-08-29 Update
bolt X Lightning Specification Meeting 2022/08/15 2022-08-29 Closed
slip slip-0044 slip-0044: add (avian network#921) 2022-08-29 Merged
slip slip-0044 Update slip-0044.md 2022-08-28 Merged