Cuvex Desktop · Linux · x64

1.0.0-beta.9.13

Your download, instructions and integrity check in one place.

Published on 2026-11-12 · UTC · AppImage · 143.5 MiB

Download ↓Check your download, step by step. →

Cuvex-Desktop-1.0.0-beta.9.13-Linux-x64.AppImage

Release notes

Details / what's new in version 1.0.0-beta.9.13

Guided chat payments and historical cryptograms

Payments with context

Contact, BTC and fiat conversion remain visible, with live UTXO amount and estimated fee coverage.
The requested amount and destination are protected; inline review and guided signing through BIT, Mirror or QR reception.

Compatibility and continuity

Binary preservation of historical cryptograms, including M-1, 25/50-byte metadata and older mobile attachments. Format recognition does not verify authenticity.
The open chat and contact are retained when navigating. Transaction states use both text and colour.

Use and updating

Beta release for testers. Create an encrypted full backup before updating and check the workflows with your devices before relying on this release. Package checks do not replace physical testing.

Beta requirements and compatibility

Cuvex BIT connects directly to Cuvex Desktop over USB-C. To fully operate Cuvex Original with Desktop, you need Cuvex Mirror on a compatible NFC smartphone, linked to your computer over Bluetooth. Mirror reads and writes NFC cards; sensitive operations are reviewed and authorized on your Cuvex device.

Installation

Before updating, create an encrypted full backup in Desk and close the app. Keep the backup and its password separately.
Download the file for your architecture and compare its SHA-256 with the value on this release page before opening it.
Give the AppImage permission to run and open it as your normal user. Install FUSE 2 if your distribution requires it; do not run as root or use --no-sandbox.
Allow Bluetooth or camera access only when using the relevant workflow. For NFC, open Mirror on Android and follow pairing; for BIT, use a USB-C data cable.

SHA-256 confirms that the file matches the published download. It does not replace verification of the manufacturer’s signature or establish compatibility with your device.

Cuvex ecosystem features

This section describes the Cuvex ecosystem. For the exact features and requirements of the file you are downloading, refer to this version’s release notes and instructions.

Cuvex Desk brings your tools together on Windows, macOS and Linux. In normal use, you review and authorize sensitive operations on your Cuvex. Mirror supplies your phone’s NFC; local decryption is reserved for emergencies.

Organize your cryptograms

Link Original NFC cards, import .bin backups or receive cryptograms from BIT over USB-C. Keep their records, aliases and metadata in an encrypted local vault.

Bitcoin through WOW

Monitor balances and activity through public descriptors, prepare PSBTs, select UTXOs and organize labels. View BTC amounts or their fiat reference, review fees and use Send all when appropriate. Signing and review remain on the device.

Review and sign on your device

Exchange PSBTs with BIT over USB-C or use a compatible export. Check recipients, amounts, change and fees on the device; Desktop verifies the signature and asks for confirmation before broadcasting.

Verified NFC copies

Read, link and clone compatible cards from Desktop with Cuvex Mirror. Before writing, the app checks the destination, protects recognized Cuvex cryptograms and verifies the write by reading it back. Use a dedicated 8K card for PSBT and always retain the original.

Encrypted local vault and backups

Protect access with a password and create an encrypted global backup of your cryptograms, WOWs, labels, drafts and settings. Chat is excluded from this backup.

Firmware for Original and BIT

Check for and download official firmware in Desktop. Original receives it over Bluetooth and BIT over USB-C. Keep the connection stable and check the final version on the device screen.

NFC from your phone

Desk directs the operation while Mirror connects the card to your computer over a local encrypted link. Confirm the session with the PIN and QR, then follow the reading or writing instructions on both screens.

Encrypted chat and QR reading

Access Cuvex encrypted chat and your computer’s QR reading tools. Chat needs its connection services and is excluded from the global backup. Mirror uses the camera to pair the session.

An emergency route. Not a shortcut.

A lost or damaged Cuvex should not leave you without an alternative when you cannot wait for another device. Desk can locally decrypt a compatible non-biometric copy if you retain the passwords required by the cryptogram.

Only when there is no safer alternative.

This feature exposes the secret on your computer, outside the isolation of Cuvex hardware. Malware, a malicious administrator or a screen capture can compromise it even without Internet access. Neither the timer nor disconnection guarantees absolute safety. Decryption does not take place on this website or through support.

What you must retain

You need the complete, compatible cryptogram and the password or number of passwords required by its multisignature scheme. It cannot recover forgotten passwords or rebuild lost data. Cryptograms protected by biometrics require the compatible device and cannot be decrypted on the PC.

Before, during and after

Disconnect the computer from the Internet and networks. Use a computer you control, close remote access and follow Desk’s disconnection check. Being offline does not clean an infected computer.
Use the emergency window in the official app. The secret is displayed for 45 seconds, with up to three extensions within the session limit. Do not take screenshots or share the secret, passwords or file with support, chats or online services.
When finished, close the flow and return to secure hardware for normal use. If you exposed a seed phrase, plan to move the funds to a new wallet generated on a trusted device. Forensic erasure of the computer is not guaranteed.

Content checked against Desk 1.0.0-beta.9.8 and Mirror 1.0.0-beta.5. Downloads show the version actually published; review its notes and compatibility. APK availability does not imply an app-store release.

Your phone can be your NFC reader.

Cuvex Mirror uses your compatible smartphone’s NFC to read and write cards for Cuvex Desktop through an encrypted Bluetooth connection. It is required to fully operate Cuvex Original with Desktop. Mirror does not decrypt your secrets or replace authorization on the hardware.

You need Android 8 or later with NFC, a camera and Bluetooth peripheral mode, plus a computer with compatible Bluetooth and Cuvex Desk. A temporary PIN and QR bind the session. Mirror needs no account or Internet permission and does not decrypt your secrets.

SHA-256

Check your download, step by step.

SHA-256 verifies file integrity. It does not replace a manufacturer signature or independently guarantee software security.

The comparison runs in your browser. Your file is not sent to the server and you do not need a terminal.

Downloaded file

Leave the downloaded file in Downloads, without extracting or renaming it. Wait for the download to finish.
Open Terminal from your Linux distribution's application menu.
Copy the entire block, paste it into the terminal and press Enter. It only calculates and compares the hash; it does not install or open the App.
Read the result below the pasted block. This may take a few seconds.

The block contains the command to paste. The OK or KO result appears after you run it.

Paste this entire block

sh <<'CUVEX_LOCAL_CHECK'
set -u
folder=""
if command -v xdg-user-dir >/dev/null 2>&1; then folder=$(xdg-user-dir DOWNLOAD 2>/dev/null); fi
if [ -z "$folder" ]; then folder="$HOME/Downloads"; fi
file="$folder/"Cuvex-Desktop-1.0.0-beta.9.13-Linux-x64.AppImage
expected=85b700138cfbaa42f1678ea7cc0100ec7662ae4bc5315bea2080541a3d6e95c8
printf "%s\n" 'CHECKING YOUR CUVEX DOWNLOAD…'
printf "%s\n" "Downloaded file: $file"
if [ ! -f "$file" ]; then
  printf "%s\n" 'KO (FAIL) — FILE NOT FOUND'
  printf "%s\n" 'Check that the download is complete and the file is in Downloads with its original name.'
  exit 1
fi
if command -v sha256sum >/dev/null 2>&1; then
  actual=$(sha256sum -- "$file" 2>/dev/null | awk '{print $1}')
elif command -v shasum >/dev/null 2>&1; then
  actual=$(shasum -a 256 -- "$file" 2>/dev/null | awk '{print $1}')
else
  printf "%s\n" 'KO (FAIL) — DO NOT OPEN THIS FILE'
  printf "%s\n" 'The file does not match the published hash. Download it again from Cuvex and repeat the check. If it fails again, contact sato@cuvex.io.'
  exit 1
fi
printf "\n========================================\n"
printf "%s\n" 'CUVEX VERIFICATION RESULT'
if [ "$actual" = "$expected" ]; then
  printf "%s\n" 'OK — FILE VERIFIED'
  printf "%s\n" 'The file matches the SHA-256 we published for this version. The integrity check completed successfully.'
  exit 0
fi
printf "%s\n" 'KO (FAIL) — DO NOT OPEN THIS FILE'
printf "%s\n" 'The file does not match the published hash. Download it again from Cuvex and repeat the check. If it fails again, contact sato@cuvex.io.'
exit 1
CUVEX_LOCAL_CHECK

Download optional script

Expected result after running

OK — FILE VERIFIED

The file matches the SHA-256 we published for this version. The integrity check completed successfully.

KO (FAIL) — DO NOT OPEN THIS FILE

The file does not match the published hash. Download it again from Cuvex and repeat the check. If it fails again, contact sato@cuvex.io.