Weekly Edition for Thursday, Oct 13



project release date
libwally-core release_0.8.6
Note this release contains ABI changes, please see CHANGES.md for details.

  • Add initial support for PSBT v2 and Elements PSET v2.
  • Update PSBT v0 support to the latest changes. Note that Taproot fields are serialized but general Taproot support is not yet implemented.
  • Remove Elements PSET v0 support.
  • Extend the wally_map API into a generic int/blob associative container.
  • Add secp256k1 group scalar arithmetic operations.
  • Add support for explicit value rangeproof and explicit asset surjectionproof generation and validation.
  • Add incremental/partial blinding primitives.
  • Update the built-in libsecp256k1 library.
  • Documentation updates, build/test improvements and misc bug fixes.
lib-ledger-core 4.4.0-rc.1

What's changed

  • VG-10078 Filter dusty UTXOs at SQL level by @BertrandD in #913

Full Changelog: https://github.com/LedgerHQ/lib-ledger-core/compare/4.3.7...4.4.0-rc.1

BTC Pay Server v1.6.12

New features

  • Greenfield: Extend LN GetInfo data (#4167) @dennisreimann

Bug fixes

  • Always show overpaid amount if invoice is overpaid (#4192) @bolatovumar
  • Fix custodian Swagger docs missing some path parameters (#4196) @AryanJ-NYC
  • Fix receipts for Lightning Address invoices (#4169) @dennisreimann
  • POS: Fix keypad view without custom amount (#4183) @dennisreimann @bolatovumar
  • Fix truncated dates in wallet transaction list (#4191) @dennisreimann
  • Update default value for "showCustomAmount" in Swagger docs (#4200) @bolatovumar


  • The wallet transaction list use infinity scroll rather than pagination (#4074) @HamroRamro @dennisreimann
  • Remove direct and temp link functionality from the File Storage (#4177) @daviogg
  • Fix warning error when rebooting the server caused by some shitcoin currency pair format @NicolasDorier
  • Add Invoice.OrderId to list of supported email interpolation strings (#4202) @bolatovumar
  • Do not hide errors happening in tasks spawned by BaseAsyncService @NicolasDorier
btcd v0.22.2

What's Changed

Full Changelog: https://github.com/btcsuite/btcd/compare/v0.22.1...v0.22.2

btcd v0.23.2

What's Changed

New Contributors

Full Changelog: https://github.com/btcsuite/btcd/compare/v0.23.1...v0.23.2

lnd v0.15.2-beta

This is an emergency hot fix release to fix a bug that can cause lnd nodes to be unable to parse certain large blocks.

This release contains no major features, and is instead just a hotfix applied on top of v0.15.1.

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.2-beta.sig and manifest-v0.15.2-beta.txt are in the current directory) with:

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

You should see the following if the verification was successful:

gpg: Signature made Sun Oct  9 20:36:23 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.2-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.2-beta.sig.ots -f manifest-roasbeef-v0.15.2-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.2-beta
gpg: Signature made Mon 10 Oct 2022 02:35:30 AM 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.2-beta /verify-install.sh v0.15.2-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.2-beta.tar.gz are in the current directory, follow these steps:

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





type rfc # title date status
bip X BIPXXX: Taproot Annex Format 2022-10-11 Update
bip bip-0118 Be more explicit about ext_flag values in BIP118 2022-10-10 Closed
bip X Package Relay and child-with-unconfirmed-parents + tx-with-unconfirmed-ancestors Packages 2022-10-13 Closed
bolt X final_incorrect_htlc_amount failure too strict? 2022-10-08 Update
slip slip-0173 Add Hypersign HRP to SLIP-0173 2022-10-11 Merged
slip slip-0044 Update slip-0044.md 2022-10-11 Merged
slip X Updated Etho 2022-10-08 Merged
slip X Bug on Transaction and Fake contract mint 2022-10-07 Closed