In this build

Small fix for the PSBT view, where values we not being updated on successive scans

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

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

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

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

You should see the following if the verification was successful:

gpg: Signature made Sun Nov 10 09:02:47 2024 EST
gpg:                using RSA key 96C225207F2137E278C31CF7AAC48DE8AB8DEE84
gpg:                issuer "[email protected]"
gpg: Good signature from "Zeus LN <[email protected]>"

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-rc2.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.