v0.11.0 Highlights
- Experimental Cashu ecash wallet
- Swaps: LN -> on-chain, and vice versa
- Import and export wallet configs
- UTXO labeling
- Activity: filter for keysends
- CLN: support for generating Taproot addresses
- CLN: view closed channels
Notes:
- Cashu wallets are tied to Embedded LND wallets. Enable under Settings > Ecash
- Other wallet types can still sweep funds from Cashu tokens
- ZEUS Pay now supports Cashu address types. You can switch between Zaplocker, Cashu, and NWC mode but can only use one at a time.
What's Changed
- feat: export/import feature for wallet configs by @myxmaster in #2963
- [Transifex] Updates for project ZEUS by @transifex-integration in #3057
- [export-import-node-configs] updated filename, removed unneeded getter by @kaloudis in #3062
- feat: Add swap button to payment/send screens and prefill swap form by @kaloudis in #3060
- [feat] export/import feature for wallet configs by @kaloudis in #3059
- feat: UTXO labeling by @a-khushal in #2989
- [Transifex] Updates for project ZEUS by @transifex-integration in #3061
Full Changelog: v0.11.0-alpha5...v0.11.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-v0.11.0-beta1.txt
and manifest-v0.11.0-beta1.txt.sig
are in the current directory) with:
gpg --verify manifest-v0.11.0-beta1.txt.sig manifest-v0.11.0-beta1.txt
You should see the following if the verification was successful:
gpg: Signature made Mon May 26 21:09:34 2025 EDT
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.11.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
Universal APK
arm64-v8a APK
Manifest
Manifest Signature