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

Firmware Cuvex · Cuvex Original

1.2.2

Your download, instructions and integrity check in one place.

Published on 2026-11-21 · UTC · BIN · 2.1 MiB

Cuvex_Original_1.2.2_Final_APP_signed.bin

Release notes

Details / what's new in version 1.2.2

The first Cuvex Original firmware with partial signing for Bitcoin multisig transactions and on-device wallet policy verification.

Policy review and signing

  • Check the wallet policy one field at a time. Read each value in full or show its QR code to compare it with Cuvex Desk.
  • Review recipients, amounts, change and fees. You can open the technical details before the three final confirmations. The device returns the PSBT with its partial signature so the coordinator can collect the required signatures.
  • Cuvex Original confirms that the wallet policy verification response or the signed PSBT has been saved to a DESFire EV1 8K card.

Supported wallets and languages

  • BIP48 P2WSH multisig with sortedmulti, PSBT v0 and SIGHASH_ALL. Up to 6 policy keys, 16 inputs and 32 outputs. The full transfer package is limited to 5247 bytes.
  • When using Original and BIT in the same wallet, use the same profile and follow Original’s limits. Transaction cosigners and the participants who unlock a cryptogram are configured separately.
  • Device languages: English, Spanish, Portuguese, German, Turkish, Japanese, Korean and Russian.

Updating and backups

  • This release follows version 1.2.1 for this model. Keep external copies of your cryptograms and check that you can open them after updating.

Beta requirements and compatibility

To update Cuvex Original, use the compatible Cuvex mobile app on an iOS or Android phone with Bluetooth and power Original over USB-C. To verify multisig policies and sign PSBTs from Cuvex Desk, use a Desk version that supports Original 1.2.2, Cuvex Mirror on a compatible NFC phone linked to Desk, and a DESFire EV1 8K card.

Installation

  1. Keep an external backup of your cryptograms and prepare version 1.2.2 in the Cuvex mobile app before starting the update on the device.
  2. If you download the BIN from cuvex.io, check that it is for Cuvex Original and compare its SHA-256 with the value on the download page. Keep the signed file intact.
  3. Power Cuvex Original over USB-C. Turn on Bluetooth on your phone and grant the connection permissions requested by the Cuvex app.
  4. Open the version section in the device settings and start the update. Follow the prompts on the device and in the Cuvex app. Confirm the pairing code shown when prompted.
  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.2. 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_Original_1.2.2_Final_APP_signed.bin
expected=6bf7091462ea78e522947bf84f8e1acaed37febb88c6fcaf7d4903fcc3bc2204
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