Crypto Wallets Explained: Private Keys, Seed Phrases and Custody

A wallet is fundamentally a signing authority, not a balance display

A crypto wallet manages private keys used to sign transactions and public keys or addresses used to identify accounts or destinations. Assets remain recorded on the network ledger rather than being physically placed inside an app or device. Deleting an app does not destroy the asset if a correct key or seed can restore access. Conversely, a visible balance cannot be moved if the required signing material is lost.

In self-custody, the user directly controls keys. In third-party custody, an exchange or custodian controls keys while the user requests withdrawals under a contract. A slogan cannot decide which is safer for a particular person. Self-custody reduces provider dependence but concentrates loss, succession and operating risk on the user. Third-party custody can provide account recovery but adds withdrawal, breach, insolvency and terms risk.

Cold storage and self-custody are not synonyms; a third-party custodian can also use cold storage.

Separate private keys, public keys, addresses and seeds

A private key is a secret value used to make a signature. A public key is used to verify that signature, and an address is usually a destination representation derived from a public key or script. Systems are designed so that deriving a public key from a private key is practical while reversing the process is not. Anyone who obtains the signing key may be able to move the asset. A support representative, accountant or executor does not need the live secret merely to inspect records.

A seed phrase or mnemonic is commonly an entry point that deterministically recreates many keys. The same seed can show unexpected addresses when the derivation path, optional passphrase, network or wallet implementation differs. An extra passphrase can increase separation but makes recovery impossible if forgotten. Record the recovery standard and configuration—not just the statement that a seed exists.

Plan for disclosure, destruction and undiscoverability at the same time

Hiding a key is not enough. Storage must address confidentiality, integrity and availability: unauthorized people cannot read it, substitutions can be detected, and an authorized person can retrieve it when needed. One paper copy in one building creates a single point of failure for fire, flood, theft and accidental disposal. Photos, cloud notes and email drafts are easy to duplicate but expand the online attack surface. A split backup requires a clear understanding of how many pieces are needed and what each piece reveals.

Phishing manufactures urgency: “enter your seed,” “synchronize your wallet,” or “claim this airdrop.” Common routes include lookalike domains, search ads, counterfeit apps, tampered hardware and remote-access requests. Open known services from saved official links, read what is being signed, confirm the destination on an independent device display, and remove unnecessary token allowances. A message signature can also authorize harmful actions even when no obvious transfer screen appears.

Separate medium, location and discovery instructions

A backup inventory can record creation date, supported network, address prefix and suffix, backup method, coded location, whether a passphrase exists, last recovery test and retirement date. Keep the secret separate from the inventory that explains where it is. A metal backup can improve resistance to fire and water without preventing theft or photography. An encrypted drive adds dependence on a password and compatible decryption software. List at least two failure modes for each medium.

For succession and emergencies, do not place the asset amount, seed and complete instructions in one document. An authorized person should be able to discover that something exists, whom to contact, what event activates the process and which separate materials must be combined. Wills, beneficiaries, tax and multisignature enforceability vary by jurisdiction. Technical ability to recover an asset is not automatically legal authority to transfer it.

• Medium: Test paper, metal and encrypted storage against fire, water, theft and decay.
• Location: Avoid one building or disaster zone and keep an access log.
• Discovery: Explain existence and process without exposing the secret.
• Change control: Retire old instructions after wallet, passphrase or signer changes.

Restore on a clean second environment before funding the wallet

A recovery drill does not require destroying a production wallet. Create a new empty test wallet, make its backup, restore it on another clean device or isolated environment, and confirm that the same receiving address is derived. Remove the temporary environment safely afterward and ensure that screen recordings, clipboard history or cloud synchronization did not retain the secret. With hardware wallets, use the vendor’s official process, authentic firmware and the device display for destination confirmation.

After restoration, complete a tiny receive-send cycle and reconcile the balance and history. Follow the address, confirmation and explorer workflow. A periodic check should cover media readability, signer contacts, device compatibility, firmware and the location of recovery instructions. Never use a website that asks you to type a seed merely to “check” it.

1. 01Create an empty test wallet

   Separate it from production assets and record the official source and device state.

2. 02Make the backup

   Avoid cameras, cloud sync, clipboard history and observers.

3. 03Restore elsewhere

   Confirm network, derived address and expected empty balance.

4. 04Send a tiny amount

   Record the receive, send, transaction hash and fee.

5. 05Log the result

   Record success or failure and the next review date—not the secret.

Allocate control by purpose instead of putting everything in one method

Regular spending, long-term holdings, DeFi interaction, business funds and shared custody require different balances of access and control. Putting everything in a frequently connected hot wallet concentrates the signing attack surface. Connecting a long-term wallet to unknown applications cancels much of the intended isolation. Separate wallets by purpose and consider transfer limits, allowlists, multiple signatures, delays and watch-only monitoring.

When using a third party, apply the exchange and custody due-diligence checklist to the legal entity, registration, client assets, key management, insurance scope, outsourcing, withdrawal terms and succession process. When moving to self-custody, do not transfer everything at once: run a small transaction on the correct network and verify it in both the explorer and recipient wallet.

The Financial Templates Hub can hold a wallet identifier, purpose, non-secret location code, recovery-test date, signers and next review date. Never enter a private key, seed phrase or sensitive personal data. The template records operations around the secret, not the secret itself.