### Lightning Peach Wallet: v0.2.0-testnet

lightning-peach-wallet version v0.2.0-testnet released.

# LightningPeach wallet v0.2.0-testnet

Release v0.2.0-testnet supports lnd 0.5.0. In this release, some bugs were fixed, and the following improvements have been added: - New tooltips, which make wallet usage easier and more user-friendly. - Automatic application update. Now there is no need to download the latest version of the wallet, it will be updated automatically. - System notifications that are displayed as push notifications on your device. Now you won’t miss important events, such as new incoming transaction or unilateral channel closing. - Switching between application tabs with the help of keyboard shortcuts (ctrl + tab + ?shift). - Now it is visible when synchronization with blockchain is lost. - Channels can be renamed. - New opportunities with stream payments. Now they are called recurring payments and can cover more practical use cases. For example, you can set up how often you would like to make payments and the wallet will automatically process them accordingly (the application should be opened or launched from time to time to process recurring transactions correctly).

# 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 LighntingPeach Wallet’s key if you haven’t done so already:

curl "https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x3B50C645039078ED" | gpg --import

Once you have LighntingPeach Wallet’s PGP key you can verify the release (assuming manifest-v0.2.0-testnet.txt and manifest-v0.2.0-testnet.txt.sig are in the current directory) with:

gpg --verify manifest-v0.2.0-testnet.txt.sig

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

82215bbee35b6375360e3c10d8053948091e71b874e7b02d4f73ac43fca061b7  lightning-peach-wallet-0.2.0-testnet-mac.zip
d5e2e5e46f70ae56c698afe7635d9d170210524b8616e25320366d8b29f9d028  lightning-peach-wallet_0.2.0-testnet_amd64.deb
27601b46d8ef33e2fa312b6f672ea36ae61709d0f98fd017957b25bd0cdc95cb  lightning-peach-wallet-0.2.0-testnet.exe
3bc78e7e838d9d99380558c5a548576bcbfa11494308ed1b20d1b6efc9e06312  lightning-peach-wallet-0.2.0-testnet-x86_64.AppImage
84800973682f32b99c913d1c1ac14705646652033fda27aa1fc15d87017afb87  lightning-peach-wallet-setup-0.2.0-testnet.exe
cb285f6823597936f4be87d09020d574cdf5dc8da8b979318ebae71c07701b74  lightning-peach-wallet-0.2.0-testnet.dmg


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