Wallet setup for no-KYC crypto purchases

A no-KYC swap never holds your funds, so the wallet you receive into is the whole security model. Get two things right — a self-custody wallet you actually control, and a deposit address you have verified — and the rest of the process is routine. This guide covers choosing a wallet per chain, backing it up so it survives a lost phone, and the address checks that stop the mistakes people genuinely lose money to.

Set up your wallet in six steps

1. 1

   Pick a wallet that fits the chain you are receiving on

   A no-KYC swap sends to an address you control, so the wallet has to support the exact network of the coin you are buying. Bitcoin, Monero, EVM chains and Solana all use different address formats — one wallet rarely covers all of them well. Choose per chain rather than forcing everything into one app.

2. 2

   Download only from the official source

   Get the installer from the project's own domain or the official app-store listing linked from that domain, never from a search ad, a forum link or an emailed file. Fake wallet apps are the single most common way self-custody funds are lost. On desktop, verify the published checksum or signature when the project provides one.

3. 3

   Create the wallet offline and write the seed phrase on paper

   The 12 or 24 word recovery phrase is the wallet. Write it by hand, store it somewhere fire- and flood-safe, and never photograph it, type it into a password manager sync field, or paste it into a website. Anyone who reads it can spend your funds; no support desk can restore it if you lose it.

4. 4

   Verify the backup with a small test restore

   Before sending anything meaningful, wipe the wallet and restore it from the written phrase, or use the wallet's built-in seed verification. A backup you have never tested is not a backup.

5. 5

   Send a small test deposit first

   Run a low-value swap to the new address before a large one. It confirms the address, the network and the wallet's ability to display incoming funds — for the price of one network fee.

6. 6

   Copy the receive address from the wallet, then verify it

   Use the wallet's copy button or QR code rather than retyping. Then check the address in the swap form against the wallet screen: the first six and last six characters plus the total length. Clipboard-hijacking malware swaps addresses silently, and an address that looks right at a glance can be a different one entirely.

Choosing a wallet by chain

Every wallet below is non-custodial: you hold the recovery phrase and nobody can freeze the balance. Match the chain you are buying on, and check the address format against the wallet before you swap.

Custodial vs self-custody, briefly

A custodial wallet — an exchange account, a broker app — holds the keys for you, which means the provider can freeze, review or lose the balance, and virtually always requires identity verification. A self-custody wallet stores the key on your device or hardware, and no third party can move funds. That control is the point of a no-KYC purchase, and it is also the trade-off: there is no password reset. Your recovery phrase and your address checks are the only safety net.

Verifying the deposit address

• Match the network, not just the ticker

  USDT exists on Ethereum, TRON, Solana, Polygon and more, and the addresses are incompatible. Pick the network in the swap form that matches the wallet screen you copied from — Monivo blocks a checkout when the requested destination network is not one the route can actually deliver on.

• Check the first and last characters after pasting

  Compare six characters at each end plus the length against the wallet. This is the cheapest defence against clipboard malware, which replaces a copied address with an attacker's one of the same shape.

• Prefer the QR code when moving between devices

  Scanning removes both transcription errors and clipboard tampering. Verify that the scanned result still matches the address shown on the receiving wallet.

• Never paste an address someone sent you

  The only trustworthy source of your receive address is your own wallet, open in front of you. Addresses forwarded in chat, email or support tickets are the classic support-impersonation scam.

• Watch for address-poisoning entries in your history

  Attackers send dust from an address whose first and last characters mimic one you have used, hoping you copy it out of your transaction history later. Always re-copy from the wallet's receive screen, never from history.

• Confirm the address is one you can spend from

  A watch-only wallet, an exchange deposit address or someone else's address will all accept funds. Only an address whose seed phrase you hold is self-custody. If you cannot sign a transaction from it, it is not your wallet.

Common mistakes to avoid

Almost every lost no-KYC payout comes from one of a handful of errors, and most of them happen in the seconds between copying an address and pressing send. Here is what each one looks like in practice, why it happens, and what to do next if it already has.

• Sent an EVM token to the right address on the wrong chain

  Usually recoverable

  Example: You buy USDC and pick Ethereum in the swap form, but the 0x… address you pasted is an Optimism-only account in a wallet that does not expose Ethereum mainnet. The transfer confirms — on a chain where you cannot see or spend it.

  Why it happens: Every EVM chain shares the same 0x address format, so the address itself never reveals the network. Only the network selector does.

  What to do next: Import the same seed phrase into a wallet that supports the receiving chain (Rabby or MetaMask with a custom RPC), add the token contract manually, then bridge it back. You need a little of that chain's native gas coin first. If the address is a smart-contract wallet or an exchange deposit address rather than a seed-controlled account, stop and contact that provider — do not send more.

• Sent BEP-20 to a Bitcoin, Solana or TRON address

  Not recoverable

  Example: You paste a bc1… or T… address into a BNB Chain withdrawal. Most interfaces reject the format outright; the ones that do not create a transfer to an address nobody holds a key for.

  Why it happens: Address formats are chain-specific. A bc1… string is not a valid EVM account, so any coins routed to its hex interpretation land in an unowned account.

  What to do next: If the send was blocked, nothing was lost — reselect the network and retry. If it broadcast, the funds are gone; there is no key and no support desk that can reverse it. Treat it as a lesson to always run a small test deposit before a full-size swap.

• Used the token's address instead of your wallet address

  Not recoverable

  Example: You copy 0xdAC17F958D2ee523a2206206994597C13D831ec7 out of a block explorer — that is the USDT contract, not a personal account — and set it as the payout address.

  Why it happens: Explorer pages show the contract at the top of the page, and it looks exactly like a wallet address.

  What to do next: Contract-held tokens are effectively burned. Always copy the address from your wallet's own receive screen, never from an explorer, a chat message or a search result. Cancel the order if the deposit has not been sent yet.

• Pasted a clipboard-hijacked or poisoned address

  Not recoverable

  Example: The address you paste starts and ends with the same characters as yours, but the middle differs — either malware swapped the clipboard, or you re-copied a dust transaction an attacker sent to your history to mimic your own address.

  Why it happens: People check the first and last few characters and skip the middle, which is exactly what both attacks rely on.

  What to do next: If the deposit has not been sent, re-copy from the wallet receive screen and compare six characters at each end plus the total length. If it has been sent, the funds are with the attacker — move the remaining balance to a freshly generated wallet on a clean device, then scan the compromised machine.

• Sent to an exchange deposit address instead of self-custody

  Sometimes recoverable

  Example: You route a no-KYC swap payout straight into a centralised exchange deposit address to save a step. The exchange flags the inbound as coming from a swap service and asks for identity documents or source-of-funds before releasing it.

  Why it happens: Custodial deposits are screened. The privacy of the swap ends the moment funds touch an account someone else controls.

  What to do next: Complete the exchange's process or open a support case — only they can release it. In future, receive into a wallet whose seed phrase you hold, and move to an exchange later if you actually need one.

• Left off a required memo, tag or payment ID

  Usually recoverable

  Example: A TON, XRP or Cosmos-style deposit to an exchange goes through without the memo field, so it credits no account.

  Why it happens: Custodial venues pool user funds in one address and use the memo to attribute the deposit. Your own self-custody wallet never needs one.

  What to do next: Open a support ticket with the transaction hash — most venues can credit it manually, sometimes for a fee. Deposits to your own wallet are unaffected and need no memo.

• Received on a chain you have no gas coin for

  Usually recoverable

  Example: USDT lands on TRON or Arbitrum, but the wallet holds zero TRX / ETH, so the balance is visible and completely immovable.

  Why it happens: Every transfer costs the chain's native coin, and tokens cannot pay their own fee.

  What to do next: Buy a few dollars of the native coin — TRX, ETH, SOL, TON — into the same address with a second small swap, then the tokens move normally. Nothing is lost, only stuck.

• Restored into the wrong derivation path or account and assumed funds were lost

  Usually recoverable

  Example: You restore a 12-word seed into a new wallet, the balance shows zero, and you panic-send more funds elsewhere.

  Why it happens: Wallets default to different derivation paths and address types (legacy vs SegWit vs Taproot on Bitcoin, account index on EVM). The coins are on the seed, just not on the addresses that wallet scanned.

  What to do next: Switch the wallet's address type or derivation path, or restore into the original wallet software. Check a watch-only view of the old address on an explorer to confirm the funds are untouched before doing anything else. Never enter the seed phrase into a website or a 'recovery service'.

Before you press swap

Run through this once: the destination network in the quote matches the wallet you copied from; the pasted address matches character-for-character at both ends; the recovery phrase is written down and tested; and you have a small amount of the chain's native coin for future fees. When all four are true you can send the deposit, and the payout lands in a wallet nobody else can touch.

Related: What is KYC in crypto? · Buy Bitcoin with no KYC · Best no-KYC crypto exchanges · Best Monero wallets