v13.2.0 Highlights:
- LDK: support for 24-word seed phrases
- Embedded LND v0.21.2-beta
- Cashu CDK upgrade (Minibits compatibility)
- Privacy: set custom Mempool instances
- Security hardening
- Bug fixes
What's Changed
- stores: clear stale ZEUS Pay auth cache on node switch by @kaloudis in #4415
- fix(security): purge orphaned key material on wallet deletion and wipe by @kaloudis in #4328
- [Transifex] Updates for project ZEUS by @transifex-integration[bot] in #4425
- LSPS1/LSPS7 order screens: fix cleared amount fields re-rendering as 0 and doubled background on gradient themes by @kaloudis in #4396
- fix(nwc): keep sign_message off full-access by default by @ajaysehwal in #4411
- Privacy: configurable mempool instance by @kaloudis in #4227
- [Transifex] Updates for project ZEUS by @transifex-integration[bot] in #4428
- LSPS1: refetch service info on focus after stacked instance wipes store by @kaloudis in #4427
- [Transifex] Updates for project ZEUS by @transifex-integration[bot] in #4429
- chore: bump CDK to 0.17.4; drop npubcash quote-key marker workaround by @kaloudis in #4424
- fix(lnc): route payment results through handlePayment on every path by @kaloudis in #4331
- fix: show errors on Zeus Pay Plus screen by @ajaysehwal in #4430
- Cashu: probe multi-mint melt quotes only until capacity covers the payment by @kaloudis in #4369
- fix: payment timeout races on LND REST, CLNRest, LndHub, and Tor by @kaloudis in #4306
- views: ZeusPayPlus: route settings gear to NWC address settings by @kaloudis in #4432
- ZEUS Pay: retire Zaplocker onboarding by @kaloudis in #4419
Full Changelog: v13.2.0-alpha1...v13.2.0-beta1
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-v13.2.0-beta1.txt and manifest-v13.2.0-beta1.txt.sig are in the current directory) with:
gpg --verify manifest-v13.2.0-beta1.txt.sig manifest-v13.2.0-beta1.txt
You should see the following if the verification was successful:
gpg: Signature made Tue Aug 18 13:04:48 2026 EDT
gpg: using RSA key 96C225207F2137E278C31CF7AAC48DE8AB8DEE84
gpg: issuer "zeusln@tutanota.com"
gpg: Good signature from "Zeus LN <zeusln@tutanota.com>"
gpg: aka "ZEUS Support <support@zeusln.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-v13.2.0-beta1.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
arm64-v8a APK
Universal APK
Manifest
Manifest Signature