v0.9.1-rc2
Pre-releasev0.9.1 Highlights
- LND: BOLT 11 blinded paths
- LND: spend full UTXOs
- LND: Inbound routing fees
- [Experimental] Rescans for external wallets
- Simplified open channel UX
- Linked contacts showing in
Channel
view - LNDHub: dismiss custodial warning
- POS: add option to default to
Keypad
view - View on-chain address list
What's Changed
- Bug fix: Lightning payments: last hop selection + circular rebalancing
- SendingLighting: show Try Again button on non-payment errors
Full Changelog: v0.9.1-rc1...v0.9.1-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.1-rc2.txt
and manifest-v0.9.1-rc2.txt.sig
are in the current directory) with:
gpg --verify manifest-v0.9.1-rc2.txt.sig manifest-v0.9.1-rc2.txt
You should see the following if the verification was successful:
gpg: Signature made Thu Oct 10 11:38:04 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.1-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.
External links
Android
Universal APK
arm64-v8a APK
Manifest
Manifest Signature