• LL-8289 LL-8255 ledgerjs lib updates https://github.com/LedgerHQ/ledgerjs/releases/tag/v6.17.0
• LL-7451 add send erc1155 capability

• Downgrade polkadot to v6.8.1 (#1537)

• fixes race condition

• LL-8218 fix outputScript for zencash
• LL-8204 LL-8203 LL-8257 LL-8261

• LL-7930 Ensure bech32 version 1.1.x and 2.0.0 are not used together

• 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)

• LL-8115 Additional fix for correct handling of change output (#1524)
• LL-6675 - See NFT in the CLI (#1421)

• LL-8115 Correctly filter out change output from recipients
• LL-8123 Update ledgerjs and deps
• LL-7845 LL-7888 btc bugs

🐛 Fixes

• Hide unsupported tokens

🐛 Fixes

• Fixed overlapping language discoverability pop-up

• @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

• add solana test currencies (#719)
• update ERC20 list

• remove coin in crypto.com name (#714)

• LL-8154 Get rid of bigint to support LLM (#712)
• support Polygon dapps (#704)
• ERC20 list update

• Fix sequence=0 becomes 0xffffffff when signing (#698)
• update axios and react-native-ble-plx

Improvements:

• Fix breaking changes of LND API 0.14 @NicolasDorier

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="" lightninglabs/lnd:v0.14.1-beta /verify-install.sh v0.14.1-beta
$ OK=$?
$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; 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 "-X github.com/lightningnetwork/lnd/build.Commit=v0.14.1-beta" ./cmd/lnd
GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.14.1-beta" ./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="linux-arm64 darwin-amd64"

⚡️⚡️⚡️ 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

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="" lightninglabs/lnd:v0.14.0-beta /verify-install.sh v0.14.0-beta
$ OK=$?
$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; 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 "-X github.com/lightningnetwork/lnd/build.Commit=v0.14.0-beta" ./cmd/lnd
GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.14.0-beta" ./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="linux-arm64 darwin-amd64"

⚡️⚡️⚡️ 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

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="" lightninglabs/lnd:v0.14.0-beta.rc4 /verify-install.sh v0.14.0-beta.rc4
$ OK=$?
$ if [ "$OK" -ne "0" ]; then echo "Verification failed!"; 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 "-X github.com/lightningnetwork/lnd/build.Commit=v0.14.0-beta.rc4" ./cmd/lnd
GO111MODULE=on go install -v -mod=vendor -ldflags "-X github.com/lightningnetwork/lnd/build.Commit=v0.14.0-beta.rc4" ./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="linux-arm64 darwin-amd64"

⚡️⚡️⚡️ 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