v13.0.2 Highlights:
- New default RGS (Rapid Gossip Sync) server
We rolled out our own RGS server at rgs.zeusln.com that provides graph updates every 15 minutes instead of every three hours. This should cut down on payment errors caused by stale fees and provide higher payment success rates for LDK users.
- Improved read from clipboard behavior
- Improved NFC support
- UI improvements
- Bug fixes
What's Changed
- refactor: some more negative positioning/margin hacks by @myxmaster in #3783
- enhancement: clipboard: re-read on foreground return, always show paste action by @kaloudis in #4049
- [Transifex] Updates for project ZEUS by @transifex-integration[bot] in #4066
- fix: handle LSP non-JSON responses and clear stale error state on invoice creation by @kaloudis in #4020
- chore(deps): bump fast-uri from 3.1.0 to 3.1.2 in /zeus_modules/@lightninglabs/lnc-core by @dependabot[bot] in #4069
- chore(deps): bump @babel/plugin-transform-modules-systemjs from 7.25.9 to 7.29.4 by @dependabot[bot] in #4071
- chore(deps): bump @babel/plugin-transform-modules-systemjs from 7.23.9 to 7.29.4 in /zeus_modules/@lightninglabs/lnc-rn by @dependabot[bot] in #4070
- [Transifex] Updates for project ZEUS by @transifex-integration[bot] in #4073
- fix(ui): use icon-only collapsed QR actions for node info URIs by @ajaysehwal in #4074
- fix: Onboarding: prevent swipe-back from clobbering an existing wallet by @kaloudis in #4068
- fix: CashuStore: don't auto-delete Lightning address when wiping Cashu data by @kaloudis in #4072
- config(connectivity): use platform-native reachability probes instead of Cloudflare by @kaloudis in #4080
- docs: require proof-of-work evidence from first-time contributors by @kaloudis in #4083
- test: add unit tests for ClaimTransaction model by @shubhamkmr04 in #4061
- ui: Set explicit animation duration for transitions by @kaloudis in #4050
- chore(deps-dev): bump protobufjs-cli from 1.1.1 to 1.2.1 by @dependabot[bot] in #4087
- chore(deps): bump @protobufjs/utf8 from 1.1.0 to 1.1.1 in /zeus_modules/@lightninglabs/lnc-core by @dependabot[bot] in #4088
- config: new default RGS server: rgs.zeusln.com by @kaloudis in #4062
- chore(deps): bump @protobufjs/utf8 from 1.1.0 to 1.1.1 in /zeus_modules/@lightninglabs/lnc-rn by @dependabot[bot] in #4090
- [Transifex] Updates for project ZEUS by @transifex-integration[bot] in #4091
- refactor/deps: extract SigningUtils and replace elliptic by @myxmaster in #4063
- [Transifex] Updates for project ZEUS by @transifex-integration[bot] in #4093
- deps: upgrade to React Native v0.85.3 by @kaloudis in #4089
- chore(deps): bump @getalby/sdk from 5.1.2 to 8.0.1 by @ajaysehwal in #4075
- [Transifex] Updates for project ZEUS by @transifex-integration[bot] in #4098
- fix(ui): align sync percentage value in circular progress center by @ajaysehwal in #4097
- fix(lightning-address): resolve switch lockup caused by empty Keychain write by @kaloudis in #4100
- fix(channels): show Online/Offline filter labels using general locales keys by @ajaysehwal in #4104
- enhancement: LDK: wait for node readiness before fetching startup data by @kaloudis in #4101
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.0.2.txt and manifest-v13.0.2.txt.sig are in the current directory) with:
gpg --verify manifest-v13.0.2.txt.sig manifest-v13.0.2.txt
You should see the following if the verification was successful:
gpg: Signature made Tue May 5 13:10:29 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.0.2.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