Confirm the objective
Know whether you are creating, importing, receiving, sending or connecting to a DApp before you start confirming actions.
imtoken Knowledge Center
Connect to a DApp
Before connecting, verify the domain and application source, then review which account and network the DApp requests.
Before you start
- Use a trusted device and network environment.
- Prepare an offline way to record necessary backup information.
- Never send a seed phrase, private key or verification code to anyone.
Steps
Check network and address
Verify the active network, destination and asset chain; use a block explorer when you need independent confirmation.
Review fees and permissions
For transfers, inspect gas and amount; for Web3, inspect signature details, contract and approval scope.
Verify after submission
Keep the transaction hash or operation record and verify status on the correct network rather than relying only on a pop-up message.
Common mistakes and checks
Connection is not authorization
A DApp connection creates a communication channel between a site and a wallet. It does not automatically authorize assets or make later signature requests safe. In the context of Connect to a DApp, the practical goal is to understand what the wallet is showing, what the network is recording, and which details must be verified before you approve an action.
A useful check is to separate interface information from on-chain facts. Review the active network, address, transaction hash, contract or permission scope as relevant, and avoid assuming that a familiar symbol or screen guarantees the intended result.
Read every signature request
Message signatures, transaction signatures and token approvals have different consequences. Before confirming, review the requester, network, amount, contract and permission scope. In the context of Connect to a DApp, the practical goal is to understand what the wallet is showing, what the network is recording, and which details must be verified before you approve an action.
A useful check is to separate interface information from on-chain facts. Review the active network, address, transaction hash, contract or permission scope as relevant, and avoid assuming that a familiar symbol or screen guarantees the intended result.
Token approvals and contract permissions
Third-party smart contracts may carry code, permission or governance risk. After use, disconnect sessions you no longer need and review persistent approvals. In the context of Connect to a DApp, the practical goal is to understand what the wallet is showing, what the network is recording, and which details must be verified before you approve an action.
A useful check is to separate interface information from on-chain facts. Review the active network, address, transaction hash, contract or permission scope as relevant, and avoid assuming that a familiar symbol or screen guarantees the intended result.
Clean up permissions after use
A DApp connection creates a communication channel between a site and a wallet. It does not automatically authorize assets or make later signature requests safe. In the context of Connect to a DApp, the practical goal is to understand what the wallet is showing, what the network is recording, and which details must be verified before you approve an action.
A useful check is to separate interface information from on-chain facts. Review the active network, address, transaction hash, contract or permission scope as relevant, and avoid assuming that a familiar symbol or screen guarantees the intended result.