Weekly Edition for Thursday, Nov 18

bulletin

Newsletters

Releases

project release date
ledger-live-desktop v2.35.1

🐛 Fixes

  • Fixed overlapping language discoverability pop-up
2021-11-16
ledger-live-desktop v2.35.0

🚀 Features

  • Taproot is now supported in Ledger Live (Experimental feature)!
  • App language automatically matches the one of your system configuration (EN, FR, RU)
  • Rebranding : New logo and splashscreen

🐛 Fixes

  • Polkadot support restored
  • Status banner removal
  • Bitcoin support improvements (Exprimental feature)
2021-11-12
bcoin v2.2.0
See https://github.com/bcoin-org/bcoin/blob/master/CHANGELOG.md for upgrade information and release notes.
2021-11-12
BTC Pay Server v1.3.5

Bug fixes:

  • Fix: Checkout page of for invoices of 0 amount shouldn't crash, but 404 @NicolasDorier
  • Swagger doc: Fix type of property cryptoCode (#3088) @ndeet
  • Fix bug with fraction amount display in crowdfund app (#3098) @bolatovumar
  • Swagger doc: Update Swagger docs for webhook event types (#3104) @bolatovumar
  • Payout/pull payment page would crash if no payment method are set on the store @satwo

Improvements:

  • Add crypto code for invoice and pull payment payout API response (#3099) @bolatovumar
  • Prevent creation of on-chain invoices below the dust limit (#3082) @satwo
2021-11-15
lnd v0.14.0-beta

Database Migrations

There are two database migrations for this version in lnd: One optimizes the storage structure of HTLCs for faster payments and the other removes old channel state data from closed channels to free up disk space. See the release notes for more information.

NOTE: Compacting the DB is recommended after running the migration to reclaim the freed up space.

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

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

You should see the following if the verification was successful:

gpg: Signature made Wed Nov 17 13:20:26 2021 PST
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.14.0-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.14.0-beta.sig.ots -f manifest-roasbeef-v0.14.0-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.17.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.14.0-beta
gpg: Signature made Wed 17 Nov 2021 08:04:23 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.14.0-beta /verify-install.sh v0.14.0-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.14.0-beta.tar.gz are in the current directory, follow these steps:

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

Read the full release notes here: https://github.com/lightningnetwork/lnd/blob/master/docs/release-notes/release-notes-0.14.0.md

Contributors (Alphabetical Order)

Abubakar Nur Khalil Adrian-Stefan Mares Alex Bosworth Alyssa Hertig András Bánki-Horváth Bjarne Magnussen Carla Kirk-Cohen Carsten Otto Conner Fromknecht Elle Mouton ErikEk Eugene Siegel Hampus Sjöberg Harsha Goli Jesse de Wit Johan T. Halseth Johnny Holton Joost Jager Jordi Montes Juan Pablo Civile Kishin Kato Leonhard Weese Martin Habovštiak Michael Rhee Naveen Srinivasan Olaoluwa Osuntokun Oliver Gugger Priyansh Rastogi Roei Erez Simon Males Stevie Zollo Torkel Rogstad Wilmer Paulino Yong Yu Zero-1729 benthecarman de6df1re github2k20 mateuszmp nathanael offerm positiveblue xanoni /laolu32@gmail.com/laolu32@gmail.com

2021-11-17
lnd v0.14.0-beta.rc4

Database Migrations

There are two database migrations for this version in lnd: One optimizes the storage structure of HTLCs for faster payments and the other removes old channel state data from closed channels to free up disk space. See the release notes for more information. NOTE: Compacting the DB is recommended after running the migration to reclaim the freed up space.

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

gpg --verify manifest-roasbeef-v0.14.0-beta.rc4.sig manifest-v0.14.0-beta.rc4.txt

You should see the following if the verification was successful:

gpg: Signature made Wed Sep 30 17:35:20 2020 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.14.0-beta.rc4.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.14.0-beta.rc4.sig.ots -f manifest-roasbeef-v0.14.0-beta.rc4.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.17.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.14.0-beta.rc4
gpg: Signature made Tue Sep 15 18:55:00 2020 PDT
gpg:                using RSA key 60A1FA7DA5BFF08BDCBBE7903BBD59E99B280306
gpg: Good signature from &#34;Olaoluwa Osuntokun <laolu32@gmail.com>&#34; [ultimate]

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

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

Read the full release notes here: https://github.com/lightningnetwork/lnd/blob/master/docs/release-notes/release-notes-0.14.0.md

Contributors (Alphabetical Order)

Abubakar Nur Khalil Adrian-Stefan Mares Alex Bosworth Alyssa Hertig András Bánki-Horváth Bjarne Magnussen Carsten Otto Conner Fromknecht Elle Mouton ErikEk Eugene Siegel Hampus Sjöberg Harsha Goli Jesse de Wit Johan T. Halseth Johnny Holton Joost Jager Jordi Montes Juan Pablo Civile Kishin Kato Leonhard Weese Martin Habovštiak Michael Rhee Naveen Srinivasan Olaoluwa Osuntokun Oliver Gugger Priyansh Rastogi Roei Erez Simon Males Stevie Zollo Torkel Rogstad Wilmer Paulino Yong Yu Zero-1729 benthecarman carla de6df1re github2k20 mateuszmp nathanael offerm positiveblue xanoni/laolu32@gmail.com/laolu32@gmail.com

2021-11-16

RFC

type rfc # title date status
bip X 371: Fix test formatting 2021-11-17 Merged
bip bip-0300 Update BIPs 300/301 2021-11-17 Update
bip bip-0325 BIP 325: Clarify that scriptWitness is a stack, not a byte string 2021-11-17 Merged
bip bip-0325 BIP 325: Remove empty section "Acknowledgement" 2021-11-17 Merged
bip bip-0341 Mention activation heights in BIP 341 🥕 2021-11-17 Merged
bip bip-0039 Czech wordlist for BIP0039 2021-11-16 Merged
bip bip-0001 BIP 0001: Absolute path for figure. 2021-11-16 Update
bip X Make Wikitext linguist-detectable 2021-11-16 Merged
bip bip-0009 BIP 0009: Remove transparent background from figure. 2021-11-16 Update
bip X typo: BIP [380-385] 2021-11-15 Update
bip bip-0322 Clarify BIP 322 seralization requires a signed transaction 2021-11-14 Merged
bip bip-0341 BIP341 test vectors 2021-11-13 Merged
bip X [Nit] Add full stop to conclude sentence 2021-11-12 New PR
bip X BIP draft of portion of tx fee burn 2021-11-18 New PR
bolt X Explicitly allow funding_locked early, and support alias scids (feat 46/47) 2021-11-13 Update
bolt X Drop ping sending rate-limit suggestion 2021-11-12 Update
slip X version bytes for p2tr 2021-11-17 Closed
slip slip-0044 Add Aleph Zero to slip-0044 2021-11-16 Merged
slip slip-0044 slip-0044: add coin 2021-11-13 Merged