Zap Desktop 0.2.0 Beta

The new and improved cross-platform Zap Desktop. Lots of new things like LND-0.4.2, a complete re-design, new on-boarding, autopilot configuration, remote node connection, sats/bits/BTC denomination support, BTCPay support and much more!

Changes

Update BTCD full nodes that neutrino connects to

Added input menu (copy/paste on text inputs)

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 jimmymow's key if you haven't done so already:

curl https://keybase.io/jimmymow/pgp_keys.asc | gpg --import

The keybase page of jimmymow includes several attestations across distinct platforms in order to provide a degree of confidence that this release was really signed by "jimmymow".

Once you have his PGP key you can verify the release (assuming manifest-v0.1.1-beta.txt and manifest-v0.1.1-beta.txt.sig are in the current directory) with:

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

That will verify the signature on the main manifest page which ensures integrity and authenticity of the zip you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the zip, and compare that with the following hashes (which are included in the manifest file):

One can use the shasum -a 256 <file name here> tool in order to re-compute the sha256 hash of the target zip for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

Zap v0.1.0-beta

This is the first public cross-platform Zap release. Everything you need to experience the Lightning Network is packaged in this release. This release runs LND with neutrino, autopilot enabled and on Bitcoin's testnet.

You can read more about Zap here You can find a Zap tutorial video series here You can find a Zap FAQ page here

NOTE: the version of lnd packaged includes a breaking change. As a result, if you've previously used LND (via Zap, lightning-app, or lnd at the command line) before updating we recommend that users close out all their active channels, and also transfer any testnet coins they wish to hold onto to an external wallet before updating.

Before updating, users will need to remove all data from lnd's home data directory. This is required as there have been some breaking database changes within lnd itself. Depending on your operating system, the data directory will be found in a different location on the file system:

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 jimmymow's key if you haven't done so already:

curl https://keybase.io/jimmymow/pgp_keys.asc | gpg --import

The keybase page of jimmymow includes several attestations across distinct platforms in order to provide a degree of confidence that this release was really signed by "jimmymow".

Once you have his PGP key you can verify the release (assuming manifest-v0.1.0-beta.txt and manifest-v0.1.0-beta.txt.sig are in the current directory) with:

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

That will verify the signature on the main manifest page which ensures integrity and authenticity of the zip you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the zip, and compare that with the following hashes (which are included in the manifest file):

One can use the shasum -a 256 <file name here> tool in order to re-compute the sha256 hash of the target zip for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.