Download
Latest release: 2.4.3 Previous releases and changelog
Sparrow-LTC Desktop
Sparrow-LTC Desktop is the fully featured desktop application. For headless systems, use Sparrow-LTC Server below.
| Type | Link |
|---|---|
| macOS (Apple M-series) | Sparrow-LTC-2.4.3-aarch64.dmg |
| macOS (Intel) (11+) | Sparrow-LTC-2.4.3-x86_64.dmg |
| Windows Installer (10+) | Sparrow-LTC-2.4.3.msi |
| Windows Standalone (10+) | Sparrow-LTC-2.4.3.zip |
| Linux (Intel/AMD) (Ubuntu/Debian) | sparrowltcwallet_2.4.3-1_amd64.deb |
| Linux (Intel/AMD) (Redhat/CentOS) | sparrowltcwallet-2.4.3-1.x86_64.rpm |
| Linux (Intel/AMD) Standalone | sparrowltcwallet-2.4.3-x86_64.tar.gz |
| Linux (ARM64) (Ubuntu/Debian) | sparrowltcwallet_2.4.3-1_arm64.deb |
| Linux (ARM64) (Redhat/CentOS) | sparrowltcwallet-2.4.3-1.aarch64.rpm |
| Linux (ARM64) Standalone | sparrowltcwallet-2.4.3-aarch64.tar.gz |
| Manifest Signature | sparrowltc-2.4.3-manifest.txt.asc |
| Manifest | sparrowltc-2.4.3-manifest.txt |
Sparrow-LTC Server
Sparrow-LTC Server builds are intended for systems without displays (headless platforms). Note the .deb and .rpm packages install to /opt/sparrowltcserver.
| Type | Link |
|---|---|
| Linux (Intel/AMD) (Ubuntu/Debian) | sparrowltcserver_2.4.3-1_amd64.deb |
| Linux (Intel/AMD) (Redhat/CentOS) | sparrowltcserver-2.4.3-1.x86_64.rpm |
| Linux (Intel/AMD) Standalone | sparrowltcserver-2.4.3-x86_64.tar.gz |
| Linux (ARM64) (Ubuntu/Debian) | sparrowltcserver_2.4.3-1_arm64.deb |
| Linux (ARM64) (Redhat/CentOS) | sparrowltcserver-2.4.3-1.aarch64.rpm |
| Linux (ARM64) Standalone | sparrowltcserver-2.4.3-aarch64.tar.gz |
| Manifest Signature | sparrowltc-2.4.3-manifest.txt.asc |
| Manifest | sparrowltc-2.4.3-manifest.txt |
Verifying the Release
For all Litecoin software, it’s a particularly important security step to verify the release. This is done to ensure the installation file you download has not been compromised.
Sparrow-LTC 1.8.3 or later
If you have Sparrow-LTC 1.8.3 or later installed, this is simple to do using Sparrow-LTC itself. Just download the following 3 files to the same folder (for example, your Downloads folder):
- Manifest Signature: sparrowltc-2.4.3-manifest.txt.asc
- Manifest: sparrowltc-2.4.3-manifest.txt
- Your install file from the list above
Drag and drop any of these files onto Sparrow-LTC, and the Verify Download dialog will open and verify your download. You can also open the Verify Download dialog from the Tools menu.
| Signed By: |  Hector Chu <hectorchu@gmail.com> on Fri Apr 3 12:26:22 2026 WEST |
| Release Hash: | Matched manifest hash |
| Verified: | Ready to install Sparrow-LTC-2.4.3-aarch64.dmg |
You can also use this tool to verify other software, like Litecoin Core or the firmware for a hardware wallet.
Earlier releases
With earlier versions of Sparrow-LTC, you’ll need to have gpg or gpg2 installed on your system (see here for macOS or Windows, on Linux it’s preinstalled).
Once you’ve installed gpg, you’ll need to use the command line. You can do this by opening Terminal.app in macOS, or Start > Run > cmd in Windows.
First, import the keys that have signed this release (if you haven’t done so already, or if a previously imported key has expired):
curl https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x6ec371a844f2c48e | gpg --import
Once you have the required PGP keys, you can verify the release. Download sparrowltc-2.4.3-manifest.txt and sparrowltc-2.4.3-manifest.txt.asc from the table above to the same directory (for example, your Downloads directory). Then verify the manifest file with:
cd Downloads
gpg --verify sparrowltc-2.4.3-manifest.txt.asc
You should see the following if the verification was successful (your timezone may differ):
gpg: assuming signed data in 'sparrowltc-2.4.3-manifest.txt'
gpg: Signature made Fri 3 Apr 12:26:22 2026 WEST
gpg: using RSA key 7FE6094DCB3A76262EE4C6896EC371A844F2C48E
gpg: Good signature from "Hector Chu <hectorchu@gmail.com>" [ultimate]
Note that you may get a message similar to the following:
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
This simply means that you have not explicitly marked the public key as trusted in your own instance of GPG. In this case it is good practice to check the key against other sources, for example https://keybase.io/craigraw (click on the link next to the key icon to see the full public key). You can read more about validating keys in the GnuPG Privacy Handbook.
You have now verified the signature of the manifest file, which ensures integrity and authenticity of the manifest file - not the binaries!
Next, depending on your operating system, you must re-compute the sha256 hash of the archive with shasum -a 256 <filename>.
First, download the installation for your operating system (if you haven’t done so already).
Then follow the steps below to compare it with the corresponding one in the manifest file, and ensure they match exactly.
For example:
macOS
shasum --check sparrowltc-2.4.3-manifest.txt --ignore-missing
Sparrow-LTC-2.4.3.dmg: OK
Note: Older versions of macOS (pre v11) don’t support --ignore-missing. You can leave it out and ignore the missing files reported.
Linux
sha256sum --check sparrowltc-2.4.3-manifest.txt --ignore-missing
sparrowltcwallet_2.4.3-1_amd64.deb: OK
Windows
CertUtil -hashfile Sparrow-LTC-2.4.3.msi SHA256 | findstr /v "hash"
Compare result to the appropriate value in sparrowltc-2.4.3-manifest.txt!
With all these steps complete you can be certain of the integrity of your download and can proceed to install!
If you are still struggling, watch this tutorial which covers the same process on macOS. There are also written tutorials for Windows and Ubuntu.
Installation
Sparrow-LTC should be installed as normal for your operating system.
Note that on QubesOS, you will need to run the following command first:
sudo mkdir /usr/share/desktop-directories/
Upgrading
Sparrow-LTC stores all wallets and settings separately from the installation in the Sparrow-LTC home folder. It is safe to uninstall Sparrow-LTC, or to upgrade the installation without risking your data. Make sure to close the application first.