Firmware Cuvex · Cuvex Original

1.2.1

Your download, instructions and integrity check in one place.

Published on 2026-11-12 · UTC · BIN · 2.0 MiB

Download ↓Check your download, step by step. →

CUVEX_Original_1.2.1_Final_APP-signed.bin

Release notes

Details / what's new in version 1.2.1

Support for legacy cryptograms, authenticated encryption, Bitcoin transaction review, and an eight-language interface for Cuvex Original.

Protection and compatibility

Reads supported legacy and current Cuvex formats while preserving the alias and secret data. Original 1.2.1 and BIT 1.2.2 share non-biometric cryptogram formats, including reinforced copies; the oldest formats require the corresponding boot secret.
New cryptograms use AES-256-GCM with authentication tag verification. Supported older copies can be reinforced without changing the secret or access credentials. A copy whose authentication has already been verified is not offered reinforcement again.

Wallets and Bitcoin transactions

Uses the BIP39, SLIP39, and Monero dictionaries without changing passphrases or keys. Coin-and-four-dice generation rejects out-of-range results and asks you to toss the coin and roll the dice again, without substituting approximate words.
Review recipients, change, and fees before signing, with verification of the generated signatures. Signing profile: BIP174 PSBT v0, native P2WPKH inputs, and SIGHASH_ALL. General PSBT v2 support and signing of Taproot or Bitcoin multisig inputs are not included.

Device features

A shared cryptogram check runs before NFC writing, cloning, seed reuse, reinforcement, or PSBT storage. It protects recognizable Cuvex backups and allows cards containing unrelated data or residue to be reused; incomplete reads prevent writing. Original does not provide biometrics or USB-C file exchange.

Interface and languages

Refined text, alias, button, and notification layouts in light and dark themes, with a language selector and distinct flags.
Firmware languages: English, Spanish, Portuguese, German, Turkish, Japanese, Korean, and Russian.
The second failed password attempt warns that one attempt remains. The third failure blocks new decryption attempts for five powered-on minutes; disconnecting the device during the lockout does not clear it.

Using existing backups

Keep existing backups and confirm that the new copy opens before replacing them. Reinforcement is optional: you can continue reading a supported older copy. Older firmware may not recognize the new authenticated formats. Interoperability between Original and BIT is limited to supported non-biometric cryptograms.

Beta requirements and compatibility

For Cuvex Original only. Guided updates require a compatible Cuvex App on an iOS or Android smartphone, Bluetooth, and a stable USB-C power supply for the device. NFC carries cryptograms and PSBTs, not firmware updates. This release does not specify an additional minimum App or operating system version. Do not install this BIN on Cuvex BIT.

Installation

Keep an external backup of your cryptograms and download update 1.2.1 in the Cuvex App before putting the device into update mode.
If you download the BIN from the website, compare its SHA-256 with the published value. Keep the signed file unchanged; the publication ZIP is not the file installed on the device.
Power Cuvex Original over USB-C. Enable Bluetooth on your smartphone and grant the connection permissions requested by the Cuvex App.
On the device, open Settings, Version, then Update, and complete the on-screen confirmations. Follow the App's update flow and confirm the pairing code displayed on the device.
Keep the smartphone beside the device and leave power connected until transfer, verification, and restart are complete. Do not disable signature validation.
Confirm that Settings, Version shows 1.2.1 and check access to your copies before replacing any backup.

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.

What does AES-256-GCM add?

New cryptograms use AES-256-GCM authenticated encryption, checking the protected content and authentication tag. This does not mean that all metadata or every older copy has this protection.

Is cryptogram multisignature the same as Bitcoin multisig?

No. Protect decryption with up to six participants, requiring everyone or a threshold such as 2 of 3. This policy controls access to the secret; it does not turn a wallet into a Bitcoin multisig wallet.

Which transactions can these versions sign?

Both devices process BIP174 v0 PSBTs with P2WPKH inputs and SIGHASH_ALL. They review recipients, amounts, change and fees; approval is bound to that transaction and the signature is verified. Displaying Taproot Bech32m recipients does not mean signing Taproot inputs. Private keys are not exported for signing.

What happens after incorrect passwords?

Three attempts trigger a five-minute pause that persists after power loss. This limits attempts on the device, not offline attacks on an exported copy. Use strong credentials and protect your backups.

What does Reinforce Cryptogram do?

After decrypting a compatible older unauthenticated copy, create a reinforced version while retaining the secret, credentials and participant policy. Original saves it to NFC; BIT returns it over USB-C and retains biometric templates where applicable. Verify the new copy before retiring the old one.

How do dice and a coin create a wallet?

The guided flow produces a 24-word BIP39 seed using the 2048-word dictionary. Follow the device’s rolls and checks. The menu language does not determine the seed dictionary language.

Can I move any cryptogram between devices?

No Cuvex cryptogram is tied to a particular device. You can decrypt it on any compatible Cuvex device, provided you retain the cryptogram and its required credentials. Cryptograms protected with biometrics can only be decrypted on Cuvex BIT.

How do I connect my Cuvex to Desktop?

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.

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: press ⌘ + Space, type Terminal and press Return.
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="$HOME/Downloads"
file="$folder/"CUVEX_Original_1.2.1_Final_APP-signed.bin
expected=a3d6f5278ab4d63e860eed0e5708d7e0b685d5884950c33a96a3a59a751aacc9
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.