Phishing
Look-alike domains and fake support can redirect users to malicious requests.
Transaction Checks
Learn address, network, amount, fees and transaction finality with practical security checks and on-chain verification guidance.
Core principles
An address can look valid on several compatible networks while balances remain separate. Confirm that the sending network is supported by the receiving side.
- Keep seed phrases and private keys under your control
- Official support should not request recovery material
- Verify address, network and amount before sending
- Review DApp spender and permission scope
- Use caution on public devices and networks
Risk scenarios
Malicious approvals
A persistent token permission can remain active after a DApp session ends.
Device exposure
Screenshots, remote control and public devices can reveal sensitive material.
Transaction mistakes
Wrong network, address or amount can lead to irreversible outcomes.
How to respond
Gas is paid to the network. After submission, use the transaction hash in the correct explorer to check status; congestion can delay confirmation.
Once confirmed, blockchain transactions usually cannot be reversed by the wallet alone. If a destination, approval or contract is unfamiliar, stop and verify before signing.
Final check
For address, network, amount, fees and transaction finality, use a deliberate sequence: verify the entry point, confirm the network, check the address or contract, review the exact request, then submit. For asset movement, also verify the amount, fee and transaction hash. For DApps, distinguish connection, message signatures, transaction signatures and token approvals because they create different permissions.