Local AI studio · Creator donations · Market engine · News in 10 languagesTelegramTrading DEX
Vantemio product status

Studio runs on Vantemio’s own channels. News, Academy and Passport are live. Donations run on a test network. Market, Home and Cloud are in development.

All lessons and topics

★ Start here

Trainers

Topics

Vantemio Academy

Free step-by-step lessons with screenshots: where to look and what to tap. Start with lesson 1 and go in order.

Beginner path — in order

  1. 1Internet basics · Steps: 5Your first steps on the internetOpen lesson →
  2. 2Wallet and self-custody · Steps: 5Crypto wallets and self-custodyOpen lesson →
  3. 3DEX and decentralised trading · Steps: 5DEX basics: how to use one safelyOpen lesson →
  4. 4For creators and viewers · Steps: 4Support an author with a Vantemio donationOpen lesson →
  5. 5For creators and viewers · Steps: 3Start receiving donations on VantemioOpen lesson →

Vantemio Academy

CoolWallet Pro and EVEDEX: a practical guide

Step by step: prepare a separate wallet, verify the recovery backup and connect to a DEX without sharing secrets. You do not need to enter secrets on Vantemio.

Open the corresponding step

Before you start

  • A CoolWallet Pro card, compatible phone and charger.
  • Access to the official manufacturer website and app.
  • Paper and pen for recovery information; a private place without screen recording or a camera.
  • A clear choice of asset and network. Do not fund the new wallet before backup verification is complete.

Separate your reserve and working wallets

  1. Assign two purposes: Reserve for longer-term custody and Working for applications and trading.
  2. For an independent reserve, generate new keys on the hardware device. Do not import a phrase already entered into browser or software-wallet storage.
Example

Reserve uses new card-generated keys. Working uses different keys and a limited operating balance. Two addresses derived from one phrase do not provide that separation. The card protects signing keys; assets are recorded on the blockchain.

Check the result

You know which wallet serves each purpose, and the two have independent recovery secrets.

Check the device and install the official app

  1. For Pro, the manufacturer specifies a CC EAL6+ secure element, display and physical confirmation button. First check that this is your exact model.
  2. Open the official CoolWallet website yourself. Follow its application links rather than a message from alleged support.
  3. Charge the card. Select the CoolWallet Pro/S setup flow and the Pro model. Match your card’s serial number when pairing by Bluetooth.
  4. Stop if a device arrives with someone else’s wallet or a prewritten recovery phrase. Contact official support.
Example

Nearby Bluetooth devices may also appear. Match the serial number of your card instead of selecting the first name.

Check the result

The verified app is paired with your own card.

Create a new wallet on the card

  1. Follow the Pro instructions for a new wallet with device-side key generation.
  2. Complete physical confirmations. Do not invent your own recovery phrase or copy an internet example.
  3. Pro and Go use different backup arrangements. Follow the instructions for your exact model.
Example

This manual contains no real seed phrase. A phrase published online is already known to other people.

Check the result

The new wallet was created on your device without importing a previously exposed secret.

Record and verify recovery information

  1. Record the information in the exact format and order used by the official Pro setup. Do not replace numerical recovery data with words you invent.
  2. Complete the backup verification provided by the card and app procedure. If it fails, do not fund the wallet; follow the official instructions again.
  3. Do not photograph or upload the record, send it to support, or paste it into an AI chat. Keep the card separate from its only recovery record.
Example

A paper checklist can say: Model Pro; order recorded; official verification complete; storage location known. Actual secrets stay in your private offline record.

Check the result

The record is legible, ordered and verified. Do not reset a funded wallet to experiment with an unverified backup.

Check the receiving address and network

  1. Open Receive for the intended asset. Compare the network, full address and supported asset with the sending service.
  2. Check fees and withdrawal minimums. If you send a test, use a small permitted amount and wait for receipt before any larger operation.
  3. Check available trusted card display information against the app. Do not rely only on the first and last address characters.
Example

ETH on Ethereum Mainnet and ETH on Arbitrum use different routes. A transfer sent on Ethereum Mainnet must use the matching destination network.

Check the result

The test arrived on the intended network and the address, asset and fee have been checked.

Prepare a separate working wallet for a DEX

  1. A supported software wallet with an independent phrase can handle regular Web3 activity. In conventional setup, MetaMask and Trust Wallet keep encrypted keys on your device.
  2. Never enter the reserve’s recovery phrase into a DEX to connect it. Connecting a wallet does not require giving a service that phrase.
  3. Verify current EVEDEX compatibility for your exact device. If your preferred connection is unsupported, do not work around it by importing the reserve secret into software.
Example

The reserve stays separate; apps use a working address. If a connection page asks for a seed phrase, close it and check the domain.

Check the result

The supported connection method does not expose the reserve secret.

Use the official EVEDEX interface

  1. Open the official EVEDEX site or the referral link below, then verify the destination domain.
  2. Before funding a trading account, read its current network, asset, minimum and fee requirements. Do not automatically reuse the previous ETH example’s settings.
  3. Identify whether a request connects a wallet, transfers funds, signs a message, grants contract access or places a trade.
Example

EVEDEX describes a hybrid DEX, non-custodial access and blockchain settlement. This reduces dependence on a key custodian. Trading losses, contract failures, issuer restrictions and applicable rules remain.

Check the result

You can explain the action, amount, network, recipient and permissions. Otherwise, do not sign yet.

Review each signature and allowance

  1. Match the request to an action you initiated. Check destination, amount, network and any token allowance.
  2. Where supported, limit an allowance to the necessary amount. Review older permissions using officially recommended tools.
  3. Reject unexpected requests for urgent recovery, synchronization or a giveaway. A physical confirmation does not make an unknown contract trustworthy.
Example

Approve usually grants a contract permission; it does not merely open a page. Find the requested asset and limit before approving.

Check the result

You authorize a clear action rather than an unexplained request.

Prepare for loss or suspected compromise

  1. Lost phone: follow official re-pairing instructions rather than sharing a backup with unsolicited support.
  2. Lost card: recovery depends on the backup and a compatible device. Check the manufacturer’s current process first.
  3. Possibly leaked phrase: changing the app password does not change the keys. Stop new connections and prepare a safe move to independent keys using official guidance.
Example

An app problem and a leaked recovery phrase are different incidents. One may require restoring access; the other means the old secret cannot be trusted.

Check the result

You have an offline recovery plan and do not keep treating a potentially exposed secret as secure.

Final checklist

  • Reserve and working wallets use independent keys.
  • Recovery data is offline and officially verified.
  • Network and address are checked before a transfer.
  • Connecting to EVEDEX does not disclose the phrase.
  • Each signature and allowance is understood before approval.