Skip to content

Releases: ZeusLN/zeus

v0.8.0-beta1

23 Oct 12:30
b9ec7e8
Compare
Choose a tag to compare
v0.8.0-beta1 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

What's Changed

Read more

v0.7.7

31 Jul 13:25
7ede236
Compare
Choose a tag to compare

Zeus-v0 7 7

v0.7.7 Highlights

  • Added confirmation process to delete a node connection
  • lnurlpay metadata display enhancements
  • Notes display enhancements
  • Bug fix: Camera: prevent scanning in background
  • Sparko interface now marked as deprecated

What's Changed

New Contributors

Full Changelog: v0.7.6...v0.7.7

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

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

You should see the following if the verification was successful:

gpg: Signature made Fri Jul 28 23:11:16 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.7.7.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

PGP Key

Android

Universal APK
arm64-v8a APK
Manifest
Manifest Signature

F-Droid
Google Play

iOS

Apple App Store

v0.7.7-beta2

24 Jul 13:00
84cca45
Compare
Choose a tag to compare
v0.7.7-beta2 Pre-release
Pre-release

v0.7.7 Highlights

  • Bug fix: Camera: prevent scanning in background
  • Added confirmation process to delete a node connection
  • lnurlpay metadata display enhancements
  • Notes display enhancements
  • Sparko interface now marked as deprecated

What's Changed since v0.7.7-beta1

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

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

You should see the following if the verification was successful:

gpg: Signature made Sun Jul 23 17:56:54 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.7.7-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

PGP Key

Android

Universal APK
arm64-v8a APK
Manifest
Manifest Signature

iOS

TestFlight

v0.7.7-beta1

21 Jul 13:09
6644683
Compare
Choose a tag to compare
v0.7.7-beta1 Pre-release
Pre-release

v0.7.7 Highlights

  • Bug fix: Camera: prevent scanning in background
  • Added confirmation process to delete a node connection
  • lnurlpay metadata display enhancements
  • Notes display enhancements
  • Sparko interface now marked as deprecated

What's Changed

New Contributors

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

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

You should see the following if the verification was successful:

gpg: Signature made Thu Jul 20 18:40:36 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.7.7-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

PGP Key

Android

Universal APK
arm64-v8a APK
Manifest
Manifest Signature

iOS

TestFlight

v0.7.6

15 Jun 10:49
03238d0
Compare
Choose a tag to compare

Zeus-v0 7 6

v0.7.6 Highlights

  • Notes: add ability to leave notes on transactions, payments, and invoices
  • Fiat exchange rates: add ability to choose between Zeus and Yadio as source
  • POS: associate existing payments with open orders + hide open orders
  • Bug fix: LNDHub: balance refresh
  • Bug fix: LCompatibility issues with CLN 23.05

What's Changed

New Contributors

Full Changelog: v0.7.5...v0.7.6

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

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

You should see the following if the verification was successful:

gpg: Signature made Tue Jun 13 07:28:49 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.7.6.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

PGP Key

Android

Universal APK
arm64-v8a APK
Manifest
Manifest Signature

F-Droid
Google Play

iOS

Apple App Store

v0.7.6-beta2

01 Jun 12:50
25ec7b9
Compare
Choose a tag to compare
v0.7.6-beta2 Pre-release
Pre-release

v0.7.6 Highlights

  • Notes: add ability to leave notes on transactions, payments, and invoices
  • POS: associate existing payments with open orders + hide open orders
  • Fiat exchange rates: add ability to choose between Zeus and Yadio as source
  • Bug fix: LNDHub: balance refresh
  • Bug fix: LCompatibility issues with CLN 23.05

What's Changed

  • Bug fix: iOS: FaceID login loop by @kaloudis in #1475
  • Bug fix: Core Lightning: display multiple channels per peer + update msat fields by @kaloudis in #1474

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

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

You should see the following if the verification was successful:

gpg: Signature made Wed May 31 22:04:42 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.7.6-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

PGP Key

Android

Universal APK
arm64-v8a APK
Manifest
Manifest Signature

iOS

TestFlight

v0.7.6-beta1

31 May 14:32
e214e9c
Compare
Choose a tag to compare
v0.7.6-beta1 Pre-release
Pre-release

v0.7.6 Highlights

  • Notes: add ability to leave notes on transactions, payments, and invoices
  • POS: associate existing payments with open orders + hide open orders
  • Fiat exchange rates: add ability to choose between Zeus and Yadio as source
  • Bug fix: LNDHub: balance refresh
  • Bug fix: LCompatibility issues with CLN 23.05

What's Changed

New Contributors

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

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

You should see the following if the verification was successful:

gpg: Signature made Tue May 30 15:31:57 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.7.6-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

PGP Key

Android

Universal APK
arm64-v8a APK
Manifest
Manifest Signature

iOS

TestFlight

v0.7.5

01 May 22:24
e1852e4
Compare
Choose a tag to compare

Zeus-v0 7 5

WARNING FOR iOS USERS: if you have not previously upgraded to the v0.7.4 general release, your settings will be cleared out and you'll have to reestablish your connections

v0.7.5 Highlights

  • Android: smaller release binaries
  • New camera w/ Samsung Galaxy support
  • New Payment Path view
  • Handle display of In-Flight payments
  • External link warning + prompt modal
  • NFC modal for Android
  • iOS: clear saved settings on uninstall
  • Settings: Display: Show all decimal places
  • Lightning Address: handle addresses hosted on Tor
  • Fix some views where inputs were getting cut off by the keyboard
  • LNURLw patch for fixed amounts
  • New currencies
    🇧🇴 Bolivian Boliviano (BOB)
    🇨🇷 Costa Rican Colón (CRC)
    🇬🇹 Guatemalan Quetzal (GTQ)
    🇳🇮 Nicaraguan Córdoba (NIO)
    🇵🇾 Paraguayan Guaraní (PYG)
    🇺🇾 Uruguayan Peso (UYU)

What's Changed

New Contributors

Full Changelog: v0.7.4...v0.7.5

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

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

You should see the following if the verification was successful:

gpg: Signature made Sun Apr 30 17:13:29 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.7.5.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

PGP Key

Android

Universal APK
arm64-v8a APK
Manifest
Manifest Signature

F-Droid
Google Play

iOS

Apple App Store

v0.7.5-beta2

26 Apr 14:25
78e03a6
Compare
Choose a tag to compare
v0.7.5-beta2 Pre-release
Pre-release

v0.7.5 Highlights

  • Android: smaller release binaries
  • New camera w/ Samsung Galaxy support
  • New Payment Path view
  • Handle display of In-Flight payments
  • External link warning + prompt modal
  • NFC modal for Android
  • iOS: clear saved settings on uninstall
  • Settings: Display: Show all decimal places
  • Lightning Address: handle addresses hosted on Tor
  • Fix some views where inputs were getting cut off by the keyboard
  • LNURLw patch for fixed amounts
  • New currencies
    🇧🇴 Bolivian Boliviano (BOB)
    🇨🇷 Costa Rican Colón (CRC)
    🇬🇹 Guatemalan Quetzal (GTQ)
    🇳🇮 Nicaraguan Córdoba (NIO)
    🇵🇾 Paraguayan Guaraní (PYG)
    🇺🇾 Uruguayan Peso (UYU)

What's Changed

  • views/Send: fix loading icon position + input issue by @kaloudis in #1445
  • views/Channel: Pending channel: show channel point by @kaloudis in #1446

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

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

You should see the following if the verification was successful:

gpg: Signature made Wed Apr 26 10:17:59 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.7.5-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

PGP Key

Android

Universal APK
arm64-v8a APK
Manifest
Manifest Signature

iOS

TestFlight

v0.7.5-beta1

21 Apr 15:46
6426042
Compare
Choose a tag to compare
v0.7.5-beta1 Pre-release
Pre-release

v0.7.5 Highlights

  • New camera w/ Samsung Galaxy support
  • New Payment Path view
  • Handle display of In-Flight payments
  • External link warning + prompt modal
  • NFC modal for Android
  • iOS: clear saved settings on uninstall
  • Settings: Display: Show all decimal places
  • Lightning Address: handle addresses hosted on Tor
  • Fix some views where inputs were getting cut off by the keyboard
  • LNURLw patch for fixed amounts
  • New currencies
    🇧🇴 Bolivian Boliviano (BOB)
    🇨🇷 Costa Rican Colón (CRC)
    🇬🇹 Guatemalan Quetzal (GTQ)
    🇳🇮 Nicaraguan Córdoba (NIO)
    🇵🇾 Paraguayan Guaraní (PYG)
    🇺🇾 Uruguayan Peso (UYU)

What's Changed

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

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

You should see the following if the verification was successful:

gpg: Signature made Thu Apr 20 16:27:07 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.7.5-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

PGP Key

Android

Universal APK
arm64-v8a APK
Manifest
Manifest Signature

iOS

TestFlight