In this build
- Speed up transaction UX improvements
- Bug fixes
v0.9.4 Highlights
- Embedded Node: LND v0.18.4-beta
- Speed up transaction UX improvements
- CLNRest: fix display of destination addresses on txs
- Display keysend messages in Activity and Payment views
- Open Channel view: UI tabs for Connect Peer
- LND: optimize payment path calls after payments
- CLNRest: add ability to paste connection strings
- Channels: restore sort by Close Height
- Networking improvements
- Bug fixes
What's Changed
- ZEUS-2626: Lightning Address Settings: Notifications setting does not persist by @kaloudis in #2652
- ZEUS-2641: Activity: make send and receive inclusive of 0 by @kaloudis in #2651
- [Transifex] Updates for project ZEUS by @transifex-integration in #2650
- [Transifex] Updates for project ZEUS by @transifex-integration in #2661
- ZEUS-2629: Failed payment to invoices with route hints by @kaloudis in #2662
- ZEUS-2663: LND: update BumpFee params and UI by @kaloudis in #2664
- Wallet config: set config to inactive when copied by @kaloudis in #2665
- Version bump: v0.9.4-beta2 by @kaloudis in #2666
Full Changelog: v0.9.4-beta1...v0.9.4-beta2
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.4-beta2.txt and manifest-v0.9.4-beta2.txt.sig are in the current directory) with:
gpg --verify manifest-v0.9.4-beta2.txt.sig manifest-v0.9.4-beta2.txt
You should see the following if the verification was successful:
gpg: Signature made Thu Dec 19 13:19:17 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.4-beta2.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