A successful test is not a security certificate. Intact packaging, an authenticity check and a successful transfer each answer different questions. Stop if you receive prewritten recovery words, a preconfigured PIN or suspicious hardware. Start with our supply-chain and buying checklist.

Prepare a quiet setup session

Use a device from a verified source, a computer or phone without known infection, and offline backup materials. Obtain companion software through the manufacturer's website, not an unsolicited support message. This guide provides a sequence, not universal menu instructions: brands, models and firmware versions differ.

Before funding, write down which assets and networks you intend to use. A useful setup note says “USDT on Ethereum, account one,” not simply “dollars.” Keep operational notes private and separate from your secret backup.

1. Verify the device, then generate fresh keys

Complete the model-specific checks and firmware procedure. Pause on an unexplained warning; a factory reset does not repair malicious hardware. The official Trezor Safe 3 setup guide, for example, separates creating a wallet from recovering an existing one.

For new cold storage, let the verified, trusted device create a new backup. Importing words previously used in a phone wallet does not undo their earlier exposure. Moving assets from that wallet requires an on-chain transfer to the new addresses, not just importing the old words. Reject seller-generated recovery phrases and PINs.

2. Record the right backup format

Record the complete backup in order without photographing, uploading or messaging it. Not every wallet uses 24 words. BIP39 and SLIP39 differ; multi-share recovery also requires its threshold. Check replacement-device compatibility rather than cutting a word list into pieces yourself. See Trezor's backup-format explanation.

Use a private label and creation date so you can distinguish backups later. Consider theft, water, fire and access by other people when choosing storage. Do not publish the location alongside your balances or address history.

3. Check the backup without erasing your only device

Use the verified manufacturer's check for your model. Trezor Model T's Check backup compares the recorded backup without clearing the wallet. Input procedures vary; prefer supported on-device entry. Never put the full backup into a website, chat or online “validator.”

Do not wipe your only funded device to test an unverified backup. Resolve a failed check before destroying records. A full restoration rehearsal belongs on a trusted spare device after confirming the backup, account information and compatible format.

Understand PIN versus passphrase

A PIN unlocks a particular device. A passphrase contributes to different wallet keys: a changed space or character can open an empty wallet. It cannot be reset by support. It is optional, not a cure for compromised hardware. If you use one, follow the official passphrase guidance and verify repeated access before funding.

4. Test the complete transfer route

  1. Confirm support: the sending service, hardware and companion software must support the asset and the same network. A ticker alone is not enough.
  2. Verify the full address: display it through the device's receive workflow and compare every section with the final sending screen. Do not copy an unfamiliar address from transaction history.
  3. Check conditions: review withdrawal minimums, fees, expected received amount and any required memo or tag. Plan for the network's native fee asset when sending out later.
  4. Send a small test: choose an amount above the service's minimum that you can afford to lose. Confirm the actual network, token contract and receipt before moving the remainder in manageable batches.
  5. Practise sending: where fees make sense, send a small amount to another address you control, reviewing the destination, amount and fee on the device.

Ledger's Ethereum guide describes device-based receive-address verification; its sending guide recommends a small first transfer. These checks test a route, not hardware integrity or the safety of future signatures.

Keep receiving separate from authorizing

Do not turn long-term storage into an everyday airdrop or unfamiliar dapp wallet. Ordinary receipt does not require an unlimited token approval to a stranger. Use the multichain explorer directory with public addresses or transaction hashes only. For an incident, follow the loss and compromise response guide.

Reviewed October 18, 2026. No setup procedure guarantees absolute safety. Check current documentation for your exact device, software and network.