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:

• MacOS: $HOME/Library/Application Support/Lnd
• Windows: %LOCALAPPDATA%\Lnd
• Linux: ~/.lnd

This release is pinned against the following commit of lnd: lightningnetwork/lnd@e30f869

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

1d194549c9a0566f92f19125a3788fb0fca4ca80576288ce327aa9be6c6acf49  mac-release-v0.1.0-beta.zip
bb08717570d2dc00ef9eee68b8bed3a2f76529b0fb54b5da1d170bf21a214e26  linux-release-v0.1.0-beta.zip
6b65e2a085a9589c1805ffc004acbe0591f712442b99c3ab82ddf9f45e1fc62a  win-release-v0.1.0-beta.zip

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.