New in this build
- Invoice Settings: Display requested amount on invoice
- Embedded LND: Troubleshooting menu
- Bug fixes and enhancements
v0.9.3 Highlights
- Channel reserve display
- Bitcoin denominated amounts: display with spaces
- ZEUS Pay: UX improvements
- Bug fixes and enhancements
What's Changed
- [Transifex] Updates for project ZEUS by @transifex-integration in #2576
- [Transifex] Updates for project ZEUS by @transifex-integration in #2581
- Hide "RECEIVE VIA NFC" button while loading by @myxmaster in #2585
- Invoice model: Better htlc array check for keysend message by @myxmaster in #2583
- [Transifex] Updates for project ZEUS by @transifex-integration in #2586
- Improve channel tabs layout by @myxmaster in #2578
- Embedded LND: handle Long values by @kaloudis in #2574
- New invoice setting "Display requested amount on invoice" by @myxmaster in #2582
- Embedded node: add Troublshooting menu by @kaloudis in #2587
- Version bump: v0.9.3-beta3 by @kaloudis in #2590
Full Changelog: v0.9.3-beta2...v0.9.3-beta3
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 the keys that have signed this release if you haven't done so already:
gpg --keyserver hkps://keys.openpgp.org --recv-keys 96C225207F2137E278C31CF7AAC48DE8AB8DEE84
Once you have his PGP key you can verify the release (assuming manifest-v0.9.3-beta3.txt and manifest-v0.9.3-beta3.txt.sig are in the current directory) with:
gpg --verify manifest-v0.9.3-beta3.txt.sig manifest-v0.9.3-beta3.txt
You should see the following if the verification was successful:
gpg: Signature made Sun Dec 1 16:57:07 2024 EST
gpg: using RSA key 96C225207F2137E278C31CF7AAC48DE8AB8DEE84
gpg: issuer "zeusln@tutanota.com"
gpg: Good signature from "Zeus LN <zeusln@tutanota.com>"
That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:
cat manifest-v0.9.3-beta3.txt
One can use the shasum -a 256 <file name here> tool in order to re-compute the sha256 hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.
External links
Android
Universal APK
arm64-v8a APK
Manifest
Manifest Signature