In this build
- Embedded Node: LND v0.18.2-beta
- Express Graph Sync: optimizations
- Express Graph Sync: select server
- LND REST + LNC: add Network Info view
- CLNRest: Activity view optimizations
- bug fix: fix edge case where successful payments were marked as failed
- bug fix: Android: fix loading of unified invoices
- bug fix: Android: fix loading of accounts list and import functionality
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
- Embedded LND: Settings: add Custom Express Graph Sync server by @kaloudis in #2300
- [Transifex] Updates for project ZEUS by @transifex-integration in #2301
- [Transifex] Updates for project ZEUS by @transifex-integration in #2305
- [Enhancement] CLNRest select specific columns from bkpr_accountevents table by @newtonick in #2297
- [Enhancement] CLNRest convert /v1/listpays to /v1/sql by @newtonick in #2298
- Bump fast-xml-parser from 4.3.6 to 4.4.1 in /zeus_modules/@lightninglabs/lnc-rn by @dependabot in #2303
- Bump fast-xml-parser from 4.4.0 to 4.4.1 by @dependabot in #2308
- [Transifex] Updates for file locales/en.json in sw by @transifex-integration in #2335
- [Transifex] Updates for file locales/en.json in ru by @transifex-integration in #2334
- [Transifex] Updates for file locales/en.json in th by @transifex-integration in #2333
- [Transifex] Updates for file locales/en.json in zh_CN by @transifex-integration in #2332
- [Transifex] Updates for file locales/en.json in vi by @transifex-integration in #2331
- [Transifex] Updates for file locales/en.json in nl by @transifex-integration in #2330
- [Transifex] Updates for file locales/en.json in ro by @transifex-integration in #2329
- [Transifex] Updates for file locales/en.json in sv by @transifex-integration in #2328
- [Transifex] Updates for file locales/en.json in nb by @transifex-integration in #2327
- [Transifex] Updates for file locales/en.json in pl by @transifex-integration in #2326
- [Transifex] Updates for file locales/en.json in ja by @transifex-integration in #2325
- [Transifex] Updates for file locales/en.json in hr by @transifex-integration in #2324
- [Transifex] Updates for file locales/en.json in ko by @transifex-integration in #2323
- [Transifex] Updates for file locales/en.json in tr by @transifex-integration in #2322
- [Transifex] Updates for file locales/en.json in pt_BR by @transifex-integration in #2321
- [Transifex] Updates for file locales/en.json in he by @transifex-integration in #2320
- [Transifex] Updates for file locales/en.json in uk by @transifex-integration in #2319
- [Transifex] Updates for file locales/en.json in sl by @transifex-integration in #2318
- [Transifex] Updates for file locales/en.json in it by @transifex-integration in #2317
- [Transifex] Updates for file locales/en.json in fr by @transifex-integration in #2316
- [Transifex] Updates for file locales/en.json in de by @transifex-integration in #2315
- [Transifex] Updates for file locales/en.json in fi by @transifex-integration in #2314
- [Transifex] Updates for file locales/en.json in cs by @transifex-integration in #2313
- [Transifex] Updates for file locales/en.json in fa by @transifex-integration in #2312
- [Transifex] Updates for file locales/en.json in hu by @transifex-integration in #2311
- [Transifex] Updates for file locales/en.json in es by @transifex-integration in #2310
- [Transifex] Updates for file locales/en.json in el by @transifex-integration in #2309
- LND: Network Info by @shubhamkmr04 in #2304
Full Changelog: v0.9.0-beta3...v0.9.0-beta4
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-beta4.txt and manifest-v0.9.0-beta4.txt.sig are in the current directory) with:
gpg --verify manifest-v0.9.0-beta4.txt.sig manifest-v0.9.0-beta4.txt
You should see the following if the verification was successful:
gpg: Signature made Fri Aug 2 13:20:47 2024 EDT
gpg: using RSA key 96C225207F2137E278C31CF7AAC48DE8AB8DEE84
gpg: issuer "zeusln@tutanota.com"
gpg: Good signature from "Zeus LN <zeusln@tutanota.com>" [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-beta4.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
Blog post
ZEUS documentation
PGP Key
Android
Universal APK
arm64-v8a APK
Manifest
Manifest Signature