This walkthrough uses Bitcoin Cash because a small first transaction is practical, but the safety process applies to most cryptocurrency wallets. Interface labels vary, so read the wallet's current documentation before moving meaningful value.
If you are still choosing between wallet types, start with the beginner wallet selection guide. For backup and recovery planning, read crypto wallet security.
1. Choose a maintained wallet
Confirm that the wallet supports BCH mainnet, the current CashAddr format, and any CashTokens you intend to use. Check its custody model, recovery format, update history, and official distribution channels.
Electron Cash is one established non-custodial BCH option. Its desktop release supports hardware-wallet integrations, CashFusion, and CashTokens; do not assume that every desktop feature or menu is also present in a mobile app. Follow the official site's platform-specific download links and signature-verification instructions rather than an advertisement or copied download page.
The recovery example below uses Electron Cash 4.4.6, checked on 12 September 2026. Recheck the current release when following this guide. The project's wallet documentation is the starting point for platform-specific help.
2. Create a new wallet privately
Use a trusted device, choose "new wallet," and let the wallet generate its own randomness. Do not use a seed phrase from a tutorial, screenshot, support message, or online generator.
If the wallet displays a recovery phrase:
- write it down away from cameras and screen sharing;
- preserve the word order exactly;
- do not paste it into notes, email, cloud storage, or a website;
- complete the wallet's backup-verification step;
- record non-secret details needed for recovery, such as wallet name and network.
An optional passphrase creates a separate wallet and can permanently block recovery if forgotten. Do not enable one until you understand how it changes the backup.
3. Verify the receive screen
Select BCH and open the receive view. A BCH CashAddr commonly starts with the network prefix "bitcoincash:" when written in full, followed by an address payload. Some interfaces omit the visible prefix; token-aware destinations can use a different address type.
Confirm the network and copy the address from the wallet itself. Never substitute an address from this or any other article.
4. Receive a small test amount
Send a small amount from another wallet, exchange withdrawal, or a trusted sender. On the sending side, verify that the selected network is Bitcoin Cash rather than Bitcoin or another similarly named network.
The incoming transaction may appear before it is included in a block. That is an unconfirmed observation, not final settlement. Wait for the number of confirmations appropriate to the amount and your risk tolerance.
5. Send a small transaction
Obtain a fresh BCH destination from a wallet you control or a trusted recipient. Check the complete address, amount, unit, and fee before signing. If a hardware wallet is involved, verify those details on its own display.
After broadcast, compare the transaction ID shown by both wallets or inspect it in a BCH block explorer. Do not judge success from a screenshot alone.
6. Confirm recovery before scaling up
Use the wallet's documented backup check. A full restore test should use trusted software and a safe procedure; do not type a funded seed into an unfamiliar online device merely to experiment.
What we checked with an unfunded wallet
On 12 September 2026, we created and restored an in-memory BIP39 practice wallet using the official Electron Cash 4.4.6 Python library on Windows, with Python 3.12.14. We used newly generated recovery material, kept it out of the published output, and did not connect the wallet to the network or send funds.
| Check | Observed result | What it tells you |
|---|---|---|
| Restore with the same recovery phrase | First five receive addresses, first five change addresses, and the master signing key matched | This backup recreated the same key sequence in this software |
| Check the restored wallet's permissions | Signing material was present; it was not watching-only | Monitoring the same balance is not the only recovery check |
| Restore with an added passphrase | The first receive address changed | The phrase alone cannot recover a wallet that also depends on a passphrase |
The test record identifies the exact source revision and checks. The downloadable reproduction script runs against that revision and creates no wallet files. This was a recovery-logic test, not a test of graphical setup screens, physical backups, mobile applications, transaction signing, or payment delivery. No recovery words or receive addresses from this test are provided for readers to reuse.
For your own rehearsal, use a separate empty practice wallet and compare the same address index on the same network. Keep the original wallet until the restore succeeds. If the addresses differ, stop and check the backup format, word order, derivation settings, and passphrase before funding anything. The wallet security guide explains how to keep the real backup private.
Only increase the balance after you can:
- identify the correct network and asset;
- receive and send a test payment;
- explain where the recovery material is stored;
- state what happens if the device or wallet provider disappears.
The first transaction teaches the interface. The recovery plan determines whether the wallet remains usable when the interface is gone.