Week of Thursday, Nov 14

project release date
nanopos v0.1.6 2019-11-11
ledger-live-common v8.8.1
fixes in @ledgerhq/devices
2019-11-12
ledger-live-common v8.8.0
fixes for XTZ
2019-11-12
ledger-live-desktop v1.18.2

🎊 Dark Mode

WHEN DARK MODE?! NOW!!! Go to the settings and select your favorite theme for your favorite app

🔍 Other

  • Improved the firmware user experience and logic
  • Big technical refactoring for better modularization and performance
  • Setting an ETH Gas Limit lower than the estimation triggers a warning
  • Added a customizable gap limit in experimental settings for recovery purposes

🐞 Bug fixes

  • ERC20 operations stay visible when they are broadcasted
  • Various minor fixes
2019-11-12
BTC Pay Server zlndseedbackup 2019-11-10
btcd v0.20.1-beta

This is a minor release of btcd that fixes some bugs in the p2p sub-system, and also updates relevant parts of btcjson to be compatible with bitciond 0.19.

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/roasbeef/pgp_keys.asc | gpg --import

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

gpg --verify manifest-v0.20.1-beta.txt.sig

You should see the following if the verification was successful:

gpg: assuming signed data in 'manifest-v0.20.1-beta.txt'
gpg: Signature made Tue Nov 12 19:08:07 2019 PST
gpg:                using RSA key 4AB7F8DA6FAEBB3B70B1F903BC13F65E2DC84465
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 Binaries

As of this release, our release binaries are fully reproducible thanks to go1.13! Third parties are now 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.13.1, which is required by verifiers to arrive at the same ones.

Finally, you can also verify the tag itself with the following command:

git verify-tag v0.20.1-beta

You should see something along the lines of this in the case of a valid tag:

gpg: Signature made Tue Nov 12 18:29:03 2019 PST
gpg:                using RSA key 4AB7F8DA6FAEBB3B70B1F903BC13F65E2DC84465
gpg: Good signature from &#34;Olaoluwa Osuntokun <laolu32@gmail.com>&#34; [ultimate]

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 btcd-source-v0.20.1-beta.tar.gz are in the current directory, follow these steps:

tar -xvzf vendor.tar.gz
tar -xvzf btcd-source-v0.20.1.tar.gz
GO111MODULE=on go install -v -mod=vendor 
GO111MODULE=on go install -v -mod=vendor ./cmd/btcctl

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 also possible to use the enclosed release.sh script to bundle a release for a specific system like so:

BTCBUILDSYS=&#34;linux-arm64 darwin-amd64&#34; ./build/release/release.sh

Release Notes

The btcjson package as been updated to be compatible with bitcoind v0.19.0 as required by the lnd project.

A race condition in the server related to the set of known addresses for a peer has been eliminated.

We've cleaned up some logic that previously caused log spam due to the stricter version handshake we now enforce.

Changelog

The full list of changes since v0.20.0-beta can be found here:

Contributors (Alphabetical Order)

Olaoluwa Osuntokun Wilmer Paulino Eugene Zeigel

/laolu32@gmail.com/laolu32@gmail.com

2019-11-13
trezor-link v1.6.6 2019-11-11
rfc
type rfc # title date status
bip bip-0157 BIP-0157: increase max getcfilters request to 1k blocks 2019-11-11 Merged
bip bip-0179 BIP 179: Name for payment recipient identifiers 2019-11-08 Merged
bolt payment encoding Add bolt11 test vector with amount in `p` units 2019-11-14 Update
bolt payment encoding Add bolt11 example with amount in pico-BTC 2019-11-13 Closed
bolt X WIP: Dual Funding (v2 Channel Establishment protocol) 2019-11-13 Update
bolt onion routing BOLT-04: modify Sphinx packet construction to use starting random bytes 2019-11-13 Update
bolt X Flat features: far simpler solution for feature bits. 2019-11-13 Update
bolt X option_scid_assign: privacy protection for private channels. 2019-11-08 Update
bolt onion routing BOLT 4: add a requirement of `tlv_payload payload format` 2019-11-08 Update
bolt X Anchor outputs 2019-11-08 Update
bolt payment encoding Bolt 11: add a payment secret to invoice 2019-11-08 Closed
bolt payment encoding BOLT 11: add optional vendor field. 2019-11-08 Update
slip X RaiBlocks is Nano now 2019-11-12 Merged
slip X 0173: Add IoTeX prefix ('io'). 2019-11-08 Merged
slip slip-0044 add Lava to slip-0044 2019-11-08 Merged