Final price. Taxes, shipping and customs duties included.
← Back to apps and firmware

Firmware Cuvex · Cuvex BIT

1.2.5

Your download, instructions and integrity check in one place.

Published on 2026-11-22 · UTC · BIN · 3.2 MiB

Cuvex_BIT_1.2.5_Final_APP_signed.bin

Release notes

Details / what's new in version 1.2.5

Cuvex BIT reconnects its USB drive so Cuvex Desk can retrieve the policy confirmation.

Device changes

  • BIT checks the response file before presenting the output drive. After saving it in Desk, you can close the confirmation on BIT.
  • The delivery screen shows the transfer status and lets you retry an interrupted transfer.

Beta requirements and compatibility

To update Cuvex BIT, use the Cuvex app on a compatible iOS or Android phone with USB-C data support, or Cuvex Desk on a compatible computer. Use a USB-C cable that carries both power and data and allow access to the device volume. Multisig policy verification and PSBT signing require Desk to recognize the Cuvex_BIT_1.2.5_Final build.

Installation

  1. Keep an external backup of your cryptograms and prepare version 1.2.5 in the Cuvex mobile app or Cuvex Desk before starting the update on the device.
  2. If you download the BIN from cuvex.io, check that it is for Cuvex BIT and compare its SHA-256 with the value on the download page. Keep the signed file intact.
  3. Connect Cuvex BIT to your trusted phone or computer with a USB-C data and power cable, then open the update app.
  4. Open the version section in BIT settings and start the update. Follow the app’s prompts and allow access to the Cuvex volume and folder if requested.
  5. Keep the device powered and connected until it has finished checking the signed firmware and restarted.
  6. Check that the version section shows 1.2.5. Make sure you can open your compatible cryptograms before replacing any earlier 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.

  1. Leave the downloaded file in Downloads, without extracting or renaming it. Wait for the download to finish.
  2. Open Terminal: press ⌘ + Space, type Terminal and press Return.
  3. 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.
  4. 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.5_Final_APP_signed.bin
expected=facae74d42e0a245512dd63e24d0aae11605b2ffd246b42e5935eb4525aeebf0
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.

YOUR SELECTION

Your bag0

Video tutorial

Playback connects to YouTube. Open on YouTube ↗

Necessary functions let you use the store. You can choose whether to enable the others.

Privacy policy