v0.12.0 Highlights
- feat: Nostr Wallet Connect service
- feat: Circular Channel Rebalance tool
- feat: Battery saver detection and warning for Embedded LND
- feat: WIF private key import
- feat: Swaps: Add ability to scan addresses/invoices
- feat: show LSP and Swap purchase in
Activityview - feat: LND: Channel Paths for incoming payments
- feat: add support for new CLNRest connection string format
- feat: Embedded node: Express Graph Sync payment prompt
- enhancement: Display balances in payment method selection view
- enhancement: Add visual feedback when copying strings to clipboard
- enhancement: improved Cashu mint fund restoration
- design: Amounts displayed on generated invoices
What's Changed
- [icloud-backup] fix: exclude the storage from using iCloud backup by @shubhamkmr04 in #3370
- [icloud-backup] fix : sync keychain read options 'cloudSync' with write options by @shubhamkmr04 in #3376
- [icloud-backup] fix: migrate data to exclude
cloudSyncfor storage by @shubhamkmr04 in #3382 - [nwc-service] refactor: update NWC service loading icon (Nostrich → nwc-logo) by @ajaysehwal in #3398
- fix: initialize sponsor arrays to prevent undefined slice error by @ajaysehwal in #3399
- [nwc-service] fix: NWC health check for backends without node info support by @ajaysehwal in #3401
- [icloud-backup] fix: Migrating Swaps by @shubhamkmr04 in #3404
- [icloud-backup] fix: Change migration Key by @shubhamkmr04 in #3405
- [feat] fix: iCloud backup storage issue by @kaloudis in #3371
- [nwc-service] fix: LNDHub budget tracking by @ajaysehwal in #3406
- [nwc-service] refactor: execute payments in parallel instead of sequentially by @ajaysehwal in #3407
- [feat] Nostr Wallet Connect (NWC) service by @kaloudis in #3216
Full Changelog: v0.12.0-alpha4...v0.12.0-beta1
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.12.0-beta1.txt and manifest-v0.12.0-beta1.txt.sig are in the current directory) with:
gpg --verify manifest-v0.12.0-beta1.txt.sig manifest-v0.12.0-beta1.txt
You should see the following if the verification was successful:
gpg: Signature made Wed Dec 10 14:59:53 2025 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.12.0-beta1.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.
Android fingerprint
Users verifying the release on an Android device can check against the key fingerprint below using AppVerifier. This fingerprint can also be found on our website here.
SHA1: 32:06:3C:97:96:38:0D:99:EE:4A:CB:B8:1E:2A:6F:27:FD:66:8E:C1
SHA256: 2A:F8:E2:0A:C9:44:57:67:CB:D4:4E:D8:4D:BB:FC:33:C6:C9:82:48:89:7C:4F:84:3C:42:C2:76:5C:4A:D3:BA
Signature algorithm name: SHA256withRSA
Subject Public Key Algorithm: 2048-bit RSA key
Version: 3
External links
Android
Universal APK
arm64-v8a APK
Manifest
Manifest Signature