On this page
verify source and domain first
Use a trusted source to verify the domain before connecting, especially when a site differs by one character or appears through an advertisement. 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 source and domain first, 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 connection may only reveal a public address at first, but later steps can request signatures, approvals or transactions and must be judged individually. 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 source and domain first workflow requires a seed phrase, private key or verification code to be sent to another person.
start the connection and choose an account
A connection may only reveal a public address at first, but later steps can request signatures, approvals or transactions and must be judged individually. 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 start the connection and choose an account workflow requires a seed phrase, private key or verification code to be sent to another person.
Closing a tab is not permission management; disconnect the session and review any approvals that were granted. 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 start the connection and choose an account.
- Never send a seed phrase, private key or verification code to anyone.
- For DApps or contracts, review each signature and approval scope separately.
review every request individually
Closing a tab is not permission management; disconnect the session and review any approvals that were granted. 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.
Use a trusted source to verify the domain before connecting, especially when a site differs by one character or appears through an advertisement. 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 review every request individually, 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.
disconnect when finished
Use a trusted source to verify the domain before connecting, especially when a site differs by one character or appears through an advertisement. 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 disconnect when finished, 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 connection may only reveal a public address at first, but later steps can request signatures, approvals or transactions and must be judged individually. 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 disconnect when finished 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 disconnect when finished.
- Never send a seed phrase, private key or verification code to anyone.
- For DApps or contracts, review each signature and approval scope separately.