On this page
prepare before creation
Prepare a private, offline environment before creating a wallet and avoid shared computers, remote-control sessions or visible cameras. This matters in practice because blockchain outcomes are determined by the selected network and the request that is signed, not merely by what a button is called. For prepare before creation, prioritize information you can verify: the active network, public address, contract target and transaction status. Turning those details into a repeatable checklist is more reliable than reacting to vague interface messages.
A seed phrase can commonly derive account keys, so a good backup is confidential, complete and recoverable rather than copied into many online services. It also helps to separate three layers: what the wallet displays, what the network has actually recorded, and what a third-party service claims. When something looks wrong, identify the layer first and then verify with a transaction hash, block explorer or explicit network parameters. No legitimate prepare before creation workflow requires a seed phrase, private key or verification code to be sent to another person.
seed phrase and private-key custody
A seed phrase can commonly derive account keys, so a good backup is confidential, complete and recoverable rather than copied into many online services. It also helps to separate three layers: what the wallet displays, what the network has actually recorded, and what a third-party service claims. When something looks wrong, identify the layer first and then verify with a transaction hash, block explorer or explicit network parameters. No legitimate seed phrase and private-key custody workflow requires a seed phrase, private key or verification code to be sent to another person.
Recovery checks belong in a trusted wallet environment. No legitimate support workflow requires sending the phrase away for “verification.” If the action includes a signature, approval or contract call, inspect the permission scope and possible asset impact separately. Friendly labels are not a substitute for the underlying request. Check the target, asset, amount or allowance, network and final confirmation details before proceeding. This sequence reduces mistakes caused by urgency, phishing or the wrong network.
- Verify the network, address and public on-chain information relevant to seed phrase and private-key custody.
- Never send a seed phrase, private key or verification code to anyone.
- For DApps or contracts, review each signature and approval scope separately.
offline backup and recovery checks
Recovery checks belong in a trusted wallet environment. No legitimate support workflow requires sending the phrase away for “verification.” If the action includes a signature, approval or contract call, inspect the permission scope and possible asset impact separately. Friendly labels are not a substitute for the underlying request. Check the target, asset, amount or allowance, network and final confirmation details before proceeding. This sequence reduces mistakes caused by urgency, phishing or the wrong network.
Prepare a private, offline environment before creating a wallet and avoid shared computers, remote-control sessions or visible cameras. This matters in practice because blockchain outcomes are determined by the selected network and the request that is signed, not merely by what a button is called. For offline backup and recovery checks, prioritize information you can verify: the active network, public address, contract target and transaction status. Turning those details into a repeatable checklist is more reliable than reacting to vague interface messages.
verify before importing an existing wallet
Prepare a private, offline environment before creating a wallet and avoid shared computers, remote-control sessions or visible cameras. This matters in practice because blockchain outcomes are determined by the selected network and the request that is signed, not merely by what a button is called. For verify before importing an existing wallet, prioritize information you can verify: the active network, public address, contract target and transaction status. Turning those details into a repeatable checklist is more reliable than reacting to vague interface messages.
A seed phrase can commonly derive account keys, so a good backup is confidential, complete and recoverable rather than copied into many online services. It also helps to separate three layers: what the wallet displays, what the network has actually recorded, and what a third-party service claims. When something looks wrong, identify the layer first and then verify with a transaction hash, block explorer or explicit network parameters. No legitimate verify before importing an existing wallet workflow requires a seed phrase, private key or verification code to be sent to another person.
- Verify the network, address and public on-chain information relevant to verify before importing an existing wallet.
- Never send a seed phrase, private key or verification code to anyone.
- For DApps or contracts, review each signature and approval scope separately.