Skip to content

v0.9.2-rc1

Pre-release
Pre-release
Compare
Choose a tag to compare
@kaloudis kaloudis released this 09 Nov 15:20
· 222 commits to master since this release
v0.9.2-rc1
94b586b
This commit was signed with the committer’s verified signature. The key has expired.
kaloudis Evan Kaloudis
GPG key ID: AAC48DE8AB8DEE84
Expired
Learn about vigilant mode.

v0 9 2-rc1

In this build

  • Hardware wallet fixes

v0.9.2 Highlights

  • Activity: Export transaction history to spreadsheets
  • Improved BIP-353 and BOLT 12 support
    • Fix UI issues indicating BOLT 12 support
    • Fall back to BOLT 11 lightning address if not supported or not found
    • Support BIP-353 on-chain addresses
    • Support BOLT 12 offers encoded in BIP-21 URIs
  • Spooky theme
  • Settings: Payments: add 'Slide to Pay' threshold
  • Hardware wallet and external signer improvements
  • Bug fixes and misc enhancements

What's Changed

  • PSBT: BC-UR: use 'crypto-psbt' instead of 'bytes' formatting by @kaloudis in #2519

Full Changelog: v0.9.2-beta2...v0.9.2-rc1

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.9.2-rc1.txt and manifest-v0.9.2-rc1.txt.sig are in the current directory) with:

gpg --verify manifest-v0.9.2-rc1.txt.sig manifest-v0.9.2-rc1.txt

You should see the following if the verification was successful:

gpg: Signature made Fri Nov  8 23:22:31 2024 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.9.2-rc1.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

ZEUS documentation
PGP Key

Android

Universal APK
arm64-v8a APK
Manifest
Manifest Signature

iOS

Apple TestFlight
IPA

Contributors

kaloudis
Assets 10
Loading