v0.10.0-alpha4
Pre-release
In this build
- Tools: export Activity CSVs
- ZEUS Pay: ability to delete addresses
- Settings optimizations
- Bug fixes
v0.10.0 Highlights
- Renewable channels
- NWC client support
- Embedded LND: v0.18.5-beta
- New share button (share ZEUS QR images)
- Activity: highlight filter icon when filters active
- Developer tools
- chantools: sweepremoteclosed
What's Changed
- Convert getSettings() and updateNodeProperties() to arrow functions by @myxmaster in #2850
- [Transifex] Updates for project ZEUS by @transifex-integration in #2849
- [Transifex] Updates for project ZEUS by @transifex-integration in #2852
- Add option to set payments timeout for CLNRest by @sha-265 in #2846
- Fix require cycle in MigrationUtils by @myxmaster in #2854
- [Transifex] Updates for project ZEUS by @transifex-integration in #2853
- Activity filter memo and maximum amount by @Mayank2808sharma in #2807
- [Transifex] Updates for project ZEUS by @transifex-integration in #2855
New Contributors
- @Mayank2808sharma made their first contribution in #2807
Full Changelog: v0.10.0-alpha3...v0.10.0-alpha4
New Contributors
- @pony-montana made their first contribution in #2795
Full Changelog: v0.9.5...v0.10.0-alpha4
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.10.0-alpha4.txt and manifest-v0.10.0-alpha4.txt.sig are in the current directory) with:
gpg --verify manifest-v0.10.0-alpha4.txt.sig manifest-v0.10.0-alpha4.txt
You should see the following if the verification was successful:
gpg: Signature made Fri Feb 21 14:59:01 2025 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.10.0-alpha4.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.
