Skip to content

Releases: ZeusLN/zeus

v0.8.1-beta3

13 Jan 15:51
e85a124
Compare
Choose a tag to compare
v0.8.1-beta3 Pre-release
Pre-release

v0 8 1-beta3

New in this build

  • Contact sharing via QR
  • Point of Sale keypad
  • Nostr contact lookup by NIP-05
  • Favorite contacts listed on Send view
  • ZEUS Pay auto-redeem improvements
  • Accessibility improvements
  • Bug fixes

v0.8.1 Highlights

  • Nostr contact import
  • Standalone Point of Sale w inventory management
  • Persistent LND (keep running LND even when ZEUS is closed, this enables instant ZEUS PAY zap redemptions, makes zapping faster, and paves the way for NWC) [Android only]
  • Node/account reordering
  • Improved expiry display
  • LND v0.17.3

What's Changed

Full Changelog: v0.8.1-beta2...v0.8.1-beta3

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

gpg --verify manifest-v0.8.1-beta3.txt.sig manifest-v0.8.1-beta3.txt

You should see the following if the verification was successful:

gpg: Signature made Sat Jan 13 10:48:01 2024 EST
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.8.1-beta3.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.8.1-beta2

04 Jan 20:00
35de8e7
Compare
Choose a tag to compare
v0.8.1-beta2 Pre-release
Pre-release

v0 8 1-beta2

v0.8.1 Highlights

  • Nostr contact import
  • Standalone Point of Sale w inventory management
  • Persistent LND (keep running LND even when ZEUS is closed, this enables instant ZEUS PAY zap redemptions, makes zapping faster, and paves the way for NWC) [Android only]
  • Node/account reordering
  • Improved expiry display
  • LND v0.17.3

What's Changed

  • LNC: fix supportsLightningSends permission check by @kaloudis in #1929
  • Fixed connection errors for old connection attempts being shown by @myxmaster in #1928

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

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

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

You should see the following if the verification was successful:

gpg: Signature made Thu Jan  4 14:51:24 2024 EST
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.8.1-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.8.1-beta1

03 Jan 20:55
cfd1951
Compare
Choose a tag to compare
v0.8.1-beta1 Pre-release
Pre-release

v0 8 1-beta1

v0.8.1 Highlights

  • Nostr contact import
  • Standalone Point of Sale w inventory management
  • Persistent LND (keep running LND even when ZEUS is closed, this enables instant ZEUS PAY zap redemptions, makes zapping faster, and paves the way for NWC) [Android only]
  • Node/account reordering
  • Improved expiry display
  • LND v0.17.3

What's Changed

New Contributors

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

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

You should see the following if the verification was successful:

gpg: Signature made Wed Jan  3 15:46:26 2024 EST
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.8.1-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.8.0

04 Dec 16:36
dde7620
Compare
Choose a tag to compare

hyper1

screenshots

v0.8.0 Highlights

  • Embedded LND node
  • OLYMPUS by ZEUS 0-conf channel service
  • ZEUS PAY self-custodial lightning addresses, using Zaplocker
  • Simple Taproot Channels
  • Contact book

What's Changed

Read more

v0.8.0-rc2

01 Dec 18:17
42708fa
Compare
Choose a tag to compare
v0.8.0-rc2 Pre-release
Pre-release

hyper1

screenshots

v0.8.0 Highlights

  • Embedded LND node
  • OLYMPUS by ZEUS 0-conf channel service
  • ZEUS PAY self-custodial lightning addresses, using Zaplocker
  • Simple Taproot Channels
  • Contact book

New in rc2

  • ZEUS PAY optimizations
  • Bug fixes

What's Changed

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

gpg --verify manifest-v0.8.0-rc2.txt.sig manifest-v0.8.0-rc2.txt

You should see the following if the verification was successful:

gpg: Signature made Fri Dec  1 13:07:40 2023 EST
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.8.0-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

Blog post
ZEUS documentation
PGP Key

Android

Universal APK
arm64-v8a APK
Manifest
Manifest Signature

iOS

Apple TestFlight

v0.8.0-rc1

30 Nov 16:31
868f9c0
Compare
Choose a tag to compare
v0.8.0-rc1 Pre-release
Pre-release

hyper1

screenshots

v0.8.0 Highlights

  • Embedded LND node
  • OLYMPUS by ZEUS 0-conf channel service
  • ZEUS PAY self-custodial lightning addresses, using Zaplocker
  • Simple Taproot Channels
  • Contact book

New in rc1

  • ZEUS PAY optimizations
  • LSP dynamic fee engine optimizations
  • New lightning animation for redeeming ZEUS PAY payments
  • Bug fixes

What's Changed

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

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

You should see the following if the verification was successful:

gpg: Signature made Thu Nov 30 11:24:09 2023 EST
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.8.0-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

Blog post
ZEUS documentation
PGP Key

Android

Universal APK
arm64-v8a APK
Manifest
Manifest Signature

iOS

Apple TestFlight

v0.8.0-beta5

28 Nov 13:44
87aaaa6
Compare
Choose a tag to compare
v0.8.0-beta5 Pre-release
Pre-release

hyper1

screenshots

v0.8.0 Highlights

  • Embedded LND node
  • OLYMPUS by ZEUS 0-conf channel service
  • ZEUS PAY self-custodial lightning addresses, using Zaplocker
  • Simple Taproot Channels
  • Contact book

New in beta5

  • LND v0.17.2
  • Dynamic LSP fees
  • Tap to enlarge QRs
  • New sending lightning animation
  • Express Graph Sync on by default
  • Updated default LN fee limits
  • Removed 50k onboarding limit
  • Onboarding improvements
  • UI improvements

What's Changed

Full Changelog: v0.8.0-beta4...v0.8.0-beta5

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

gpg --verify manifest-v0.8.0-beta5.txt.sig manifest-v0.8.0-beta5.txt

You should see the following if the verification was successful:

gpg: Signature made Mon Nov 27 20:03:56 2023 EST
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.8.0-beta5.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

iOS

Apple TestFlight

v0.8.0-beta4

15 Nov 00:19
5d8643f
Compare
Choose a tag to compare
v0.8.0-beta4 Pre-release
Pre-release

hyper1

screenshots

v0.8.0 Highlights

  • Embedded LND node
  • OLYMPUS by ZEUS 0-conf channel service
  • ZEUS PAY self-custodial lightning addresses, using Zaplocker
  • Simple Taproot Channels
  • Contact book

New in beta4

  • Embedded node: LND v0.17.1-beta
  • Bug fixes

What's Changed

Full Changelog: v0.8.0-beta3...v0.8.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.8.0-beta4.txt and manifest-v0.8.0-beta4.txt.sig are in the current directory) with:

gpg --verify manifest-v0.8.0-beta4.txt.sig manifest-v0.8.0-beta4.txt

You should see the following if the verification was successful:

gpg: Signature made Tue Nov 14 19:09:23 2023 EST
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.8.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

iOS

Apple TestFlight

v0.8.0-beta3

14 Nov 05:08
ae26c67
Compare
Choose a tag to compare
v0.8.0-beta3 Pre-release
Pre-release

hyper1

screenshots

v0.8.0 Highlights

  • Embedded LND node
  • OLYMPUS by ZEUS 0-conf channel service
  • ZEUS PAY self-custodial lightning addresses, using Zaplocker
  • Simple Taproot Channels
  • Contact book

New in beta3

  • New branding
  • Bug fixes
  • Korean language support

What's Changed

Full Changelog: v0.8.0-beta2...v0.8.0-beta3

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

gpg --verify manifest-v0.8.0-beta3.txt.sig manifest-v0.8.0-beta3.txt

You should see the following if the verification was successful:

gpg: Signature made Mon Nov 13 23:49:51 2023 EST
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.8.0-beta3.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

iOS

Apple TestFlight

v0.8.0-beta2

30 Oct 13:43
1ab82d3
Compare
Choose a tag to compare
v0.8.0-beta2 Pre-release
Pre-release

feature-image

v0.8.0 Highlights

  • Embedded LND node
  • OLYMPUS by ZEUS 0-conf channel service
  • ZEUS PAY self-custodial lightning addresses, using Zaplocker
  • Simple Taproot Channels
  • Contact book

New in beta2

  • ZEUS PAY: Replace attestation icons with colorblind-friendly versions
  • ZEUS PAY: Auto redeem enhancements
  • Channels pane: Added clock icon to Button in WalletHeader to indicate pending channels
  • AddressUtils: Lightning Address validation: handle uppercase chars
  • [Display bug] Seed: explicitly create two columns
  • [Bug fix] Balance sliders: Readded styles for vertical align
  • [Bug fix] Lightning Address Settings: Nostr relays: update relays_sig on relay deletion
  • [Bug fix] Sending Lightning: fix wrong display of Zaplocker warning

What's Changed

  • Bump crypto-js from 4.1.1 to 4.2.0 by @dependabot in #1800
  • Bump browserify-sign from 4.2.1 to 4.2.2 by @dependabot in #1805
  • Balance sliders: Readded styles for vertical align by @myxmaster in #1791
  • [Bug fix] Lightning Address Settings: Nostr relays: update relays_sig on relay deletion by @kaloudis in #1793
  • [Bug fix] Sending Lightning: fix wrong display of Zaplocker warning by @kaloudis in #1794
  • Channels pane: Added clock icon to Button in WalletHeader in case there are pending channels by @myxmaster in #1796
  • AddressUtils: Lightning Address validation: handle uppercase chars by @kaloudis in #1802
  • [Display bug] Seed: explicitly create two columns by @kaloudis in #1795
  • ZEUS PAY: Auto redeem enhancements by @kaloudis in #1797
  • ZEUS PAY: Replace attestation icons with colorblind-friendly versions by @myxmaster in #1808

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

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

You should see the following if the verification was successful:

gpg: Signature made Sun Oct 29 23:22:35 2023 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.8.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.

External links

Blog post
ZEUS documentation
PGP Key

Android

Universal APK
arm64-v8a APK
Manifest
Manifest Signature

iOS

Apple TestFlight