@lverba lverba released this Nov 23, 2018 · 78 commits to master since this release

Assets 15

LightningPeach wallet v0.3.0-testnet

Release notes v.0.3.0-testnet:

  • Now it is possible to restore all lighting channels with their balances in situations when device is lots, broken or there is a need to transfer data to another device. This option is now available since data from wallet is backed up to Dropbox.
  • The initial block synchronization has been speeded up. Now synchronization takes up to 1 minute.
  • Payment history became more convenient. Now you can search and filter payments by a name of payment or a recipient.
  • The possibility to edit existing recurring payments has been added.

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.3.0-testnet.txt and manifest-v0.3.0-testnet.txt.sig are in the current directory) with:

gpg --verify manifest-v0.3.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):

5827d8b55ded2e7ef1a8d46c29a2891791acb4672f1a8a1b307ebc208c0f185a  lightning-peach-wallet_0.3.0-testnet_amd64.deb
ed11c63ebc92d346380d1323a03cfd47647d0ce4bdbaf17e45d7f41ba755b7b0  lightning-peach-wallet-0.3.0-testnet.dmg
e2c8f8bf3361a37f23595b0d0675d5b5a47480fab6e751d543aa9435068ab9a1  lightning-peach-wallet-0.3.0-testnet.exe
5fffc9e53d1c724554631cc8bfb71ac7bd92a678aab4a73f3204f088bbd580a6  lightning-peach-wallet-0.3.0-testnet-mac.zip
21a1ed06eb515a21e8618ac72b5b28532ea921b838e956e304e746aa0d70ba52  lightning-peach-wallet-0.3.0-testnet-x86_64.AppImage
e4a594e6e47db0115a975641704bff56d808408623d702f5c2009f9f8e62b385  lightning-peach-wallet-setup-0.3.0-testnet.exe

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.

@boodyvo boodyvo released this Oct 11, 2018 · 195 commits to master since this release

Assets 15

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.

@boodyvo boodyvo released this Aug 8, 2018 · 299 commits to master since this release

Assets 7

LightningPeach wallet v0.1.0-testnet

This is the first public release of the LightningPeach wallet.
This release runs LND with neutrino enabled and on Bitcoin's testnet.
Find out more about our wallet:

  • LightningPeach wallet video tutorial can be found here
  • LightningPeach wallet user guide can be found here

Important: Development of the LightningPeach wallet is still in progress. It means that different issues can occur during wallet usage. Using real coins may be risky.

Known issues:

  • Sometimes Lightning Network channels may become inactive.
  • Sometimes payments may result in the following error: “unable to find path to destination”.

Note: We use LND fork to improve UX. If you would like to build your application from LND, please use the Installation guide.

Logs collected by the application are kept in local folder on your PC:

  • MacOS: ~/Library/Application\ Support/lightning-peach-wallet/.lnd/
  • Linux: ~/.config/lightning-peach-wallet/.lnd/
  • Windows: %HOMEPATH%\AppData\Roaming\lightning-peach-wallet\.lnd\

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.1.0-testnet.txt and manifest-v0.1.0-testnet.txt.sig are in the current directory) with:

gpg --verify manifest-v0.1.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):

634eed0d7918f1230292cde469a942571f8e78e545bbb56340fc7741c2cfd9cf  lightning-peach-wallet-setup-0.1.0-testnet.exe
3927d8fe0fb3497e62905b7db4eb22788d19687fe9c33dca776c19dc421868fa  lightning-peach-wallet-0.1.0-testnet-amd64.deb
ca74681d45cd12108099aee793f5e8acf6e3c6a81856eb49f9591e661f62689c  lightning-peach-wallet-0.1.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.