Firmware Cuvex · Cuvex BIT

1.2.2

Your download, instructions and integrity check in one place.

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

Download ↓Check your download, step by step. →

CUVEX_BIT_1.2.2_Final_APP-signed.bin

Release notes

Details / what's new in version 1.2.2

Support for legacy cryptograms, authenticated encryption, USB-C file exchange, and optional biometric access, with a twelve-language interface for Cuvex BIT.

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

Receive cryptograms and PSBTs over USB-C, wait for complete files, and remount the volume so the App or Desk can retrieve reinforced cryptograms or signed PSBTs. BIT has no NFC or Bluetooth.
Optional biometric access combines a password with two fingerprints per participant. Fingerprint mismatches turn the outline red; Retry appears after three mismatches. A capture with no result is not treated as a match. Biometric cryptograms require Cuvex BIT.

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, French, Italian, Portuguese, German, Turkish, Japanese, Korean, Polish, Russian, and Arabic.
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 BIT only. Requires a USB-C cable supporting data and power, plus read/write access to USB storage through the Cuvex App on an iOS or Android smartphone with USB-C, or through Cuvex Desk on a compatible computer. This release does not specify an additional minimum App, Desk, or operating system version. NFC and Bluetooth are not required. Do not install this BIN on Cuvex Original.

Installation

Keep an external backup of your cryptograms and prepare update 1.2.2 in the Cuvex App or Cuvex Desk before starting the update on BIT.
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.
Connect Cuvex BIT to your smartphone or computer with a USB-C cable supporting data and power. Open a compatible Cuvex App or Cuvex Desk.
On BIT, open Settings, Version, then Update, and complete the on-screen confirmations. Continue the update flow in the App or Desk and authorize access to the Cuvex drive and folder when prompted.
Let the App or Desk transfer the signed firmware over USB-C. Leave the cable connected until verification and restart finish; do not close the process or disable signature validation.
Confirm that Settings, Version shows 1.2.2, then check that your cryptograms open and exported files can be retrieved before replacing backups.

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_BIT_1.2.2_Final_APP-signed.bin
expected=7f4d5684d0d6647f6ca5cde698e5d8b005f31d3068b31a0cd3322b59a603b527
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.