top of page

SUPPORT

Need help?
If you have any questions, please read our FAQ or contact us; our support team will be happy to assist you.
background_contacto.jpg

WRITE TO US

CUVEX DEVICES
TUTORIALS

CUVEX 

Seed Phrase Encryption Recovery & Doble AirGap Hardware Wallet PSBT.

disp+usbc.png

CUVEX BIT

Personal HSM for Seed Phrase Encryption.

 

Double AirGap PSBT Signing (Biometric Access)

biometric.png
Cuvex_home.png

DEVICE

  • Yes, you can encrypt even plain text not linked to crypto assets. With Cuvex you can encrypt any secret, private key or seed.

  • The Cuvex device is certified by CE, UL, and RoHS, meeting quality, safety, and environmental standards. It is resistant to damage from X-ray machines and can be safely transported on airplanes.

  • No, any Cuvex device purchased second-hand or from third parties, may be compromised.

    It is vitally important that you never use a device that is not purchased directly on our website or official distributors.

    As well as you must check that the factory seal and/or delivery packaging have not been tampered with.

    If you have any doubt about factory sealing, do not use the device and return it.

    ​Learn more about our sealing and packaging process here.

  • Reducing costs in this vital part of our device was not an option.

    We have selected the best, from the best manufacturer that any electronics professional knows.

     

    Cuvex mounts STM32U585, the highest quality version marketed by the manufacturer ST.

    Designed specifically for military grade hardware encryption, it features its own encryption accelerator engine (AES, PKA, OTFDEC).

     

    Our device does NOT store anything in its secure element, but we also decided to implement it in the hardware so that it does not perform any of its temporary tasks of encryption or decryption in a standard memory.

     

    In addition, the device is already prepared for future evolutions where the functionalities demanded by the Blockchain industry can be implemented.​

  • If you enter your password wrong a second time, the device enters a time-locked process in which it supports a new retry. Please make sure you enter your Passwords correctly.

  • The Cuvex device supports the creation of cryptograms through two methods:

     

    a) You can select one of three types of Seed Phrases: BIP39, Monero, or SLIP39 (Shamir). The device will verify each word for these three types of seed phrases.

     

    b) Alternatively, you can input plain text of up to 500 characters.

     

    Option A: Seed Phrases

    Using this option, the device supports up to 54 words from any of the three types of seed phrases. This means you could store multiple wallets in a single cryptogram, depending on the type of seed phrase and the number of words in each.

    If you choose to do so, it’s essential to clearly identify the last word of one wallet’s seed phrase and the first word of the next.

    For instance, if you have wallets with seed phrases consisting of 12 words each, you could store up to four wallets in a single cryptogram. However, always keep the above precautions in mind.

     

    Option B: Plain Text

    With this option, you can simply include any text you want, up to 500 characters. This is a free-text option, meaning it does not verify or assist in inputting standardized words.

    You must carefully ensure that the text is accurate and thoroughly reviewed before encrypting it. Mistakes cannot be corrected after the encryption process.

  • We have not implemented a process to erase or format cards in any of the workflows within the Cuvex device or the Cuvex App.

     

    This decision was made to avoid situations where a user might accidentally erase the wrong card, potentially causing significant issues.

     

    The cost of a pack of new cards is minimal compared to the consequences of unintentionally erasing a card that contains an unbacked secret.

     

    That said, if you choose to use other applications to erase cards, you must ensure that the formatting is done using the NDEF standard.

     

    Failing to format the card with this standard will render it incompatible with the Cuvex device. You can learn more about the types of cards used with Cuvex here by visiting NFC TAG.

  • To begin using your Cuvex device, first visit our manual, and next download the Cuvex App, remove and keep the security seals from both the box and the device, and validate the shipment's traceability using the seal codes.

  • The AES 256 GCM encryption algorithm and hardware architecture guarantee the creation of a cryptogram of the highest quality.

    The device does not store any information, all processes are performed without connection to any external device and without internet connection. Storage on an NFC card is already secure in itself, since only the stored cryptogram can be accessed, which is already encrypted before being stored on the card.

     

    AES 256, is possibly the most secure encryption algorithm today. In some published studies, it is estimated that a current supercomputer could take more than 10,000 years to break an AES 256 cipher. This is the encryption algorithm used for military and government secrets.

     

    Our code is public and anyone can audit what we say. Despite including the device, a secure hardware element where information is handled for each process, no data is ever stored in it. You only have to guarantee to remember your Passwords, if you forget this information, neither we nor anyone else can help you recover your secret.​

  • For security, Cuvex does not erase or rewrite on cards that already have a cryptogram stored.

     

    You can always decrypt a card and encrypt a new one, changing the mono or multi-signature access control, with new Passwords.

  • Yes, you can encrypt even plain text not linked to crypto assets.

    With Cuvex you can encrypt any secret, private key or seed.

  • Uppercase, lowercase, numbers and symbols of a minimum of 12 characters are required.

  • To summarize, let me inform you that a password with a minimum configuration in MonoSignature mode requires 12 characters, with uppercase and lowercase letters, numbers, and symbols. This configuration generates a vast number of possibilities that, for a potential attacker, would take current computers approximately 14.9 billion years to test all possible combinations.

     

    In practical terms, a brute force attack on the AES 256 GCM cryptogram that safeguards the secret you have protected is impractical.

     

    If you are using a multi-signature setup or have established a password longer than the standard 12 characters, the security level increases exponentially.

     

    You can rest assured. With current global technology, the likelihood of a successful brute force attack is exceedingly low.

    Please find specific technical details below.

     

    Security Estimation for a 12-Character Password

    This section provides an analysis of the security of a 12-character password composed of uppercase letters, lowercase letters, numbers, and symbols, explaining the total possible combinations and the estimated time required to break it through brute force.

     

    1. Number of Possible Combinations

    When you create a password using 12 characters where each character can be an uppercase letter, lowercase letter, number, or symbol, you’re generating combinations within a very large “space” of possibilities. Here’s a step-by-step breakdown:

    ​​

    • Types of characters and their possible counts:

      • Lowercase letters: 26 (from 'a' to 'z').

      • Uppercase letters: 26 (from 'A' to 'Z').

      • Numbers: 10 (from '0' to '9').

      • Common symbols: Approximately 32 symbols available on most keyboards.

    • Total possible characters: We add all character types to determine how many options exist for each position in the password. Total: 26 + 26 + 10 + 32 = 94

    • Possible combinations for a 12-character password: For a password with 12 characters, where each position can be any of the 94 characters available, the number of possible combinations is calculated using exponents: Total combinations = 94^12

    • This means that for each of the 12 positions in the password, you have 94 options. By multiplying the options for each position, we get the total number of combinations.

    • Resulting number of combinations: 94^12 is approximately 4.7 x 10^23 combinations, or 470,000,000,000,000,000,000,000 possibilities.

     

    This large number illustrates how difficult it would be to guess or attempt all possible combinations. With a 12-character password using this full range of characters, the number of combinations is so high that brute force attempts would require enormous amounts of time.

    2. Estimated Time to Break the Password

    To calculate the time required to break a password, we need to understand the processing speed of the attacking system, specifically how many combinations it can attempt per second.

    • Processing Speed (Attempts per Second):

      • Standard modern computer: approximately 1 million combinations per second (10^6 attempts/sec).

      • Advanced supercomputers or networks: around 10 billion combinations per second (10^9 attempts/sec).

    • Estimated Time Calculation:
      With 4.7 x 10^23 possible combinations, we divide this number by the speed of attempts to obtain the estimated time.

      • Case 1: Standard computer (1 million attempts/sec)

        • Estimated time: 4.7 x 10^23 / 10^6 = 4.7 x 10^17 seconds = approximately 14.9 billion years.

      • Case 2: Supercomputer (10 billion attempts/sec)

        • Estimated time: 4.7 x 10^23 / 10^9 = 4.7 x 10^14 seconds = approximately 14,900 years.

    In conclusion, even with advanced technology, breaking a 12-character password using uppercase letters, lowercase letters, numbers, and symbols remains extremely difficult and would require an impractical amount of time.

    All these calculations are based on the assumption that someone obtains access to a card containing your encrypted secret and attempts to brute-force it using computers available to the public or even a supercomputer, which only a few entities worldwide possess. This would mean the attacker can automate the process of testing every possible combination. If the attacker attempts to do this using a Cuvex device, the time required could increase exponentially, potentially thousands of times over, as human error and the manual process would render such an attempt virtually impossible.

    In any case, if you enter the password for your secret twice in a row in an attempt to decrypt it, the Cuvex device will lock for 5 minutes. This further adds to the immense complexity of finding the correct password.

    Rest assured! Cuvex has been designed to do something very complex in a very simple way, implementing military-grade security in a system accessible to everyone.

     

     

  • Whenever Cuvex prompts you to bring your card close to the device, you can do it in one of the following 2 ways: 1. ​At the bottom part of the device. 2. Front part of the device.​

     

    Furthermore, the Cuvex device will activate a green LED when the NFC card is correctly positioned within the reader antenna’s range, helping you align it properly. If the green LED at the top of the screen does not light up when the card is brought close to the device, remove the card and try repositioning it in the reading area. You can also move the card slowly over the reading area to ensure it is detected.

     

    8K cards designed to store N-of-Six multisignature cryptograms take slightly longer to be read by the Cuvex device.

  • The Cuvex device will ask you to approach the issuer card, the card you want to clone. The device will ask you to approach a blank receiver card and will clone on the new card an exact copy and with the same security of the issuing card.

    It's that simple!

  • Cuvex Supports "N of N" and "N of 6" Multisignature Options.

     

    In the multisignature encryption process, the Cuvex device will prompt you to specify the number of signers you want to establish and how many of them will be required to decrypt the cryptogram.

     

    For example, you can designate up to six signers and configure the cryptogram to be decrypted with as few as one of them. You can create any combination, such as requiring all six passwords for decryption, only three, only two, four, or any other setup within the maximum of six signers.

     

    When you configure fewer required participants for decryption than the total number of signers, such as "3 of 6", you will need to use 8K cards.

     

    If you require all signers to decrypt (e.g., "6 of 6"), standard cards can be used.

    To view the encrypted private key or seed phrase stored on an NFC card, you must input the number of passwords defined as mandatory for decryption.

     

    It is not possible to specify which passwords are mandatory any of the entered passwords will suffice as long as the minimum required number is met.

     

    There is no need for each signer to input their password in the same order they signed during the encryption process. The Cuvex device will validate and allow decryption regardless of the order in which the passwords are entered.

  • All entropy calculated by software demands your trust in that software.

    If it is you who, completely independent of the software, generate the necessary 23 words by throwing heads or tails and all four dice, you will have no doubt about the quality of the seed that you have created yourself.

    Although the seed generation softwares are assumed to be a high quality of entropy, none can equal to this completely unique manual process that you are going to create.​

  • Our App will notify you that you have an update available by downloading the new version of Firmware to the secure hardware element of your smartphone.​

    Important, do not start the device update process until you download the new firmware version to your smartphone.

     

    When you select “Update” from the Cuvex device menu, the device will completely erase the application firmware and activate its BlueTooth module, showing you a code on the screen that you must confirm by entering it in the Cuvex App. If you accept it, the firmware download will begin from the secure element of your smartphone, to the Cuvex device. When you complete the download, the device will cut off the BlueTooth connection, ensuring that your firmware update process is done offline with any third-party device or Internet.

     

    ​Finally, the device and App Cuvex will confirm the update made and the new firmware version.

  • Cuvex has selected the best NFC card manufacturers, demanding top-notch quality standards. Your cryptogram will be stored on the chip of the cards, so it must be of first quality and withstand as many read cycles as possible. It makes no sense to save by purchasing cheaper or poorer quality cards.

    In any case, NFC cards or tags must be compatible with those used by Cuvex, learn more about NFC TAG.

     

    We recommend that you access our NFC Cards catalogue, where you can even request your 100% personalized card.

  • Traceability Seals

     

    The traceability seals are two identifiers included with your Cuvex device. You should receive your package shrink-wrapped and sealed with a numbered security seal. We recommend not breaking this seal until you validate it.

     

    Upon opening the package, you will find an additional seal on the device itself, covering the USB-C port. This second seal will display a different code than the one on the external seal.

     

    When you first use the Cuvex smartphone app, please go to the menu>security>validate traceability. If you didn’t complete this step during the initial setup, don’t worry you can access this process later.

     

    These seals are designed to ensure that your device’s package has not been tampered with during transit. Once removed, the seals leave the word "VOID" imprinted on the surface, providing visible evidence of tampering.

     

    Additionally, the codes from both seals can be entered into the Cuvex app to confirm that they were generated by us during manufacturing.

  • Security of the Bluetooth Module

    We understand your concerns about the inclusion of Bluetooth and why you might feel it’s safer without it. However, in practice, the Bluetooth-enabled firmware update process on the current Cuvex device is possibly more secure due to the AirGap it establishes.

     

    Allow me to provide a brief and concise explanation.

     

    How the Cuvex Bluetooth Firmware Update Process Works

     

    The Cuvex device operates with two firmware components:

    1. Bootloader:

    • The Bootloader’s sole function is to securely listen for Bluetooth communications and receive the operational firmware for the device.

    • Once received, it validates the RSA signature of the firmware before installing it.

    1. This Bootloader is pre-installed in a specific, immutable section of the device’s physical memory, which is locked at the factory and cannot be modified—not even with physical access to the device.

    2. Application Firmware:

    • After validation, the Bootloader installs the operational firmware into a separate memory partition and initiates a restart, forcing the device to boot from this partition.

    • Once the device boots into operational mode, the Bluetooth module is disabled and cannot be activated.

     

    This configuration ensures that Bluetooth functionality is only active during firmware updates and remains entirely inactive during normal operation. You can verify this because our firmware is openly accessible, verifiable, and compilable via our GitHub repository.

     

    Why Bluetooth is Secure

     

    Updating the firmware via USB-C presents greater security challenges, as physical access could potentially allow someone to manipulate the firmware up to the Bootloader level without the safeguards provided by Bluetooth’s encrypted pairing.

    Additionally, the Bluetooth module’s power activation is tied to a circuit-level design that illuminates a blue LED on the screen whenever the module is energized. This ensures that any attempt to activate Bluetooth, regardless of firmware, will alert the user.

     

    According to third-party security auditors, the Bluetooth update process for the Cuvex device is as secure, if not more secure, than alternative update methods that do not use Bluetooth.

     

    The mandatory RSA signature verification for firmware installations further ensures that no unauthorized operations, including Bluetooth activation, can be implemented from the memory partition used for regular Cuvex operations.

     

    Conclusion

    You can rest assured and fully enjoy the benefits of Cuvex using the current device.

  • With the Cuvex device, it is possible to encrypt a single cryptogram containing seed phrases of up to 54 words or plain text secrets of up to 500 characters.

     

    Encryption can be performed in single-signature mode or multisignature mode with up to six distinct signers/passwords. In multisignature mode, you can configure only a portion of the signers as mandatory for decryption. For instance, you can set it so that 3 out of 6 signers are required to decrypt.

     

    Passwords must be at least 12 characters long, using a combination of uppercase letters, lowercase letters, numbers, and symbols. This configuration creates an astronomical number of possibilities, making it computationally infeasible for a potential attacker to brute force current computers would require approximately 14.9 billion years to test all possible combinations.

  • Any card containing a Cuvex cryptogram can be decrypted using any Cuvex device, provided you have the passwords used during the encryption process. If you lose access to these passwords, neither we nor anyone else will be able to assist in decrypting your secret.

     

    The AES-256-GCM algorithm, implemented via hardware, is a military-grade encryption standard widely used across public and private industries.

APP CUVEX

  • A Watch Only Wallet (WOW) is an application that exclusively manages the public key of your wallet. This means it is limited to performing operations such as balance verification, generating receiving addresses, and managing Coin Control functionality.

     

    A WOW, on its own, cannot sign transactions to send funds to any address.

  • A PSBT (Partially Signed Bitcoin Transaction) Hardware Wallet is a physical device capable of signing PSBT transactions.

    Typically, Watch Only Wallet (WOW) applications prepare the data required to construct a PSBT transaction and then send it to a hardware device equipped with the capability to sign such transactions.

    PSBT hardware wallets usually store the private keys needed for signing these transactions. This process is commonly referred to as AirGap, as there is a physical separation between each component involved in the process.

    However, only the Cuvex device implements a Double AirGap PSBT procedure, providing an additional layer of security.

    What Makes the Cuvex Double AirGap Process Unique?

    Unlike traditional PSBT hardware wallets, the Cuvex device does not store any private keys, making it doubly secure. To sign a transaction using the Cuvex device, the following steps are required:

    1. Create the PSBT transaction: Use the Cuvex App to prepare the transaction and record it onto a blank NFC card.

    2. First AirGap: Read the NFC card containing the unsigned transaction with the Cuvex device. Verify the transaction on the device.

    3. Second AirGap: If the user confirms the transaction, decrypt the private keys stored on a separate encrypted NFC card using the same Cuvex device.

     

    Key Advantages of the Cuvex Approach This unique process allows a single Cuvex device to be shared among multiple users, such as members of a family, enabling each person to sign transactions from different wallets using the same device. This unparalleled functionality makes the Cuvex device a standout solution in the blockchain and cryptocurrency sector.

  • Coin Control refers to a set of procedures that allow you to associate specific metadata with your transactions.

    This information is stored locally in your Watch Only Wallet (WOW) and is managed exclusively by you. It is not shared or stored elsewhere, ensuring full privacy.

     

    Key Features and Use Cases

     

    • Tagging Transaction Details: When generating a new receiving address in your wallet, Coin Control enables you to tag relevant information, such as the sender (person or entity) who is transferring Bitcoin to you. This allows you to track the receiving address you provided and monitor future payments.
       

    • Additional Metadata: You can also label the initial amount received, the purpose of the transaction, or any other details. This ensures you can always trace the origin of any payment and decide whether or not the original sender can monitor the future use of those received Bitcoins on the Bitcoin blockchain.
       

    • Privacy Alerts: Wallets with Coin Control can generate alerts to help you avoid common privacy pitfalls, such as:
       

      • Reusing addresses.
         

      • Overpaying transaction fees.
         

      • Creating transactions without change outputs.
         

      • Rounding errors and other situations that may compromise your financial privacy.

     

    These alerts aim to enhance your Bitcoin privacy and help you manage your funds securely.

     

    Privacy Implications of Coin Control

     

    One of the most critical aspects of Bitcoin privacy is understanding that when you receive Satoshis in your wallet, you share the receiving address with the sender. This means the sender can monitor how you spend those Bitcoins in the future.

    Additionally, when you send Bitcoin to a third party without using Coin Control, you may unknowingly reveal significant information about your total holdings. Many wallets reuse addresses or store all available funds in a single address.

     

     

    A Real-World Example

    Let’s say your wallet has $100,000 in Bitcoin in one address. Without effective Coin Control, when you send $100 to a third party, the transaction will:

     

    1. Transfer the full $100,000 to the blockchain.
       

    2. Deduct $100 for the payment.
       

    3. Return $99,900 to a newly generated change address.
       

     

    The recipient of your $100 payment can see the change address on the blockchain and deduce the total value of your wallet, which poses significant privacy and security risks.

     

    By leveraging Coin Control, you can mitigate these risks, ensuring greater privacy and control over your Bitcoin transactions.

  • Absolutely nothing!

     

    The Cuvex App is one of the few applications that adheres to a strict zero-knowledge policy. This means that no user data is collected or stored on Cuvex servers.

     

    Unlike most apps on the market, Cuvex does not require users to create a profile. You are not asked to provide an email, password, OTP verification, or undergo any KYC process.

     

    All information entered into the app is stored securely in your smartphone’s secure element. Furthermore, this information is not personal and serves solely as internal management data for the user, with no intrinsic value.

     

    As such, if you lose your smartphone, there is no need to worry about the information stored in the Cuvex App.

     

    Restoring Your "Profile" on a New Smartphone

     

    To restore your app setup on a new smartphone, simply download the Cuvex App from the official app store.

    Since there is no login option, your data cannot be recovered from Cuvex servers. Instead, you’ll need to re-link your Cuvex cards as you did with your previous smartphone.

     

    The app will prompt you to create a PIN. This process is conducted entirely on your smartphone, with no data being transmitted over the internet or shared with anyone else. The PIN is stored in your smartphone’s secure element and is known only to you.

     

    Once you access the main menu of the app, you’ll need to re-link your Cuvex cards:

    1. Choose the design of your card or take a photo of your personalized card.
       

    2. Start the card linking process. This will activate your smartphone’s NFC, and simply bringing your card close will allow the app to read basic administrative information such as the card alias, firmware version, and hardware version used to create the cryptogram.
       

     

    It’s important to note that the app does not store or read the cryptogram itself. It only accesses non-encrypted card information needed for administrative purposes.

     

    This information is securely stored in your smartphone’s secure element and can be managed entirely offline.

    If the linked card contains information for a wallet created with the Cuvex device using the Dice and Coin method, and you have a backup file of your labels, you can import that file to restore all label information and the wallet’s privacy settings.

     

    In Summary

     

    The Cuvex App ensures your information remains private and accessible only to you. It does not share data with anyone else.

     

    You can restore your "profile" on any new app installation by re-linking your Cuvex cards and, if applicable, importing the backup files of your labels associated with your UTXOs.

TRANSCEND

  • No. Under no circumstances does Cuvex ever have access to your recovery seed phrase. It is fully encrypted offline using the Cuvex device, creating a military-grade AES 256 GCM cryptogram. This cryptogram is then stored on Cuvex NFC cards, which only you have in your possession.

  • No. Under no circumstances does Cuvex ever have access to the Password that grants your heirs access to your inheritance. This Password is encrypted in the Cuvex App, and the smartphone is required to go offline during the encryption process, generating an AES 256 GCM cryptogram before anything is sent to Cuvex servers. Furthermore, that cryptogram is then encrypted a second time using Shamir’s Secret Sharing by splitting it into no fewer than 50 fragments. Finally, each fragment is encrypted a third time using the public keys of each decentralized Encryptor Node of the Transcend Network.

    In short, the Password your heirs can download and decrypt at the time you choose can only be deciphered by them using their Clone card.

  • Yes. You may access your Transcend contract at any time to edit the life-verification intervals, the additional Coverage period, the contract duration, or to link new cards as the primary cards for managing the inheritance. You can also, if you wish, cancel the Cuvex crypto inheritance service entirely.

     

    All you need is the primary card you used during setup, or any of the secondary cards linked to you as the inheritance issuer.

  • Whenever you create a Transcend contract, you must designate several cards as the contract’s primary inheritance cards. Because Cuvex does not ask for any personal information, the only way to interact with your inheritance contract is by using the metadata on those primary cards. You can link as many cards as you deem necessary when you create your contract, or later by editing your inheritance contract and linking additional cards as primary.

     

    We recommend linking at least two primary cards to manage your inheritance contract properly.

  • If all of your heirs lose their inheritance cards, they will lose access to both the recovery seed phrase encrypted on those cards and the second Password that you have not yet provided them. It is critical that your heirs have enough copies to ensure sufficient redundancy. If you only provided one inheritance card to each heir, they can create as many Clones of that card as they feel necessary to guarantee future access. As long as at least one heir retains a copy, they all can access both the recovery seed phrase and the second Password that the Transcend system will deliver to them. Thus, a total loss of the inheritance is highly unlikely.

  • If your heirs lose the other Password that you gave them privately (the one not encrypted with Transcend), there is no way to decrypt your Wallet’s recovery seed phrase. The AES 256 GCM cryptogram generated by the Cuvex device could take a supercomputer more than 10,000 years to break using current technology.

    It is of utmost importance that your heirs safeguard the Password you provide along with a copy of their Cuvex card. This Password alone cannot decrypt the inheritance card, but it is crucial to combine it with the second Password they will eventually retrieve from Transcend. They should memorize it and store it wherever they keep their sensitive passwords, following standard best practices.

  • The Transcend system is designed such that no data stored within it is of any use to an attacker. All information is encrypted offline before being sent to Transcend Nodes. Once received, it is fragmented using Shamir’s Secret Sharing, and each fragment is then re-encrypted by decentralized encryptors.

    Put simply, no information managed by the Transcend system can reveal the Password that you have protected and intend to provide to your heirs. Only your heirs, after the life-verification period and the coverage period have elapsed, can retrieve the missing Password and access their inheritance.

  • Transcend’s systems are designed so that the entire decentralized network of encryptors stores a backup of all inheritance contracts. Each backup held by every Node in the Transcend network is fragmented and re-encrypted by the other Nodes. As a result, no single Node can decrypt anything by itself, but any Node can facilitate a complete recovery of the system.

    Put simply, Transcend’s security lies in its decentralized encryption and redundancy. Completely disabling the network and consequently all inheritance contracts would require compromising 85% of the Nodes worldwide.

  • In practice, the Clone cards held by your heirs cannot be decrypted by an attacker who steals or copies them, so there is no immediate danger.

    The real problem would occur if someone steals or copies your heirs’ inheritance card and obtains the initial Password you gave them. With those two pieces of data, once the life-verification period expires, this attacker could recover the remaining Password needed to access the Wallet.

    That is why your heirs must properly safeguard their inheritance, following these recommendations:

    1. Do not reveal to anyone that they are recipients of a crypto inheritance through Transcend.

    2. Memorize and securely store the first Password they received.

    3. Keep as many Clones of their recipient card as they see fit in different secure locations, ideally protected in Faraday pouches.

STORE

  • We ship to more than 160 countries. In the purchase process you will be able to select within the admitted countries.

  • Usually, between 3 and 10 business days, depending on your destination country.

  • The price you pay with your order to Cuvex does not include customs taxes.

    The transport agency will contact you if it is necessary to pay these taxes from your country of receipt.

  • By default, and in order not to request any unnecessary personal information, Cuvex delivers a payment receipt. If you need a nominative invoice, you just have to contact us, send us the payment receipt and the data of the natural or legal person who requires the nominative invoice, including full name or company name, address, email and tax identification number.​

  • The official warranty period is 24 months for Cuvex Device.

    Any factory faults of the device will be covered.

    Cuvex will not repair your device, we will deliver you a completely new one

  • Unfortunately, we cannot cover any accidental break, bump, wet, moisture, handling or mistreatment suffered by the Cuvex device. Soon you will be able to contract an accident insurance with us.

  • Unfortunately, we cannot cover any accidental break, bump, wet, moisture, handling or mistreatment suffered by the Cuvex device. Soon you will be able to contract an accident insurance with us.

  • 30 days returns, as long as the factory packaging has not been opened.

    You have a replacement guarantee.

    Against any manufacturing problem, your Cuvex Device, Faraday Case, and Cuvex NFC Cards, is guaranteed for 24 months.

     

    Please read the store's terms and conditions carefully.

NFC CARDS, CRYPTOGRAMS, CLONING & TROUBLESHOOOTING

Tabla.jpg
  • Cuvex uses two types of cards depending on the size and characteristics of the cryptogram.

    Standard Cuvex Card

    • Chip: NTAG216

    • Intended for standard cryptograms.

    • Compatible with single-signature cryptograms.

    • Compatible with multisignature cryptograms when all configured signers are mandatory for

    decryption.

    Cuvex 8K Card

    • Chip: MIFARE DESFire EV1 8K

    • Format: NDEF

    • Intended for cryptograms requiring additional storage capacity.

    • Required for N-of-6 / X-of-6 multisignature configurations where not all configured signers are

    • mandatory for decryption.

  • Yes.

    The original type of secret does not determine which card you need.

    The Cuvex device can encrypt, among other things:

    • Plain text.

    • Seed phrases.

    • Private keys.

    • Wallets created using physical dice-and-coin entropy.

    In all these cases, Cuvex generates an AES-256-GCM cryptogram.

    As long as the resulting cryptogram is a standard-size cryptogram, it can be stored on a standard Cuvex

    NTAG216 card.

    The relevant limitation is not whether the original information was text, a seed phrase or a wallet, but

    the final cryptogram structure and size.

  • Yes, with one important exception.

    A standard Cuvex NTAG216 card can be used for:

    • Single-signature cryptograms.

    • Multisignature cryptograms where all configured signers are mandatory.

    If you create an N-of-6 / X-of-6 multisignature cryptogram where not all configured signers are

    required for decryption, a Cuvex 8K card is required because the resulting cryptogram needs more

    storage capacity.

  • A Cuvex 8K card is required when the cryptogram structure requires more storage capacity than a

    standard card provides.

    In particular, X-of-6 multisignature cryptograms where not all configured signers are mandatory

    for decryption require a Cuvex 8K card.

    The Cuvex 8K card uses:

    MIFARE DESFire EV1 8K + NDEF format.

  • No.

    A standard NTAG216 card does not provide enough capacity for a cryptogram that requires a Cuvex 8K

    card.

    A properly NDEF-formatted MIFARE DESFire EV1 8K card must be used.

  • Not necessarily.

    For the Cuvex workflow, the card must meet the required characteristics, including:

    • MIFARE DESFire EV1

    • 8K

    • NDEF formatting

    Having 8K capacity alone does not confirm that the card is prepared in the format required by Cuvex.

  • No.

    Compatible Cuvex cards are prepared for the appropriate Cuvex workflows and do not require previous

    programming by the user.

    We do not recommend formatting, erasing or modifying a new card with third-party NFC applications

    before using it with Cuvex.

  • A card being identified as NTAG216 does not by itself guarantee complete compatibility with every

    Cuvex workflow.

    For important information, we recommend using cards supplied or validated for use with Cuvex.

    During troubleshooting, an NFC application can be used to identify the chip and its characteristics, but

    we do not recommend modifying the card.

  • An NFC diagnostic application such as NFC Tools can be used to read the card information.

    We recommend:

    1. Remove the card from any plastic packaging or sleeve.

    2. Keep it away from other NFC cards.

    3. Open NFC Tools.

    4. Select Read only.

    5. Present one card at a time to the smartphone.

    6. Confirm that it is identified as NTAG216.

    If you are checking several cards, test them one by one.

    There is no need to write, erase or format the cards during this test.

  • If NFC Tools can identify the chip, this confirms NFC communication with the card, but it does not

    guarantee that every requirement of the Cuvex workflow is being met.

    • You should also check:

    • Card type and capacity.

    • Correct format.

    • Cryptogram type.

    • Card position over the NFC reader.

    • Firmware version.

    • Cuvex app version.

    • USB-C cable.

    • Stable power supply.

  • During NFC operations, the card should be presented to the lower/front area of the device as

    demonstrated in the Cuvex tutorials and manual.

    The optimal reading position may also depend on where the NFC antenna is located inside each card.

    If the card is not immediately detected:

    • Try both sides.

    • Try it horizontally.

    • Try it vertically.

    • Rotate the card.

    • Slowly move it across the NFC reading area.

    Once you find the correct position, keep the card still until the device confirms that the operation has

    finished.

  • When the original Cuvex device correctly detects the card during an NFC operation, the LED turns

    green and remains green.

    This visual indication can help you find the optimal card position over the NFC reader.

    Do not remove the card during a read or write operation until Cuvex confirms that the process has

    finished.

  • Yes.

    Once Cuvex starts reading or writing the card, do not remove it until the device confirms that the

    operation has completed.

    The manual specifically instructs users to keep the card over the NFC reader until the recording process

    has successfully finished.

  • Not necessarily.

    15If your Cuvex correctly reads other Cuvex cards, this is a good indication that the NFC reader itself is

    operational.

    Before considering a hardware problem, check:

    • Card position and orientation.

    • Chip type.

    • Card capacity.

    • Cryptogram type.

    • Firmware.

    • USB-C cable.

    • Power supply.

  • Yes.

    The Cuvex device requires stable power throughout the process.

    Insufficient or unstable power may allow the device to turn on and appear operational while preventing

    an operation that requires stable power during transfer or writing from completing successfully.

    As a troubleshooting step, we recommend:

    • Using the original Cuvex USB-C cable.

    • Using a stable USB power source.

    • Using a suitable charger.

    • Avoiding unnecessary hubs or adapters.

    The manual states that if the device loses power during an operation, the processed information is

    deleted and the workflow must be restarted.

  • Yes.

    The fact that the device powers on does not automatically rule out a cable or power-supply problem.

    A damaged or unsuitable cable, or a weak or unstable power source, may allow the device to boot while

    causing problems during certain operations.

    For this reason, when troubleshooting writing or cloning issues, one of the first tests should be to use

    the original Cuvex USB-C cable together with a reliable charger.

  • We recommend checking the following in this order:

    1. Confirm whether you are using the original Cuvex or Cuvex BIT.

    2. Make sure the latest available firmware is installed.

    3. Update the Cuvex app to the latest available version.

    4. Use the original Cuvex USB-C cable.

    5. Use a stable power source.

    6. Try both sides of the NFC card.

    7. Try horizontal and vertical positions.

    8. Confirm that the green LED indicates correct NFC detection.

    9. Confirm the card model.

    10. Confirm whether it is a standard NTAG216 or an 8K card.

    11. Confirm the cryptogram type.

    12. Confirm whether you are creating a new cryptogram or cloning an existing one.

    13. Confirm whether the operation is being performed from the Cuvex device or from the Cuvex app.

  • Because certain functionality and behavior can depend on the installed firmware version.

    You can check it directly on the device under:

    Settings → Version

    For NFC, cloning, encryption, firmware or compatibility-related issues, Cuvex Support may ask for the

    exact installed firmware version.

    Keeping the device updated is also recommended.

  • Yes.

    When troubleshooting any issue involving the device, cards, firmware or smartphone communication,

    make sure you are using the latest available version of the official Cuvex app.

  • “Wrong format” should not automatically be associated with one single cause.

     

    If this message appears, check:

    1. Card type.

    2. Capacity.

    3. Format.

    4. Cryptogram type and size.

    5. Workflow being used.

    6. NFC position.

    7. Firmware.

    8. App version.

    9. Device power supply.

    A card being readable by NFC Tools or functioning in another process does not automatically rule out a

    format or capacity issue in a particular Cuvex workflow.

  • These are different troubleshooting scenarios.

    Card is not detected:

    Check primarily:

    Position.

    Orientation.

    Which side of the card is presented.

    NFC reader area.

    Power supply.

    Card condition and compatibility.

    Card is detected but cannot be written:

    Check primarily:

    • Capacity.

    • Card type.

    • Format.

    • Cryptogram type.

    • Firmware.

    • Stable power during the writing operation.

  • The cloning workflow is designed to create a copy of the cryptogram stored on a Cuvex card.

    18The source card must contain a valid cryptogram and the destination card must be suitable for the size

    and type of cryptogram.

    The Cuvex device does not overwrite a card that already contains a cryptogram.

    If the cryptogram requires an 8K card, the destination card must also provide the appropriate capacity

    and format.

  • Yes.

    If Cuvex detects that the destination card already contains a cryptogram, it will not use it as the cloning

    destination and will request another card.

    This helps prevent accidental overwriting of existing backups.

  • No.

    For security reasons, Cuvex does not delete or overwrite cryptograms already stored on a card.

    This reduces the risk of accidentally destroying a valid backup of a seed phrase, private key or other

    secret.

  • Cuvex does not provide a card-erasing function and, as a general rule, we do not recommend erasing

    and reusing cards that have stored cryptograms.

    A third-party application may alter the NDEF formatting required for correct card operation.

    If the card only contains test data and can be considered disposable, the user may try the Erase Tag

    function in NFC Tools.

    Before doing so:

    • Make absolutely sure you have identified the correct card.

    • Physically separate it from all other cards.

    • Never do this with a card containing an important cryptogram.

    • Be aware that after erasing it, the card may no longer work correctly with Cuvex.

    For important secrets, we recommend using a new card.

  • This is a security-oriented design decision.

    An erase function could allow a user to accidentally delete a cryptogram for which no other backup

    exists.

    The cost of replacing an NFC card is insignificant compared with the potential consequences of

    accidentally deleting the only backup of a seed phrase or other critical secret.

  • No.

    The actual encryption operation is performed by the Cuvex device.

    The mobile app can be used as a convenient way to type a long text using the smartphone keyboard

    and temporarily write that text onto an NFC card.

    At that stage, the information is not yet encrypted.

    You must then use:

    Encrypt → Text from NFC

    on the Cuvex device. The device reads the text and performs the encryption process.

  • Not as the primary criterion.

    Plain text, seed phrases and wallets generated using dice and coin entropy are ultimately stored as

    encrypted cryptograms.

    The relevant limitation when choosing between a standard card and an 8K card is the structure and

    size of the resulting cryptogram, particularly for certain multisignature configurations.

  • No.

    Original Cuvex

    Includes NFC.

    Can directly read and write NFC cards.

    USB-C is used for power and not as the operational data channel.

    Cuvex BIT

    • Has no NFC hardware.

    • Has no Bluetooth hardware.

    • Exchanges files with the smartphone through USB-C.

    • The Cuvex app can subsequently create external copies depending on the cryptogram type.

    For this reason, the first question when troubleshooting a card-related problem should always be which

    Cuvex device is being used.

  • To help us diagnose the issue efficiently, please provide:

    • Original Cuvex or Cuvex BIT.

    • Smartphone model.

    • iPhone or Android.

    • Exact iOS or Android version.

    • Cuvex app version.

    • Exact device firmware version.

    • Card model.

    • Standard NTAG216 or 8K card.

    • Cryptogram type:

    • Single-signature.

    • Multisignature with all signers mandatory.

    • N-of-6 / X-of-6 where not all signers are mandatory.

    • Whether you are creating a new cryptogram or cloning an existing one.

    • Whether the operation is being performed from the Cuvex device or the Cuvex app.

    • Exact error message.

    • Exact step where the error occurs.

    • USB-C cable being used.

    • Power source or charger being used.

    Never send Cuvex Support your seed phrase, private key, encryption password or any other readable

    secret.

  • No.

    Cryptograms created with Cuvex BIT using biometric protection cannot be stored or cloned onto

    passive NFC cards.

    This applies to both:

    Standard Cuvex NTAG216 cards.

    Cuvex 8K MIFARE DESFire EV1 8K cards formatted as NDEF.

    Biometric-protected cryptograms have storage requirements that prevent passive NFC cards from being

    used as their backup medium.

    In these cases, external backups must be created using external USB-C storage devices connected to

    the smartphone.

    The Cuvex App can store the cryptogram in the smartphone's secure storage and, from there, create

    compatible external backups according to the cryptogram type.

    For biometric-protected cryptograms, the supported external backup medium is a USB-C storage

    device.

  • No.

    A Cuvex 8K card provides more storage capacity than a standard NTAG216 card, but this does not make

    it suitable for biometric-protected cryptograms created with Cuvex BIT.

    Biometric cryptograms cannot be cloned onto any passive NFC card, regardless of whether the card

    is:

    A standard NTAG216 card.

    A MIFARE DESFire EV1 8K card formatted as NDEF.

    To create an external backup of a biometric-protected cryptogram, an external USB-C storage device

    connected to the smartphone must be used.

    Therefore, the Cuvex 8K card should not be considered a universal card for every Cuvex BIT cryptogram.

    Its additional capacity is intended for certain larger cryptograms created without biometric

    protection.

  • It depends on the cryptogram type.

    Cryptogram without biometrics, Single-signature

    It can be cloned or externally backed up to:

    • Standard Cuvex NTAG216 card.

    • External USB-C storage device.

    Cryptogram without biometrics, Multisignature with all signers mandatory

    It can be cloned or externally backed up to:

    • Standard Cuvex NTAG216 card.

    • External USB-C storage device.

    Cryptogram without biometrics, X-of-6 / N-of-6 where not all signers are mandatory

    This type of cryptogram requires additional storage capacity.

    It can be cloned or externally backed up to:

    Cuvex 8K card, MIFARE DESFire EV1 8K formatted as NDEF.

    External USB-C storage device.

    It cannot be stored on a standard NTAG216 card.

    Cryptogram with biometric protection

    An external backup can only be created on:

    External USB-C storage device.

    It cannot be cloned onto:

    • NTAG216 cards.

    • MIFARE DESFire EV1 8K cards.

    • Any other passive NFC card.

  • Because biometric-protected Cuvex BIT cryptograms are not compatible with passive NFC cards as a

    backup medium.

    This does not mean that there is:

    • An NFC failure.

    • A card-positioning problem.

    • An NDEF formatting error.

    • A problem with the NTAG216 card.

    • A defective 8K card.

    Using a card with more memory will not solve the issue either.

    Although a Cuvex 8K card provides more storage capacity than an NTAG216 card, biometric

    cryptograms must use external USB-C storage devices for external backups.

    Therefore, if a cryptogram was created using Cuvex BIT with biometric access control,

    troubleshooting should not focus on changing between NTAG216 and 8K cards.

    The correct external backup medium is a USB-C storage device.

  • No.

    Cryptograms created with Cuvex BIT using biometric protection cannot be decrypted using the Cuvex

    Desktop App.

    With Cuvex BIT, biometric authentication acts as an additional authentication parameter together with

    the passwords or signatures configured for the cryptogram.

    For this reason, a cryptogram protected with biometrics requires a Cuvex BIT device to complete the

    decryption process.

    The Cuvex Desktop App cannot replace the Cuvex BIT device in this scenario.

    Therefore:

    Cuvex BIT cryptogram without biometrics and compatible with the Desktop App:

    Decryption using the Cuvex Desktop App may be possible, subject to the applicable cryptogram

    compatibility requirements.

     

    Cuvex BIT cryptogram with biometric protection:

    It must be decrypted using a Cuvex BIT device.

    The Cuvex Desktop App cannot decrypt it.

bottom of page