CuvexACADEMY

· Edition 0.1

Student manual

Free · no registration

All sections
Cuvex operating manual

This manual accompanies the lessons. Each procedure describes the workflow found in the reviewed sources, its checks and its stopping point. This is a pilot candidate edition. It does not attest to independent physical tests with Original, BIT, phones or every desktop platform. Before teaching with real funds, the team must complete the acceptance matrix and adjust any labels or screens that differ.

References: Original 1.2.2 Final, BIT 1.2.3 Final, Desk 1.0.0-beta.9.21 and Mirror 1.0.0-beta.12.12. Selecting a profile in Desk declares compatibility. It does not remotely measure firmware. The included Mirror screenshots come from the Android emulator for package 12.12. The product photographs are corporate materials and do not prove which version a current device displays.

P01 | Check provenance and version | Cuvex | L16,L21 | C01,C02

Preparation: Have the purchase details and an official channel you can verify independently. Do not enter any secrets yet.

  1. Inspect the packaging and seals. If you see signs of tampering, stop setup and retain nonsensitive evidence.
  2. Use the integrity and seal-check workflow in the app compatible with your delivery. Enter codes only there, never with the tutor.
  3. Identify whether you have Original or BIT and which revision is available. Check the versions displayed by the device and applications.
  4. Compare them with the team’s published matrix. Neither a catalog nor a hash replaces firmware authentication or physical acceptance.

Result: The model and versions have been identified and the source checked without exposing secrets. If the codes are invalid or the interface differs, do not use a historical guide to force operation.

Pause: Stop before loading custody material. Commercial traceability alone cannot guarantee the absence of sophisticated tampering.

P02 | Update Original over Bluetooth | Original | L46 | C01,C02,C03

Preparation: Have recoverable backups, stable power, a compatible official package and an accepted workflow for your system. This course does not establish complete physical availability on every platform.

  1. In the app’s devices or firmware section, select Original and the official download or corresponding authentic local file.
  2. Use the device menu to enter update mode and connect through the application workflow. Stay nearby and avoid competing sessions.
  3. Enter the code shown by Original in the specified field. It is separate from the cryptogram password.
  4. Follow transfer, validation, installation and reboot. A percentage alone does not prove installation.
  5. Check the final version on Original and record it in the app if the corresponding field exists.

Result: The device screen confirms the version after reboot and the workflow confirms completion. If it fails before the PIN, during packet transfer or at the end, record the stage and code. Do not improvise a disconnection or software change to “get past 99%.”

P03 | Update BIT over USB | BIT | L46 | C01,C02,C03

Preparation: Identify BIT’s actual storage medium, power supply and compatible official package. Retain backups before changing software.

  1. Select BIT in the compatible Desk or Mirror firmware workflow.
  2. Connect the device using the appropriate data cable and adapter. Authorize volume or folder access when requested.
  3. Select authentic firmware for the model. Check the version and compatibility details before transferring it.
  4. Wait through transfer and device validation. A volume may disappear and be mounted again as the protocol proceeds.
  5. After reboot, check the version on BIT and the final result in the app.

Result: Installation has been checked on the device itself. If the volume does not appear, check device mode, data cable, permissions, mounting and competing active sessions. A PC folder with the same name cannot substitute for it. Recovery after a failed update requires the official procedure for that hardware.

P04 | Generate a wallet with a coin and dice | Cuvex | L17 | C01

Preparation: Use a private space, suitable dice and a coin, with the tutor microphone off and no cameras. Use a learning wallet.

  1. Open wallet creation and the firmware’s entropy workflow. Fix the order of the four dice before starting.
  2. Enter the coin result and each die as the screen directs. Never change a result to suit a preference.
  3. The reviewed source computes index = coin × 1,296 + (d1−1) × 216 + (d2−1) × 36 + (d3−1) × 6 + (d4−1). It accepts only indices 0 through 2,047.
  4. On rejection, flip the coin and roll all the dice again. The warning retains the previous words and asks for a new complete set.
  5. Complete the device algorithm including final validation, protect the mnemonic and test recovery privately.

Result: The wallet was generated through the full procedure without manually selecting words. Stop if the screen and source disagree. Never adopt a public example of dice, seed or key as your own material.

P05 | Encrypt a secret | Cuvex | L18,L19 | C01

Preparation: Choose model, content format and protection. Entering a secret on a PC or phone exposes it at the source even when the destination is encrypted.

  1. Select encryption and a supported type: BIP39, SLIP39, Monero or text. Do not interchange wordlists. The reviewed plaintext keyboard accepts up to 500 characters. Storing another format does not imply support for signing on its network.
  2. Enter the content directly on the device to maintain isolation. Review order, characters and additional fields on its screen.
  3. Choose individual or shared protection according to the workflow, and biometrics on BIT if appropriate. Distinguish this threshold from the Bitcoin threshold.
  4. Privately enter and confirm the passwords according to the firmware validator. Do not automatically apply Desk’s rules.
  5. On Original, write to a compatible blank card. On BIT, retain the export objects created by the USB workflow. Wait for confirmation.
  6. Start a test recovery to verify the contents, then close the secret display.

Result: The cryptogram has been checked through recovery. If a read or write fails, protect the original and follow the screen’s retry procedure. Do not delete headers or force overwrites.

P06 | Decrypt on the device | Cuvex | L18 | C01,C02

Preparation: Ensure physical privacy and sufficient unlocking components. Turn off nearby microphones and screen capture when working with the secret.

  1. Start decryption on the correct model and supply the cryptogram through NFC on Original or the BIT USB workflow.
  2. Check the alias and object identification before entering credentials.
  3. Supply the required passwords and biometrics if the format requires them. Avoid repeated automatic retries after failures. Access controls and lockouts apply.
  4. Verify the contents only on the intended display. A QR code representing the secret is just as sensitive as its text.
  5. Close or end the process as the device directs, and store the medium and credentials separately according to your plan.

Result: The contents have been recovered privately and the session has ended. If the format is unrecognized, authentication fails or the contents are unexpected, do not “fix” them using an unknown app. Give support the version, format and error without attaching the secret.

P07 | Prepare recovery of a biometric cryptogram | BIT | L19,L47 | C01,C02

Preparation: Use a learning cryptogram and documentation for its format. A .bin copy alone does not establish recoverability.

  1. In the Desk details view, identify any biometric components and the available recovery export.
  2. Retain the full set of files associated by the workflow and an independent copy, using discreet identifiers.
  3. Test normal unlocking on BIT and document the passwords and conditions it requires.
  4. Study the exceptional local recovery method and its supported formats. Verify the necessary material exists before you need it.
  5. Use data with no funds to rehearse device failure or an unavailable fingerprint.

Result: You have a tested plan with defined limits for that specific format. This does not imply that any biometric requirement can be bypassed or that a fingerprint replaces backups. If a secret is recovered on a PC, assess its exposure and whether control should be moved afterward.

P08 | Create and check a cryptogram backup | Cuvex and Desk | L20 | C01,C02

Preparation: Identify the original and choose a compatible destination without data you need to retain.

  1. On Original, use the device’s clone function or the compatible Desk function. Present source and destination in the specified order.
  2. Hold cards steady and respect rejection of media that already hold cryptograms.
  3. For BIT or a file, export the complete set of components and preserve the required names or associations.
  4. Isolate the original copy and test reading and recovery from the new one.
  5. Privately record the date, format and result. Store the copies where they face independent physical risks.

Result: A second copy has passed testing. It is not another wallet, does not revoke passwords and provides no protection against an already leaked seed. If the destination fails, retain the original without trying to “repair” it to make the copies match.

P09 | Create and unlock Desk storage and change its password | Desk | L21,L40 | C02

Preparation: Use a verified installer and the correct architecture. Have a backup plan for the store.

  1. Create the store with a unique password of 12 to 1,024 characters and matching confirmation.
  2. Lock and reopen it to verify access. Enter the password only in Desk.
  3. Under Security and Access and Locking, review inactivity and background behavior. Keep optional erasure off during a demonstration.
  4. To change the password, enter the current one and confirm the new one through the appropriate workflow.
  5. If you used PC biometrics, configure them again as instructed. Make a current backup and retain the relationship to prior copies.

Result: Access is confirmed. Earlier copies retain their original password and encryption. PC biometrics and BIT biometrics are distinct. If access fails, stop repeated attempts and review recovery without asking the tutor to store credentials.

Preparation: Use a test cryptogram of known origin and an available transport method.

  1. Open Cryptograms or Cards and choose to link via NFC, USB or a compatible backup.
  2. Select the design and source. For NFC, use Cuvex Mirror paired with the computer over Bluetooth. Alternatively, use the volume of a Cuvex BIT connected by USB-C. Cuvex Desktop does not support external USB NFC readers.
  3. Review alias, source, size, format and interpreted access conditions in the details view. These are metadata, not decrypted contents.
  4. Check for retained accounts awaiting association and link only the verified account.
  5. Export a copy if backup coverage is incomplete and test recovery separately.

Result: The object is organized locally. “Linked” proves neither seed authenticity nor balance. For an unrecognized object, check format and version. Do not change its extension or delete data to force acceptance.

P11 | Activate a watch-only WOW account | Desk and Cuvex | L13,L22 | C01,C02

Preparation: Have the public information obtained through the device workflow and privately verify its origin.

  1. Open Activate WOW or Add Account from the correct cryptogram.
  2. Import the supported descriptor or public material through file, webcam or Mirror as the function permits.
  3. Review network, script, origin, fingerprint, path and checksum where applicable. Never enter a seed or xprv.
  4. Name the account and make an informed choice of query source.
  5. Check a verification address and the scope of discovery before interpreting the balance.

Result: The watch-only wallet is associated. A zero balance calls for checking network, original passphrase, derivation, account, provider and scan before concluding that coins disappeared. Networks supported by a general interface may not be supported by the multisignature profile. Respect the context.

P12 | Configure the node and synchronization | Desk | L25,L33 | C02

Preparation: Decide what privacy you need. If using Core, have access to a protected, synchronized node.

  1. Under Security and Privacy and Nodes, select the WOW account and review its provider.
  2. Explicitly choose a supported public provider or Core. For Core, enter endpoint, wallet and credentials only in the application.
  3. Authorize the query after considering what data each service receives. TLS does not hide the query from the provider.
  4. Synchronize and review date, chain tip, progress and completion state. For a rescan, check the period covered and continuity of the work.
  5. On HTTP 429, respect the pause. If the provider fails, do not assume another node took over. The configuration does not rotate silently.

Result: You know the source and its state. Do not expose RPC to the internet, share the password or restrict discovery to addresses with a balance. An empty history may be only a partial result.

P13 | Generate and retrieve a receiving request | Desk and Cuvex | L26 | C01,C02

Preparation: Verify the account, network and policy.

  1. Open Receive and generate or retrieve the appropriate request.
  2. Add observer, reason and expected amount only if you need those local metadata.
  3. Verify the address through the compatible device workflow before receiving a significant payment. Where physical acceptance is outstanding, stop the exercise at simulation.
  4. Share only the necessary data over the recipient’s authenticated channel.
  5. Check receipt, amount and confirmations through your network source.

Result: The payment has been reconciled, beyond merely issuing a request. Multisignature addresses already displayed are kept for late payments and never reassigned. If you reach the limit for new addresses without history, retrieve previous requests. Do not force indices manually.

P14 | Labels, freezing and BIP329 | Desk | L27 | C02,B13

Preparation: Use a lab account with UTXOs and a password for protected export.

  1. Label an input with its context, omitting unnecessary personal information.
  2. Freeze or unfreeze deliberately and review the spendable balance. The restriction is local.
  3. Export labels using the protected function. Distinguish the BIP329 format from file encryption.
  4. Import into a compatible copy and check that references, labels and freeze states match.
  5. Keep a current backup of the metadata with its associated password according to your plan.

Result: The context is preserved and selection understood. Never let an import automatically unfreeze coins without review. Do not send the tutor the label file. It may reveal counterparties and relationships without containing spending keys.

P15 | Prepare a payment and send the entire balance | Desk | L28 | C02

Preparation: Have a verified request and an account with sufficient spendable inputs.

  1. Open Pay from WOW, UTXOs or chat and confirm the account and network.
  2. Select inputs, recipients and amounts. Review which contexts you are connecting.
  3. Choose the fee rate and review the absolute fee, change and warnings. If there is dust, consider alternatives without accepting a hidden fee.
  4. To send all, check the net amount after fees. In chat, explicitly confirm a partial payment if it does not cover the request.
  5. Prepare a draft and review every detail before exporting for signing.

Result: The intent is clear and the PSBT belongs to that transaction. A general form may accept more inputs or recipients than the hardware. Apply the effective limits of signer and transport. A change to outputs or conditions starts a new review.

P16 | Sign and return a PSBT with Original | Original and Mirror | L29 | C01,C02,C03

Preparation: Have the correct draft, compatible transport card, compatible authenticated cryptogram and a private way to unlock it. An older copy without verified authenticity may require verified recovery and creation of a new copy before signing. Editing its header does not fix it.

  1. Export the request through the compatible NFC workflow from Desk/Mirror.
  2. Take it to Original. Supply the cryptogram when requested and unlock it without dictating credentials.
  3. Review network, summary, complete outputs, fee, change and mandatory warnings.
  4. For Final multisignature, decide whether to examine extended parameters. Complete the three final confirmations only if everything matches.
  5. Wait for the response to be written to the card and read back.
  6. Read the response with Cuvex Mirror and validate it in the corresponding Desk operation.

Result: The signature has been received and linked to the draft. It has not yet been broadcast. If writing fails, retain the state and follow the retry process. Never use a backup card as disposable payment transport.

P17 | Sign, receive and acknowledge with BIT | BIT and Desk | L29 | C01,C02

Preparation: Have the correct draft, a compatible authenticated cryptogram and the actual BIT volume selected. If an older copy is rejected for signing, follow the indicated recovery and renewal procedure without forcing the format.

  1. Deliver the request over USB-C through Desk’s service. Follow the device screen for the cryptogram.
  2. Unlock privately and review the summary, every output, the fee and the warnings.
  3. For Final multisignature, optionally inspect the extended details. Authorize with the mandatory final confirmations.
  4. In Desk, use Receive from BIT to import and validate the response for that job.
  5. Check that the response is saved and acknowledged. If acknowledgment fails after receipt, retry the same operation. Do not allow the model to select a different one.

Result: The signature is verified and exchange state is consistent. If disconnection occurs before receipt or after saving, retain the request’s profile. Never switch to another firmware entry in the catalog to make a pending response fit.

P18 | Finalize, broadcast and monitor a transaction | Desk | L30,L44 | C02

Preparation: Have verified signatures and a sufficient threshold where applicable.

  1. Review the intent, inputs, outputs, fee and network again.
  2. Use the appropriate action to finalize and verify that no signatures or conditions are missing.
  3. Authorize broadcast and retain the local result. If the network response is lost, check before retrying.
  4. Track the mempool and confirmations through the selected provider, noting the synchronization date.
  5. If considering RBF, review the new transaction and obtain the required signatures. Do not assume built-in CPFP support.

Result: Chain state has been checked against its source. Canceling a draft does not revoke exported signatures or rewrite confirmed payments. A chat message or screenshot cannot replace monitoring.

P19 | Compare two policy QR codes in any order | Mirror | L43 | C03,C02

Preparation: Have the field visible in Desk and Cuvex. During practice, use only the course’s synthetic samples.

  1. Open Compare Policies and scan either side first.
  2. Choose whichever field you want to check. You may begin at step 15 and skip fields you reviewed manually.
  3. Scan the counterpart and review both complete texts. If the step is ambiguous, use Specify Desk Step and remember that this context is entered manually.
  4. Interpret Match or No Match only for that literal pair. Spaces, capitalization and encoding count.
  5. Start another pair in any order. Exit or move to the background to finish according to the reviewed clearing behavior.

Result: This is a local check of one pair. It does not establish origin, session, overall approval or activation. Clarify any discrepancy with the sources. Do not normalize the text to force an OK.

P20 | Activate, recover and move chat | Desk and Cuvex | L36,L39 | C02

Preparation: Choose DEV or Production. Have an alias and Chat Key on the device, never in the course.

  1. Open chat activation or recovery from the cryptogram context.
  2. Choose a new alias or transfer an existing one. Select the compatible mobile profile specified by the app.
  3. Enter or read the Chat Key exclusively through the private workflow. Do not use a seed, PIN or WOW key.
  4. Check activation with the service. If it is pending, use the completion or verification action rather than assuming success.
  5. Verify continuity with contacts after a transfer. Avoid using one alias on several devices simultaneously.

Result: The identity is activated or recovered in the correct environment. Neither the Chat Key nor the full Desk backup automatically recovers past history and sessions. Respect the limits of the available material.

P21 | Verify a contact’s identity | Desk | L36,L48 | C02

Preparation: Have an independent channel agreed in advance with the person.

  1. Add the alias and inspect its public identity through the app.
  2. Compare the fingerprint through the authenticated channel, not just inside the newly created conversation.
  3. If using recognition questions, avoid public information and secrets reused on other services.
  4. Confirm only after all discrepancies are resolved. Suspend payments and coordination after an identity change until it is verified.
  5. Document the verification method without storing sensitive answers in the course.

Result: You have contextual trust in the contact, without a guarantee covering every future request. A voice can be imitated and a legitimate device compromised. Each operation still needs review.

P22 | Request an address, request payment and pay through chat | Desk and Cuvex | L37 | C02,C01

Preparation: Have a verified contact and a compatible WOW account.

  1. Choose Request Address, Reply with Address or Request Payment according to your intent.
  2. Review the original request, network, amount and note before sending it.
  3. To pay, start preparation from the correct account, select UTXOs and fee rate and review the net amount.
  4. Authorize on Cuvex following the procedure for your model. Chat never signs automatically.
  5. Track broadcast and confirmation through your source. Reconcile any explicitly agreed partial payment against the original request.

Result: Chat has provided coordination while preserving custody review. Message status and transaction status are distinct. An explorer link may send information to a third party. Assess it before opening it.

Preparation: Identify a concrete reason for sharing, verify the contact and define which means of access the contact will receive.

  1. Choose Share Cryptogram from the chat action and review the object.
  2. Do not attach passwords, a seed or a Chat Key as a comment.
  3. The recipient checks provenance and links the supported object through the receiving action.
  4. Consider what capability the recipient obtains immediately and what they could obtain with sufficient unlocking credentials.
  5. Keep a realistic revocation plan. Deleting messages does not remove external copies or revoke known keys.

Result: An encrypted object has been deliberately transferred. This does not make a payment or independently add a key to a multisignature wallet. If the attachment directs you to an unknown webpage for decryption, stop the workflow.

P24 | Make and restore a full Desk backup | Desk | L15,L21 | C02

Preparation: Use a learning store and a controlled backup destination.

  1. Open the store backup function and set the requested password. Keep track of which password belongs to this particular backup.
  2. Store the backup away from your only working device. Follow the workflow to check provenance and integrity.
  3. Restore it in a separate test environment and verify the covered accounts, settings and data.
  4. Review exclusions. Do not assume chat, its sessions and history are included. A multisignature policy and private keys are not interchangeable.
  5. Repeat after major changes and retain recovery instructions.

Result: You know the backup’s scope and password. Older backups retain older passwords. When access changes or a secret is exposed, assess those copies as well as the current store.

P25 | Create and accept a multisignature wallet | Desk and Cuvex | L41,L42 | C01,C02

Preparation: Have independent participants, verified contacts and agreement on the network and effective limits.

  1. The creator chooses the name, M/N, network, participants and operational validity period.
  2. Supply the correct extended public key with fingerprint and BIP48 path through the supported workflow.
  3. Each participant reviews, accepts or rejects and supplies their public material. No participant shares a seed.
  4. Build the complete policy and prepare to verify it on each device.
  5. Keep policy backups before funding. Check a verification address and the ability to recover.

Result: The proposal is complete and verifiable. Accepting an invitation cannot replace hardware review. If Original participates, apply its six-key maximum and the NFC size limit. BIT does not increase other participants’ capabilities.

P26 | Verify a policy and receive confirmation | Desk and Cuvex | L43 | C01,C02,C03

Preparation: Give everyone the same complete policy. Use the correct firmware profile and a device without competing operations.

  1. Start Verify Policies in the supported context. Original requires explicit selection of the installed profile. BIT negotiates capabilities under its specification.
  2. Deliver the request by NFC/Mirror or USB-C according to the model.
  3. Review the policy fields on the device. You may use Mirror to compare selected pairs in any order.
  4. Complete device confirmation and return the response through the appropriate transport.
  5. In Desk, validate the response for this request. A visual OK from the comparator cannot replace that step.

Result: The response is correlated and applies to this review. The catalog does not remotely attest firmware, and the device is not presented as a persistent policy store. On FIRMWARE_CAPABILITY_REQUIRED, first check the Desk version and model/build combination.

P27 | Request and receive signatures and hand over coordination | Desk and Cuvex | L44 | C01,C02

Preparation: Have a verified policy, an identified transaction and agreed recipients.

  1. Prepare inputs, outputs, fee and notes and request signatures from compatible participants.
  2. Each participant reviews and signs on their device through its transport workflow.
  3. Receive, validate and save each signature. Resolve pending acknowledgments without changing the saved profile.
  4. On handover, the recipient accepts the coordination workflow and checks its state. This changes neither M/N nor key ownership.
  5. Once the threshold is reached, review and finalize before broadcasting. Track the transaction on the network.

Result: You have separate evidence for each coordination step. A coordinator’s progress report is distinct from your own local check. Canceling or rejecting in one app need not destroy signatures already retained by others.

P28 | Export, restore and locally delete a multisignature wallet | Desk | L45 | C02

Preparation: Have a known policy and a backup encrypted with a unique password.

  1. Use Desk’s recovery export. The current workflow uses an authenticated CVXMSBK1 container for this export.
  2. Keep the copy and password exposed to independent risks. Do not infer encryption from the extensions of older files.
  3. To restore, supply the backup, password and participant public key with the correct origin, using webcam or Mirror if applicable.
  4. Check policy, network, address and discovery before operating.
  5. For local deletion, read the scope and confirmation. Keep a backup if you want to retain recovery. A later restore is an explicit action.

Result: The policy can be recovered, or local state was deliberately removed. Deletion does not move funds, erase other signers’ keys or automatically cancel operations retained by others.

P29 | Perform exceptional recovery on a PC | Desk | L47 | C02

Preparation: Have supported-format material, a prepared clean environment and a backup. This operation may reveal a secret to the PC. Use learning data during the course.

  1. Start local recovery from the correct context and read the format restrictions and warnings.
  2. Consciously accept the risk and disconnect the network as the workflow requires. The window checks connection state before allowing you to proceed.
  3. Enter only the required credentials in the private window. Do not dictate them, paste them into the course or share them with support.
  4. Enable viewing only in a space free of cameras and listening assistants. Respect the timer and closing behavior.
  5. Finish, consider the exposure that may have occurred and plan migration to new keys if necessary.

Result: This is exceptional recovery. It does not guarantee forensic erasure or equivalence to isolated hardware. If authentication, format compatibility or access material is missing, do not test internet tools on the real backup.

P30 | Review preferences, biometrics and locking | Desk | L40 | C02

Preparation: Know the password and verify a tested backup before changing security.

  1. Under Access and Locking, review password, available biometrics, inactivity and locking when the app goes into the background.
  2. Understand the delay after failures and the configured maximum before changing it.
  3. Keep optional erasure disabled until you understand its conditions, threshold and recovery. Never test it in production.
  4. Under Preferences, adjust language, theme, currency, 3- or 5-minute synchronization and sounds.
  5. If you register bitcoin: links, verify that opening a request still requires unlocking, selection and review. Opening the link does not pay by itself.

Result: You understand the configuration. Operating-system biometrics depend on the device and replace neither the password nor the backup. Visual preferences do not modify Bitcoin policy.

P31 | Delete records with a clear understanding of scope | Desk | L22,L45 | C02

Preparation: Identify whether you are deleting a local cryptogram, account, WOW record, chat or multisignature wallet and which backup you will keep.

  1. Read the selected object and its warning. Confirm the exact alias or explicit condition when the app asks.
  2. Export and test a backup if you need to recover that state later.
  3. Delete only the intended object and check which associations the workflow keeps or removes.
  4. Check for outstanding operations or outside participants. Do not assume messages, signatures or files disappear from other devices.
  5. Document the change in your private inventory without adding sensitive data to the course.

Result: Local state has been deliberately managed. None of these actions alone changes the scripts of funded UTXOs, destroys a seed known to others or reverses confirmed transactions.

P32 | Diagnose problems without exposing secrets | Desk and Mirror | L23,L30,L48 | C02,C03

Preparation: Note the approximate time, system, architecture, version and stage. Avoid repeatedly triggering a sensitive operation whose state is unknown.

  1. Identify whether the failure involves search, pairing, reading, writing, validation, signing, return, network or display.
  2. Copy the error code and text without QR codes or private data. Use the app’s diagnostics where appropriate.
  3. Review the file before sharing it. Do not attach a store backup, cryptogram, seed, Chat Key, descriptor or RPC credential.
  4. For an interface issue, record window size, zoom and hidden controls using a synthetic scene.
  5. Send the expected result and reproducible steps through the official channel. The course does not automatically send messages to support.

Result: The report allows investigation with minimal data. Record a stage lacking evidence as “pending” rather than “completed.” Voice assistance does not need remote access to your custody device.

Download PDF ↗

You can keep reading without an account. To share progress with TutorAI, activate a code.