Weekly Edition for Thursday, Oct 7

Newsletters

Releases

project release date
lnd v0.13.3-beta

Security Fixes

This release contains a security fix for CVE-2021-41593 which would allow an attacker to cause loss of funds through a griefing vector related to high accepted dust values. This release addresses the issue by enforcing stricter clamps on accepted dust values during channel funding, and also adds hltcswitch level dust accounting to limit the total dust exposure (triggered by an instantaneous force close) at any moment. The default allotted fully forwarded dust exposure level is set at 500k sats, this value can be tweaked with a new config flag: --dust-threshold=.

If upgrading is not possible to prevent CVE-2021-41593, the dust-tool can intercept bad open_channel parameters and reject them via our ChannelAcceptor. In addition, it can also scan your node's current set of confirmed channels and recommend closing potentially risky ones out.

Alternatively, your node's advertised min_htlc value can be increased to ensure it is well above all the dust limits of its active channels.

Database Migrations

This release does not contain any database migrations.

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://keybase.io/bitconner/pgp_keys.asc | gpg --import
curl https://keybase.io/roasbeef/pgp_keys.asc | gpg --import

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

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

You should see the following if the verification was successful:

gpg: Signature made Mon Oct  4 08:20:20 2021 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.13.3-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.13.3-beta.sig.ots -f manifest-roasbeef-v0.13.3-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.16.3, which is required by verifiers to arrive at the same ones. They include the following build tags: autopilotrpc, signrpc, walletrpc, chainrpc, invoicesrpc, routerrpc, watchtowerrpc and monitoring. 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.13.3-beta
gpg: Signature made Mo 04 Okt 2021 16:08:05 CEST
gpg:                using RSA key F4FC70F07310028424EFC20A8E4256593F177720
gpg: Good signature from &#34;Oliver Gugger <gugger@gmail.com>&#34; [unknown]

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.13.3-beta /verify-install.sh v0.13.3-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.13.3-beta.tar.gz are in the current directory, follow these steps:

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

https://github.com/lightningnetwork/lnd/blob/master/docs/release-notes/release-notes-0.13.3.md

Contributors (Alphabetical Order)

2021-10-04

RFC

type rfc # title date status
bip X BIP: Process, revision 3 2021-10-04 Closed
bip bip-0032 Add a Swift implementation of BIP32 for iOS. 2021-10-04 Closed
bip bip-0032 add libwally as bip32 implementation 2021-10-04 Closed
bip bip-0032 Update the implementations section of BIP0032. 2021-10-04 Closed
bip bip-0032 (BIP 32) Repo has been relocated 2021-10-04 Closed
bip bip-0032 BIP32: Add links to libbitcoin implementation, update style. 2021-10-04 Closed
bip bip-0370 BIP 370: Use PSBT_GLOBAL_FALLBACK_LOCKTIME in text 2021-10-02 Merged
bip bip-0174 BIP 0174: Fix typo in PSBT_OUT_BIP32_DERIVATION 2021-10-01 Merged
bolt X Update gossip protocol to support signed values for fees. 2021-10-06 New Issue
bolt X Allowing dust limit below 546 sats 2021-10-06 Closed
bolt X Peers need to check each other's dust limit 2021-10-06 Merged
bolt peer protocol BOLT 2: peers need to check each other's dust limit 2021-10-06 Closed
bolt X Lightning Specification Meeting 2021/09/13 2021-10-06 Closed
bolt messaging BOLT 1: introduce warning messages, reduce requirements to send (hard) errors, remove "all-channel" errors. 2021-10-01 Update
slip X update btachain 2021-10-06 Merged
slip X add DSRV coin type 2021-10-06 Merged
slip X Remove that CJ must be P2WPKH 2021-10-05 Update
slip slip-0044 slip-0044: add Saage coin 2021-10-02 Merged
slip X Update to include Provenance Blockchain prefixes 2021-10-07 Merged