v0.9.0 Highlights

Our brand new Purchase channels in advance service,
A new interface for Core Lighting users: CLNRest, which is officially supported by the Core Lightning team
Hardware wallet / signing device support, allowing users to craft on-chain transactions, and open and close channels to and from popular hardware wallets such as:
- Coldcard Q
- Foundation Passport
- Seedsigner
- Krux
- Keystone Pro 3
- and many others
Watch-only account import (xpub)
Batch channel opens + transactions
Close channels to external addresses
Pending HTLCs view
A new swipe to pay component for invoices >= 10,000 sats
A new layout that makes for quicker one-handed invoice scanning
A new, more performant camera

What's Changed

[bug fix] LND (REST): incorrectly displayed failed payment by @kaloudis in #2289
CLNRest: show indicator on payment received by @kaloudis in #2291
CLNRest: performance improvements using sql query by @niteshbalusu11 in #2290
Contacts: Added Bolt12 offers by @shubhamkmr04 in #2288

Full Changelog: v0.9.0-beta1...v0.9.0-beta2

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

gpg --verify manifest-v0.9.0-beta2.txt.sig manifest-v0.9.0-beta2.txt

You should see the following if the verification was successful:

gpg: Signature made Thu Jul 18 12:43:43 2024 EDT
gpg:                using RSA key 96C225207F2137E278C31CF7AAC48DE8AB8DEE84
gpg:                issuer "[email protected]"
gpg: Good signature from "Zeus LN <[email protected]>" [ultimate]

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.0-beta2.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.