DApp Connections｜imtoken

Learn how to review a DApp domain, connection request, account access and disconnect flow.

On this page

Identify the site you are connecting to

To understand DApp Connections, place identify the site you are connecting to inside the full on-chain workflow instead of treating it as an isolated label. The practical point is to verify identify the site you are connecting to in the context of the selected blockchain network. The user should compare the request with the intended address, asset, account or contract before confirming. A wallet can organize information and submit requests, but the selected network and the blockchain determine the final state. On-chain state and a transaction hash provide stronger evidence than a delayed interface alone. Third-party DApps, services and smart contracts can introduce risks that need separate review. If the interface does not match your expectation, verify the network, address, contract and on-chain record before taking another action.

A practical way to approach identify the site you are connecting to is to use a consistent review sequence. First, the practical point is to verify identify the site you are connecting to in the context of the selected blockchain network. Next, the user should compare the request with the intended address, asset, account or contract before confirming. After a transaction, signature or approval is submitted, on-chain state and a transaction hash provide stronger evidence than a delayed interface alone. Finally, third-party dapps, services and smart contracts can introduce risks that need separate review. This sequence gives each confirmation a clear reason and helps reduce wrong-network transfers, address mismatches, unnecessary permissions and repeated actions caused by a delayed interface.

The practical point is to verify identify the site you are connecting to in the context of the selected blockchain network
The user should compare the request with the intended address, asset, account or contract before confirming
On-chain state and a transaction hash provide stronger evidence than a delayed interface alone
Third-party DApps, services and smart contracts can introduce risks that need separate review

Read the connection request

To understand DApp Connections, place read the connection request inside the full on-chain workflow instead of treating it as an isolated label. The practical point is to verify read the connection request in the context of the selected blockchain network. The user should compare the request with the intended address, asset, account or contract before confirming. A wallet can organize information and submit requests, but the selected network and the blockchain determine the final state. On-chain state and a transaction hash provide stronger evidence than a delayed interface alone. Third-party DApps, services and smart contracts can introduce risks that need separate review. If the interface does not match your expectation, verify the network, address, contract and on-chain record before taking another action.

A practical way to approach read the connection request is to use a consistent review sequence. First, the practical point is to verify read the connection request in the context of the selected blockchain network. Next, the user should compare the request with the intended address, asset, account or contract before confirming. After a transaction, signature or approval is submitted, on-chain state and a transaction hash provide stronger evidence than a delayed interface alone. Finally, third-party dapps, services and smart contracts can introduce risks that need separate review. This sequence gives each confirmation a clear reason and helps reduce wrong-network transfers, address mismatches, unnecessary permissions and repeated actions caused by a delayed interface.

The practical point is to verify read the connection request in the context of the selected blockchain network
The user should compare the request with the intended address, asset, account or contract before confirming
On-chain state and a transaction hash provide stronger evidence than a delayed interface alone
Third-party DApps, services and smart contracts can introduce risks that need separate review

Permissions during a session

To understand DApp Connections, place permissions during a session inside the full on-chain workflow instead of treating it as an isolated label. Approvals can give a contract permission to use tokens within a defined scope. The spender or operator address and amount should be checked before signing. A wallet can organize information and submit requests, but the selected network and the blockchain determine the final state. Disconnecting a DApp does not automatically revoke an on-chain approval. Unused permissions can be reviewed and revoked with a new on-chain transaction. If the interface does not match your expectation, verify the network, address, contract and on-chain record before taking another action.

A practical way to approach permissions during a session is to use a consistent review sequence. First, approvals can give a contract permission to use tokens within a defined scope. Next, the spender or operator address and amount should be checked before signing. After a transaction, signature or approval is submitted, disconnecting a dapp does not automatically revoke an on-chain approval. Finally, unused permissions can be reviewed and revoked with a new on-chain transaction. This sequence gives each confirmation a clear reason and helps reduce wrong-network transfers, address mismatches, unnecessary permissions and repeated actions caused by a delayed interface.

Approvals can give a contract permission to use tokens within a defined scope
The spender or operator address and amount should be checked before signing
Disconnecting a DApp does not automatically revoke an on-chain approval
Unused permissions can be reviewed and revoked with a new on-chain transaction

Disconnect and review

To understand DApp Connections, place disconnect and review inside the full on-chain workflow instead of treating it as an isolated label. The practical point is to verify disconnect and review in the context of the selected blockchain network. The user should compare the request with the intended address, asset, account or contract before confirming. A wallet can organize information and submit requests, but the selected network and the blockchain determine the final state. On-chain state and a transaction hash provide stronger evidence than a delayed interface alone. Third-party DApps, services and smart contracts can introduce risks that need separate review. If the interface does not match your expectation, verify the network, address, contract and on-chain record before taking another action.

A practical way to approach disconnect and review is to use a consistent review sequence. First, the practical point is to verify disconnect and review in the context of the selected blockchain network. Next, the user should compare the request with the intended address, asset, account or contract before confirming. After a transaction, signature or approval is submitted, on-chain state and a transaction hash provide stronger evidence than a delayed interface alone. Finally, third-party dapps, services and smart contracts can introduce risks that need separate review. This sequence gives each confirmation a clear reason and helps reduce wrong-network transfers, address mismatches, unnecessary permissions and repeated actions caused by a delayed interface.

The practical point is to verify disconnect and review in the context of the selected blockchain network
The user should compare the request with the intended address, asset, account or contract before confirming
On-chain state and a transaction hash provide stronger evidence than a delayed interface alone
Third-party DApps, services and smart contracts can introduce risks that need separate review

Download imtoken Read FAQ →