Week of Thursday, Nov 25

project release date
ledger-live-common v21.18.0
ledger-live-common v21.17.2
  • Downgrade polkadot to v6.8.1 (#1537)
ledger-live-common v21.17.1
  • fixes race condition
ledger-live-common v21.17.0
  • LL-8218 fix outputScript for zencash
  • LL-8204 LL-8203 LL-8257 LL-8261
ledger-live-common v21.16.4
erc20 update
ledger-live-common v21.16.3
  • LL-7930 Ensure bech32 version 1.1.x and 2.0.0 are not used together
ledger-live-common v21.16.2
  • LL-8185 add hardcoded dependencies between plugins and eth app (#1529)
  • LL-8115 Yet another case to handle change output in recipients (#1527)
  • LL-7913 Fix isConfirmed operation condition (#1526)
  • LL-8133 Improve tx size estimation function (#1522)
ledger-live-common v21.16.1
  • LL-8115 Additional fix for correct handling of change output (#1524)
  • LL-6675 - See NFT in the CLI (#1421)
ledger-live-common v21.16.0
  • LL-8115 Correctly filter out change output from recipients
  • LL-8123 Update ledgerjs and deps
  • LL-7845 LL-7888 btc bugs
ledger-live-desktop v2.35.2

🐛 Fixes

  • Hide unsupported tokens
ledgerjs v6.17.0
  • @ledgerhq/cryptoassets update
    • Add Celo to currencies (#723) thx @pawelnguyen
    • LL-8289 avalanche to be having its own family (#729)
    • added moonriver (#722) thx @albertov19
  • @ledgerhq/hw-app-eth: All necessary fixes to support NFT
  • @ledgerhq/hw-app-btc: LL-8255: call onDeviceSignatureRequested at a more accurate time
ledgerjs v6.16.0
  • add solana test currencies (#719)
  • update ERC20 list
ledgerjs v6.15.2
  • remove coin in crypto.com name (#714)
ledgerjs v6.15.1
  • LL-8154 Get rid of bigint to support LLM (#712)
  • support Polygon dapps (#704)
  • ERC20 list update
ledgerjs v6.15.0
  • Fix sequence=0 becomes 0xffffffff when signing (#698)
  • update axios and react-native-ble-plx
BTC Pay Server v1.3.6


  • Fix breaking changes of LND API 0.14 @NicolasDorier
lnd v0.14.1-beta

This marks the first minor release of the 0.14.x release cycle! This is primarily a bug fix release that fixes: an issue that would arise with lnd nodes older than 2 years in certain circumstances, a fix to ensure we always advertise a consistent of feature bits, and most importantly a fix to ensure compatibility for new channel opens with the latest versions of c-lightning+eclair.

Database Migrations

There are two database migrations for this version in lnd (that were included in 0.14.0): 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 v0.14.0-beta (and v0.14.1-beta) 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/guggero.asc | gpg --import

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

gpg --verify manifest-guggero-v0.14.1-beta.sig manifest-v0.14.1-beta.txt

You should see the following if the verification was successful:

gpg: Signature made Wed 24 Nov 2021 11:15:46 PM CET
gpg:                using RSA key F4FC70F07310028424EFC20A8E4256593F177720
gpg: Good signature from &#34;Oliver Gugger <gugger@gmail.com>&#34; [ultimate]
Primary key fingerprint: F4FC 70F0 7310 0284 24EF  C20A 8E42 5659 3F17 7720

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-guggero-v0.14.1-beta.sig.ots.

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

ots verify manifest-guggero-v0.14.1-beta.sig.ots -f manifest-guggero-v0.14.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.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.1-beta
gpg: Signature made Wed 24 Nov 2021 11:04:06 PM CET
gpg:                using RSA key F4FC70F07310028424EFC20A8E4256593F177720
gpg: Good signature from &#34;Oliver Gugger <gugger@gmail.com>&#34; [ultimate]
Primary key fingerprint: F4FC 70F0 7310 0284 24EF  C20A 8E42 5659 3F17 7720

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

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

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

Contributors (Alphabetical Order) – combined 0.14+0.14.1

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 Jamie Turley 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 nayuta-ueno offerm positiveblue xanoni /gugger@gmail.com/gugger@gmail.com

type rfc # title date status
bip X [DRAFT] Durable, Low Energy Bitcoin PoW 2021-11-25 Update
bip bip-0322 Allow Taproot outputs in BIP 322 2021-11-24 Merged
bip bip-0174 BIP-174: Removing PSBT_OUT_TAP_LEAF_SCRIPT 2021-11-23 Update
bip X Enable secure protocol 2021-11-23 Update
bip X PSBT: Add pay-to-contract tweaks to tx inputs 2021-11-22 Update
bip bip-0119 Define BIP-119 CheckDefaultCheckTemplateVerifyHash 2021-11-21 Update
bip X fix secg.org secp256k1 docs link 2021-11-19 Merged
bip bip-0032 Fix typo in BIP 32 2021-11-19 Update
bip bip-0155 BIP 155: add Yggdrasil 2021-11-19 Update
bolt routing gossip BOLT 7: Onion message support (features 38/39) 2021-11-25 Update
bolt X Protocol Feature Request: Shift balance between multiple channels with the same peer 2021-11-23 Update
bolt X Advertize compression algorithms support in `init` (features 32/33) 2021-11-23 Update
bolt peer protocol BOLT-02+09: introduce feature bit to gate new channel_type feature - 44/45 2021-11-23 Update
bolt X Lightning Specification Meeting 2021/10/25 2021-11-22 Closed
slip X Added EVM Scaling Chains 2021-11-25 Merged
slip slip-0044 slip-0044: add coin 2021-11-25 Merged
slip X add BNC to 0044 2021-11-24 Merged
slip slip-0173 slip-0173: add bostrom 2021-11-23 Merged
slip slip-0044 update slip-0044.md - insert Lunarium project 2021-11-20 Merged
slip slip-0044 Update slip-0044.md 2021-11-19 Update