Skip to content

Crypto wallet

A crypto wallet manages blockchain addresses, signing keys, and access to on-chain assets; it does not store coins locally. Learn how addresses, private keys, recovery phrases, custody models, and transaction signing fit together, and how to use a wallet safely.

Updated

For educational purposes only; not investment advice. Investing may result in loss.

Direct answer

A crypto wallet is software, hardware, or a service that manages addresses and the keys or authorization methods used to control on-chain assets. The blockchain records balances, unspent outputs, and contract state; the wallet stores or accesses the credentials needed to authorize a valid state change. A wallet therefore does not store coins in a local container.

The word “wallet” is useful shorthand but can be misleading. Losing an app installation does not erase an on-chain balance, while losing the only signing credential can make self-custodied assets inaccessible. Custody also matters: a centralized exchange may hold the keys for you, whereas a self-custody wallet leaves signing authority with you.

A wallet can help you:

  • create or import addresses and display balances;

  • hold, encrypt, or delegate signing keys;

  • construct, simulate, sign, and broadcast transactions or messages;

  • connect to on-chain applications while showing the requested permissions.

What it really manages is authorization to change state on a particular network. A token balance is meaningful only on its own chain and under that token contract; an address alone is not proof that a payment arrived or that an application is safe.

How it works

Wallet security is a chain of dependencies: entropy creates a secret, a derivation scheme can create many keys, an address identifies a destination, and a signature authorizes an exact transaction or message. Different networks use different address formats, transaction rules, and contract interfaces, so the network shown in the wallet must match the recipient and asset.

The usual failure modes are:

  • sending a private key or recovery phrase instead of a public address;

  • signing a message whose domain, recipient, allowance, or calldata was not reviewed;

  • approving a malicious or unnecessarily broad token allowance;

  • trusting a wallet banner, balance, or “successful” toast without checking the chain explorer and final state.

The wallet is the security boundary because whoever can satisfy its signing policy may be able to move or encumber the assets.

Example

Suppose Alice is sending 100 USDC to Bob. Before signing, she verifies the network, the recipient address through a second channel, the token contract, the amount, and the fee. She sends a small test amount first, checks the transaction hash on an independent explorer, and confirms that Bob received the token on the intended network. A wallet interface can prepare and sign this sequence, but the sender remains responsible for the destination and authorization.

Risks

Wallet risk is broader than price risk. Consider malware, phishing, malicious browser extensions, supply-chain compromise, weak backups, device loss, wrong-network transfers, nonce or fee errors, token-approval abuse, smart-contract bugs, exchange withdrawal freezes, and the loss of a recovery path. Hardware isolation can reduce exposure of a key, but it cannot validate a malicious recipient or contract for you.

If a secret may be exposed, stop using it for new signatures. From a clean device, create a new wallet with independently verified software or hardware, verify the backup, move remaining assets, and revoke unnecessary token approvals where the chain supports revocation. Never type a recovery phrase into a website or give it to support. For a suspected bad transaction, preserve the hash, network, block, contract, and signed data; a pending transaction can sometimes be replaced according to that network’s rules, but an included transaction is not undone by uninstalling the wallet.

Keep separate records for custody, protocol, and investment decisions. An audited contract may still have governance, oracle, front-end, economic, or key-management risk. Review the exact chain, contract address, permissions, upgrade administrators, approval limits, recovery procedure, and exit conditions. When a mechanism cannot be independently verified, reduce both the amount and the authority granted instead of relying on a reassuring interface or forecast.

Common misconceptions

Can I share my wallet address?

Usually yes: an address is public information used to identify a destination. Share only the address, confirm the network and token contract, and remember that public addresses can reveal transaction history.

Can I give a private key or recovery phrase to support?

No. A private key or recovery phrase is a signing secret. Legitimate support cannot need it, and anyone who asks may be attempting to take control of the wallet.

If I uninstall the wallet, do the coins disappear?

No: the ledger remains on the network. Access can be restored only if you retain the correct recovery material and use the same derivation and network settings; a password for one app is not a universal backup.

Is project documentation enough to evaluate a wallet or app?

No. Compare documentation with the wallet’s published code or vendor, the exact chain and contract addresses, permissions and upgrade paths, signing prompts, independent transaction data, and the recovery process. Documentation describes intent; the ledger and executed code show what happened.

Does an audit make a wallet or contract safe?

No. An audit is scoped evidence about reviewed code at a point in time. It does not remove front-end, oracle, governance, upgrade, private-key, operational, or economic risk. Keep approvals narrow and review every signature.

How do I reduce first-use risk?

Use the official domain or app, verify the network and contract address independently, test with a small amount, simulate or inspect the transaction when possible, limit approvals, and keep long-term holdings in a separate wallet with a tested recovery plan.

Sources

Navigation

Search the wiki...