LightningPeach wallet v0.5.0-mainnet-beta
In this release we introduce two user modes:
- Standard mode – the mode, in which there is no communication with central server. This allows you to save anonymity provided by the Lightning network.
- Extended mode – in this mode you can use all wallet functions with the help of central server. This opens access to such features as address book, paying by Lightning ID and recurring payments.
The user mode can be changed anytime.
Invoices in socket messages, which are sent through the server, are now encrypted. It means that invoice data, as well as received payment requests, now can't be read by third parties, thus it provides more security for your invoices and received payment requests.
We are introducing QR codes for connecting from the Peach mobile wallet. It means that, If you have public IP address, then you can keep your desktop node active and connect to it from your Peach mobile wallet with the help of generated QR code.
- Added the descirption of what data is collected in each user mode (Standard and Extended one).
- Updated information on collecting additional user data with Google Analytics and Firebase.
- Removed several purposes for which user's data is collected.
Verifying the Release
In order to verify the release, you'll need to have
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.5.0-mainnet-beta.txt.sig are in the current directory) with:
gpg --verify manifest-v0.5.0-mainnet-beta.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):
6719ff040bfd67857d44c44f69d1e9f034a38f62e5a92179a14cb11f4bc618ed peach-wallet-desktop-0.5.0-mainnet-beta-mac.zip 62fd69f4f8b87fdb10588c5127f3786f3fca653550bd2624ca62be8d7390f4cb peach-wallet-desktop-0.5.0-mainnet-beta-x86_64.AppImage e50ee596399b9b963d9522102126486841339c380acecd659e79a893fa1ee56d peach-wallet-desktop-0.5.0-mainnet-beta.dmg 42ad9439feaef7889b8f44ed30d125e8d210ad41be814b0f11e35e37013635bc peach-wallet-desktop-0.5.0-mainnet-beta.exe 91589518785ca39a7b440d8da85dc50f25488917e3eab807184a075e680bb333 peach-wallet-desktop-setup-0.5.0-mainnet-beta.exe c1083353f4ee1b084d8aaeaa114fbc8101dbd8b8181136359ccecb7e44e25489 peach-wallet-desktop_0.5.0-mainnet-beta_amd64.deb
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.