A mobile Bitcoin wallet fit for the gods. ⚡️ Est. 563345
Full Changelog: https://github.com/ZeusLN/zeus/compare/v0.8.3...v0.8.4
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.4.txt
and manifest-v0.8.4.txt.sig
are in the current directory) with:
gpg --verify manifest-v0.8.4.txt.sig manifest-v0.8.4.txt
You should see the following if the verification was successful:
gpg: Signature made Fri May 3 21:03:51 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.8.4.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.
Universal APK arm64-v8a APK Manifest Manifest Signature
Full Changelog: https://github.com/ZeusLN/zeus/compare/v0.8.3...v0.8.4-rc2
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.4-rc2.txt
and manifest-v0.8.4-rc2.txt.sig
are in the current directory) with:
gpg --verify manifest-v0.8.4-rc2.txt.sig manifest-v0.8.4-rc2.txt
You should see the following if the verification was successful:
gpg: Signature made Fri May 3 15:40:14 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.8.4-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.
Universal APK arm64-v8a APK Manifest Manifest Signature
Full Changelog: https://github.com/ZeusLN/zeus/compare/v0.8.3...v0.8.4-rc1
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.4-rc1.txt
and manifest-v0.8.4-rc1.txt.sig
are in the current directory) with:
gpg --verify manifest-v0.8.4-rc1.txt.sig manifest-v0.8.4-rc1.txt
You should see the following if the verification was successful:
gpg: Signature made Wed May 1 11:21:55 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.8.4-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.
Universal APK arm64-v8a APK Manifest Manifest Signature
Full Changelog: https://github.com/ZeusLN/zeus/compare/v0.8.3...v0.8.4-beta3
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.4-beta3.txt
and manifest-v0.8.4-beta3.txt.sig
are in the current directory) with:
gpg --verify manifest-v0.8.4-beta3.txt.sig manifest-v0.8.4-beta3.txt
You should see the following if the verification was successful:
gpg: Signature made Sun Apr 28 13:57:18 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.8.4-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.
Universal APK arm64-v8a APK Manifest Manifest Signature
Full Changelog: https://github.com/ZeusLN/zeus/compare/v0.8.3...v0.8.4-beta2
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.4-beta2.txt
and manifest-v0.8.4-beta2.txt.sig
are in the current directory) with:
gpg --verify manifest-v0.8.4-beta2.txt.sig manifest-v0.8.4-beta2.txt
You should see the following if the verification was successful:
gpg: Signature made Fri Apr 19 12:56:42 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.8.4-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.
Universal APK arm64-v8a APK Manifest Manifest Signature
Full Changelog: https://github.com/ZeusLN/zeus/compare/v0.8.3...v0.8.4-beta1
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.4-beta1.txt
and manifest-v0.8.4-beta1.txt.sig
are in the current directory) with:
gpg --verify manifest-v0.8.4-beta1.txt.sig manifest-v0.8.4-beta1.txt
You should see the following if the verification was successful:
gpg: Signature made Fri Apr 19 12:56:42 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.8.4-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.
Universal APK arm64-v8a APK Manifest Manifest Signature
Full Changelog: https://github.com/ZeusLN/zeus/compare/v0.8.2...v0.8.3
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.3.txt
and manifest-v0.8.3.txt.sig
are in the current directory) with:
gpg --verify manifest-v0.8.3.txt.sig manifest-v0.8.3.txt
You should see the following if the verification was successful:
gpg: Signature made Sun Apr 7 20:09:52 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.8.3.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.
Universal APK arm64-v8a APK Manifest Manifest Signature
Full Changelog: https://github.com/ZeusLN/zeus/compare/v0.8.2...v0.8.3-rc1
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.3-rc1.txt
and manifest-v0.8.3-rc1.txt.sig
are in the current directory) with:
gpg --verify manifest-v0.8.3-rc1.txt.sig manifest-v0.8.3-rc1.txt
You should see the following if the verification was successful:
gpg: Signature made Sun Apr 7 19:25:15 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.8.3-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.
Universal APK arm64-v8a APK Manifest Manifest Signature
Full Changelog: https://github.com/ZeusLN/zeus/compare/v0.8.2...v0.8.3-beta3
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.3-beta3.txt
and manifest-v0.8.3-beta3.txt.sig
are in the current directory) with:
gpg --verify manifest-v0.8.3-beta3.txt.sig manifest-v0.8.3-beta3.txt
You should see the following if the verification was successful:
gpg: Signature made Wed Apr 3 14:15:31 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.8.3-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.
Universal APK arm64-v8a APK Manifest Manifest Signature
Full Changelog: https://github.com/ZeusLN/zeus/compare/v0.8.2...v0.8.3-beta2
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.3-beta2.txt
and manifest-v0.8.3-beta2.txt.sig
are in the current directory) with:
gpg --verify manifest-v0.8.3-beta2.txt.sig manifest-v0.8.3-beta2.txt
You should see the following if the verification was successful:
gpg: Signature made Tue Apr 2 13:01:16 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.8.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.
Universal APK arm64-v8a APK Manifest Manifest Signature