In this build
- Fixed an issue that prevented some connections from initiating
- Fixed wallet identicons for Embedded LND and NWC wallets
- Fixed display of NWC invoice status on some platforms
v0.10.0 Highlights
- Renewable channels
- NWC client support
- Ability to create multiple Embedded LND 'node in the phone' wallets
- Ability to delete Embedded LND wallets
- Embedded LND: v0.18.5-beta
- New share button (share ZEUS QR images)
- Activity: highlight filter icon when filters active
- chantools: sweepremoteclosed
- Tools: Export Activity CSVs, Developer tools
- Activity: filter by max amount, memo, and note
- CLNRest: add payment timeout setting
- Receive: add advanced settings toggle
- ZEUS Pay: ability to delete addresses
What's Changed
Full Changelog: v0.10.0-alpha6...v0.10.0-alpha7
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-alpha7.txt and manifest-v0.10.0-alpha7.txt.sig are in the current directory) with:
gpg --verify manifest-v0.10.0-alpha7.txt.sig manifest-v0.10.0-alpha7.txt
You should see the following if the verification was successful:
gpg: Signature made Tue Mar 4 19:09:33 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-alpha7.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.