On this page
system and browser updates
Keep the operating system, browser and wallet software current, and obtain updates only from trusted sources. 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 system and browser updates, 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.
Shared computers can retain input or sessions, while public networks add uncertainty; both are poor environments for high-sensitivity actions. 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 system and browser updates workflow requires a seed phrase, private key or verification code to be sent to another person.
public Wi-Fi and shared computers
Shared computers can retain input or sessions, while public networks add uncertainty; both are poor environments for high-sensitivity actions. 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 public Wi-Fi and shared computers workflow requires a seed phrase, private key or verification code to be sent to another person.
After copying a recipient address, compare its beginning and ending characters again to catch clipboard substitution malware. 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 public wi-fi and shared computers.
- Never send a seed phrase, private key or verification code to anyone.
- For DApps or contracts, review each signature and approval scope separately.
clipboard and input-method risks
After copying a recipient address, compare its beginning and ending characters again to catch clipboard substitution malware. 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.
Keep the operating system, browser and wallet software current, and obtain updates only from trusted sources. 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 clipboard and input-method risks, 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.
what to do if a device is lost
Keep the operating system, browser and wallet software current, and obtain updates only from trusted sources. 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 what to do if a device is lost, 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.
Shared computers can retain input or sessions, while public networks add uncertainty; both are poor environments for high-sensitivity actions. 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 what to do if a device is lost 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 what to do if a device is lost.
- Never send a seed phrase, private key or verification code to anyone.
- For DApps or contracts, review each signature and approval scope separately.