Download Lattice Desktop

A wallet backup alone is not enough for rollback once the new per-chain peer settings are saved. The older node cannot read the new object-valued peer configuration. Returning to the older version requires the full backup made while the app and node were stopped; do not reuse the upgraded profile.

An older node may also lose remembered peer addresses when it encounters peerbook v2. That loss concerns remembered peers, not ledger corruption. Peer-format compatibility checks do not prove that arbitrary node data can be downgraded.

Continue only if you trust the source and have checked the download. For an unverified-developer warning or an alert that Apple cannot check the app:

1. Try opening Lattice from Applications once, then dismiss the warning.
2. Open System Settings → Privacy & Security. Scroll to Security and find the message about Lattice.
3. Choose Open Anyway for Lattice, authenticate if asked, and confirm Open.

This creates an exception for this app. If Open Anyway is unavailable, check Apple’s opening-app guidance or your Mac administrator.

Stop if macOS reports malware, says the app will damage your computer, or says it is damaged. Do not override those warnings.

Checksums, the project signature, and the public key will be linked here when the release is available.

• SHA256 checksums
• Project signature for the checksums
• Project public key

Compare the ZIP’s SHA256 with its entry in the release’s SHA256SUMS file. In Terminal, type shasum -a 256 (including a trailing space), drag the ZIP into Terminal, then press Return.

To authenticate the checksum file, use Minisign with the project’s public key. Confirm the key against a previously trusted copy or a separately trusted project source. Save the signature beside SHA256SUMS as SHA256SUMS.minisig, and the public key as lattice-releases.pub, then run this in that folder:

minisign -Vm SHA256SUMS -p lattice-releases.pub

A matching checksum shows that your ZIP matches the listed bytes. A valid project signature authenticates the checksums only to the key you trust. Neither is Apple notarization or a guarantee that the software is safe. If either check fails, do not open the app.

Linux packages are built for amd64 (x86-64) as .deb and AppImage files. Check your distribution and architecture in your system’s About settings. Both need glibc 2.35 or later. The .deb declares WebKitGTK 4.1, GTK 3 and SQLite dependencies; the AppImage bundles those libraries.

1. Choose a package. Use the .deb on a compatible Debian or Ubuntu system. The AppImage is a separate option; review its requirements below.
2. Install or open. Open the .deb with your system’s package installer and review its dependency prompts.
3. Open Lattice and set up your wallet. Follow the app’s create or import prompts and back up your recovery phrase. The node starts syncing when the app opens; mining is optional.

If a dependency is missing or your system blocks the app, stop and check the platform requirements. The installed .deb has passed startup and UI checks.

Linux packaging and requirements

Verification files are not available yet.

• SHA256 checksums
• Project signature for the checksums
• Project public key

Save SHA256SUMS, SHA256SUMS.minisig and lattice-releases.pub in the same folder as your download. Install Minisign, and confirm the public key against a previously trusted copy or a separately trusted project source before using it.

In that folder, authenticate the checksum file:

minisign -Vm SHA256SUMS -p lattice-releases.pub

Then run the command for the package you downloaded and compare its result with that filename’s entry in SHA256SUMS. For the .deb:

sha256sum Lattice_0.1.1_amd64.deb

For the AppImage:

sha256sum Lattice_0.1.1_amd64.AppImage

A checksum compares bytes; a project signature authenticates the checksum file only to the key you trust. Neither guarantees software safety. If either check fails, do not open the package.

Version 0.1.1 · amd64 (x86-64) · glibc 2.35 or later; FUSE mounting or extraction

The download is not available yet.

The AppImage bundles WebKitGTK 4.1, GTK 3 and SQLite. In your file manager’s Properties → Permissions, allow the verified AppImage to run as a program, then open it. Labels vary by desktop.

Normal opening needs working FUSE mounting and helper access. This build does not require the libfuse2 package. FUSE mounting has not been tested; the extracted AppImage UI has been tested.

If mounting is unavailable, extraction is an alternative. In a terminal in the download folder, after verifying the file:

chmod +x Lattice_0.1.1_amd64.AppImage
./Lattice_0.1.1_amd64.AppImage --appimage-extract
./squashfs-root/AppRun

Extraction creates a squashfs-root folder. Keep it to run AppRun again.

Verification files are not available yet.

• SHA256 checksums
• Project signature for the checksums
• Project public key

Compare the checksum for the AppImage, not the .deb. A checksum or signature does not guarantee software safety.

The Windows app runs its node in Windows Subsystem for Linux (WSL). It uses your default Linux distribution, which needs glibc 2.35 or later and SQLite; the repository lists Ubuntu 22.04 or later and Debian 12 or later.

1. Prepare WSL. Follow Microsoft’s WSL setup instructions. This may require administrator access and a restart. Open your default Linux distribution once to finish its setup, and ensure it meets the glibc and SQLite requirements above.
2. Check WebView2. The app also requires Microsoft’s WebView2 Runtime. The installer downloads WebView2 if it is missing, so an internet connection is needed for that step. You must set up WSL and its default distribution separately.
3. Install Lattice. Download the verified x64 .exe installer, open it, and follow the setup prompts. It is an NSIS installer. Read any Windows security warnings before deciding whether to proceed.
4. Open Lattice and set up your wallet. Follow the create or import prompts and back up your recovery phrase. The app starts its node in your default WSL distribution and shows sync progress. Mining is optional.

Microsoft’s WSL setup recipe requires Windows 10 version 2004 (build 19041) or later, or Windows 11. That is a WSL prerequisite, not a tested Lattice desktop support matrix. Compatibility checks used Windows Server 2025; desktop Windows versions do not yet have a formal test matrix. A malware alert is a reason to stop, not to bypass a protection.

Windows packaging and requirements

Verification files are not available yet.

• SHA256 checksums
• Project signature for the checksums
• Project public key

Save SHA256SUMS, SHA256SUMS.minisig and lattice-releases.pub in the same folder as your download. Install Minisign, and confirm the public key against a previously trusted copy or a separately trusted project source before using it.

In PowerShell in that folder, authenticate the checksum file:

minisign.exe -Vm SHA256SUMS -p lattice-releases.pub

Then calculate the installer’s hash and compare it with its entry in SHA256SUMS (letter case does not matter):

Get-FileHash -LiteralPath .\Lattice_0.1.1_x64-setup.exe -Algorithm SHA256

A matching checksum compares bytes; a project signature authenticates the checksum file only to the key you trust. Neither establishes Windows publisher trust or guarantees software safety. If either check fails, do not open the installer.