Skip to content

Releases: ZeusLN/zeus

v0.9.3-beta2

25 Nov 15:01
1265413
Compare
Choose a tag to compare
v0.9.3-beta2 Pre-release
Pre-release

v0 9 3-beta2

In this build

  • Channel UI improvements
    • New tab navigation for list view
    • SCIDs displayed on single channel view
  • Activity: download button hidden when list is empty
  • Activity: display year on events, when not current year
  • Android: NFC button hidden when not supported
  • ZEUS Pay enhancements
  • UX improvements

v0.9.3 Highlights

  • Channel reserve and SCID display
  • Bitcoin denominated amounts: display with spaces
  • ZEUS Pay: UX improvements
  • Bug fixes and enhancements

What's Changed

Full Changelog: v0.9.3-beta1...v0.9.3-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.3-beta2.txt and manifest-v0.9.3-beta2.txt.sig are in the current directory) with:

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

You should see the following if the verification was successful:

gpg: Signature made Mon Nov 25 00:15:54 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.3-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.

External links

ZEUS documentation
PGP Key

Android

Universal APK
arm64-v8a APK
Manifest
Manifest Signature

iOS

Apple TestFlight
IPA

v0.9.3-beta1

18 Nov 12:45
c3a9ed0
Compare
Choose a tag to compare
v0.9.3-beta1 Pre-release
Pre-release

v0 9 3-beta1

v0.9.3 Highlights

  • Channel reserve display
  • Bitcoin denominated amounts: display with spaces
  • ZEUS Pay: UX improvements
  • Bug fixes and enhancements

What's Changed

  • Only console.log Pending HTLCs if existing by @myxmaster in #2517
  • Use central storeInstances file by @myxmaster in #2518
  • [Transifex] Updates for project ZEUS by @transifex-integration in #2520
  • ZEUS Pay: new device check by @kaloudis in #2521
  • ZEUS-2523: Bug fix: Coins: external wallets marked hidden appear in tab nav by @kaloudis in #2524
  • Visualize channel reserve capacity by @kaloudis in #2522
  • Refactor: remove Sats component by @kaloudis in #2527
  • Receive: do not place 0 into amount input field by @kaloudis in #2528
  • BTC amount formatting: Decimals: remove commas and add spaces by @kaloudis in #2526
  • Channels: fixed aliases by @kaloudis in #2532
  • LND: coin control backwards compatibility by @kaloudis in #2533
  • [Transifex] Updates for project ZEUS by @transifex-integration in #2534
  • Channels: reserve updates by @kaloudis in #2535
  • deps: pull react-native-qrcode-local-image into zeus_modules by @kaloudis in #2537
  • ZEUS Pay: update relay sig when Nostr key updated by @kaloudis in #2536
  • Bump cross-spawn from 7.0.3 to 7.0.5 by @dependabot in #2538

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

gpg --verify manifest-v0.9.3-beta1.txt.sig manifest-v0.9.3-beta1.txt

You should see the following if the verification was successful:

gpg: Signature made Sun Nov 17 14:49:54 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.3-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.

External links

ZEUS documentation
PGP Key

Android

Universal APK
arm64-v8a APK
Manifest
Manifest Signature

iOS

Apple TestFlight
IPA

v0.9.2

11 Nov 15:40
dd87266
Compare
Choose a tag to compare

v0 9 2

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.1...v0.9.2

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

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

You should see the following if the verification was successful:

gpg: Signature made Sun Nov 10 09:43:34 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.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

F-Droid
Google Play

iOS

IPA

Apple App Store

v0.9.2-rc2

10 Nov 14:06
ed8c739
Compare
Choose a tag to compare
v0.9.2-rc2 Pre-release
Pre-release

v0 9 2-rc2

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.

External links

ZEUS documentation
PGP Key

Android

Universal APK
arm64-v8a APK
Manifest
Manifest Signature

iOS

Apple TestFlight
IPA

v0.9.2-rc1

09 Nov 15:20
94b586b
Compare
Choose a tag to compare
v0.9.2-rc1 Pre-release
Pre-release

v0 9 2-rc1

In this build

  • Hardware wallet fixes

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

  • PSBT: BC-UR: use 'crypto-psbt' instead of 'bytes' formatting by @kaloudis in #2519

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

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

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

You should see the following if the verification was successful:

gpg: Signature made Fri Nov  8 23:22:31 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-rc1.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

ZEUS documentation
PGP Key

Android

Universal APK
arm64-v8a APK
Manifest
Manifest Signature

iOS

Apple TestFlight
IPA

v0.9.2-beta2

06 Nov 13:44
a415bb3
Compare
Choose a tag to compare
v0.9.2-beta2 Pre-release
Pre-release

v0 9 2-beta2

In this build

  • External account signing fixes
  • Seedsigner Passport support fixes

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
  • Bug fixes and misc enhancements

What's Changed

  • External account workflow fixes by @kaloudis in #2512
  • SetWalletPicture: Fix Locale by @shubhamkmr04 in #2514
  • [Transifex] Updates for project ZEUS by @transifex-integration in #2513
  • [Transifex] Updates for project ZEUS by @transifex-integration in #2515

Full Changelog: v0.9.2-beta1...v0.9.2-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.2-beta2.txt and manifest-v0.9.2-beta2.txt.sig are in the current directory) with:

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

You should see the following if the verification was successful:

gpg: Signature made Wed Nov  6 08:35:01 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-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.

External links

ZEUS documentation
PGP Key

Android

Universal APK
arm64-v8a APK
Manifest
Manifest Signature

iOS

Apple TestFlight
IPA

v0.9.2-beta1

04 Nov 13:07
3a66a61
Compare
Choose a tag to compare
v0.9.2-beta1 Pre-release
Pre-release

v0 9 2-beta1

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
  • Bug fixes and misc enhancements

What's Changed

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

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

You should see the following if the verification was successful:

gpg: Signature made Sat Nov  2 20:46:36 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.2-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.

External links

ZEUS documentation
PGP Key

Android

Universal APK
arm64-v8a APK
Manifest
Manifest Signature

iOS

Apple TestFlight
IPA

v0.9.1

14 Oct 13:08
773c51b
Compare
Choose a tag to compare

v0 9 1

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

  • [Transifex] Updates for project ZEUS by @transifex-integration in #2360
  • Bump elliptic from 6.5.4 to 6.5.7 in /zeus_modules/@lightninglabs/lnc-core by @dependabot in #2361
  • Bump micromatch from 4.0.5 to 4.0.8 in /zeus_modules/@lightninglabs/lnc-rn by @dependabot in #2362
  • handleAnything: Fix lnaddress with onion domain by @shubhamkmr04 in #2346
  • Settings: Flow LSP: request Simple Taproot Channels by default by @kaloudis in #1999
  • ContactStore by @shubhamkmr04 in #2283
  • Bump webpack from 5.76.0 to 5.94.0 in /zeus_modules/@lightninglabs/lnc-core by @dependabot in #2385
  • Link Channel to the stored contacts by @shubhamkmr04 in #2299
  • Bump micromatch from 4.0.5 to 4.0.8 in /zeus_modules/@lightninglabs/lnc-core by @dependabot in #2386
  • Bump micromatch from 4.0.7 to 4.0.8 by @dependabot in #2387
  • Send: Using ContactStore to fetch contacts by @shubhamkmr04 in #2376
  • Loading contacts only when the wallet is connecting by @shubhamkmr04 in #2393
  • Sending Lightning: always display Try Again button on error by @kaloudis in #2381
  • Open Channel view enhancements by @kaloudis in #2348
  • SendingLightning: Display payment paths after successful lightning payment by @shubhamkmr04 in #2345
  • [Transifex] Updates for project ZEUS by @transifex-integration in #2383
  • ZEUS-2382: Channels: clean up capacity labels by @kaloudis in #2388
  • ZEUS-2189: Node Configuration: some buttons should be labels by @kaloudis in #2366
  • Embedded LND: v0.18.3-beta-zeus by @kaloudis in #2413
  • POS: Option to change default view by @shubhamkmr04 in #2395
  • Add modal to dismiss custodial wallet warning by @shubhamkmr04 in #2394
  • Display Notes on Activity view by @shubhamkmr04 in #2292
  • [Transifex] Updates for project ZEUS by @transifex-integration in #2412
  • Bump serve-static from 1.15.0 to 1.16.2 by @dependabot in #2418
  • [Transifex] Updates for project ZEUS by @transifex-integration in #2417
  • Bump serve-static from 1.15.0 to 1.16.2 in /zeus_modules/@lightninglabs/lnc-rn by @dependabot in #2419
  • ZEUS-2371: LND v0.18.3: blinded paths for BOLT 11 by @kaloudis in #2414
  • [Transifex] Updates for project ZEUS by @transifex-integration in #2420
  • [Transifex] Updates for project ZEUS by @transifex-integration in #2424
  • ZEUS-2396: External accounts: don't pass in preferred address type on new address call by @kaloudis in #2426
  • Embedded Node: Optimize Neutrino Peers: Asia by @kaloudis in #2427
  • Inbound routing fees by @shubhamkmr04 in #2354
  • [Transifex] Updates for project ZEUS by @transifex-integration in #2428
  • [Transifex] Updates for project ZEUS by @transifex-integration in #2431
  • [Transifex] Updates for project ZEUS by @transifex-integration in #2432
  • [Transifex] Updates for project ZEUS by @transifex-integration in #2434
  • Error screen redesign by @kaloudis in #2105
  • Close Channel: Force Close: fee rate fix by @kaloudis in #2429
  • ZEUS-2106: LND: spend entire UTXO in on-chain TX by @kaloudis in #2416
  • HWW/External accounts: rescan for existing funds by @kaloudis in #2307
  • [Transifex] Updates for project ZEUS by @transifex-integration in #2439
  • Bug Fix: Prevent Currency input to display '0' when it is empty by @shubhamkmr04 in #2438
  • Import Account: make count of addresses to generate user configurable by @kaloudis in #2440
  • New screen: On-chain addresses by @myxmaster in #2242
  • [Transifex] Updates for project ZEUS by @transifex-integration in #2442
  • [Transifex] Updates for project ZEUS by @transifex-integration in #2446
  • Fix default inbound fees bug by @shubhamkmr04 in #2448
  • Receive: Blinded Paths: turn off and disable AMP and Route Hints by @kaloudis in #2450
  • Lockscreen: include back button when in POS mode by @kaloudis in #2449
  • Nostr: new default relays by @kaloudis in #2454
  • [bug fix] SetFeesForm: allow iOS users to input negative amounts for inbound fees by @kaloudis in #2457
  • PaymentRequest: Handling payment calls from separate functions by @shubhamkmr04 in #2459
  • ImportingAccount: add loading indicator by @kaloudis in #2456
  • Version bump: v0.9.1 by @kaloudis in #2462

Full Changelog: v0.9.0...v0.9.1

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

gpg --verify manifest-v0.9.1.txt.sig manifest-v0.9.1.txt

You should see the following if the verification was successful:

gpg: Signature made Thu Oct 10 14:51:19 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.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

F-Droid
Google Play

iOS

IPA

Apple App Store

v0.9.1-rc2

10 Oct 15:45
31168d3
Compare
Choose a tag to compare
v0.9.1-rc2 Pre-release
Pre-release

v0 9 1-rc2

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

ZEUS documentation
PGP Key

Android

Universal APK
arm64-v8a APK
Manifest
Manifest Signature

iOS

Apple TestFlight
IPA

v0.9.1-rc1

10 Oct 13:03
56d05b9
Compare
Choose a tag to compare
v0.9.1-rc1 Pre-release
Pre-release

v0 9 1-rc1

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

  • Nostr: new default relays by @kaloudis in #2454
  • [bug fix] SetFeesForm: allow iOS users to input negative amounts for inbound fees by @kaloudis in #2457
  • PaymentRequest: Handling payment calls from separate functions by @shubhamkmr04 in #2459
  • ImportingAccount: add loading indicator by @kaloudis in #2456

Full Changelog: v0.9.1-beta2...v0.9.1-rc1

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

gpg --verify manifest-v0.9.1-rc1.txt.sig manifest-v0.9.1-rc1.txt

You should see the following if the verification was successful:

gpg: Signature made Wed Oct  9 16:39:00 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-rc1.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

ZEUS documentation
PGP Key

Android

Universal APK
arm64-v8a APK
Manifest
Manifest Signature

iOS

Apple TestFlight
IPA