Verify the domain
Verify the domain is a distinct part of understanding DApp Connections. Connecting a DApp often allows it to see a public address or request actions; it does not automatically move assets. Asset impact usually comes later through a signed transaction or token approval. A DApp may request a public address, a message signature, a transaction signature or a token approval. These requests have very different consequences. Treat every prompt as a separate decision: verify the domain and contract, understand the request, then approve or reject it.
In practice, do not rely on interface color, icons or labels alone. Cross-check verifiable details such as the active network, public address, transaction hash, contract address and approval target. Before any action that changes onchain state, read the request and confirm the amount, network and destination.
If something looks wrong, stop signing or resubmitting transactions until the situation is understood. Keep non-sensitive details such as the transaction hash, network name and public address for troubleshooting, but never share a seed phrase, private key or verification code. Onchain transactions are generally not reversible by a wallet provider, so preventive checks matter more than recovery promises.
Connect accounts
Connect accounts is a distinct part of understanding DApp Connections. Connecting a DApp often allows it to see a public address or request actions; it does not automatically move assets. Asset impact usually comes later through a signed transaction or token approval. A DApp may request a public address, a message signature, a transaction signature or a token approval. These requests have very different consequences. Treat every prompt as a separate decision: verify the domain and contract, understand the request, then approve or reject it.
In practice, do not rely on interface color, icons or labels alone. Cross-check verifiable details such as the active network, public address, transaction hash, contract address and approval target. Before any action that changes onchain state, read the request and confirm the amount, network and destination.
If something looks wrong, stop signing or resubmitting transactions until the situation is understood. Keep non-sensitive details such as the transaction hash, network name and public address for troubleshooting, but never share a seed phrase, private key or verification code. Onchain transactions are generally not reversible by a wallet provider, so preventive checks matter more than recovery promises.
- Confirm the active network before sending or approving.
- Compare the full destination or contract details.
- Keep recovery material offline and private.
Scope of requests
Scope of requests is a distinct part of understanding DApp Connections. Connecting a DApp often allows it to see a public address or request actions; it does not automatically move assets. Asset impact usually comes later through a signed transaction or token approval. A DApp may request a public address, a message signature, a transaction signature or a token approval. These requests have very different consequences. Treat every prompt as a separate decision: verify the domain and contract, understand the request, then approve or reject it.
In practice, do not rely on interface color, icons or labels alone. Cross-check verifiable details such as the active network, public address, transaction hash, contract address and approval target. Before any action that changes onchain state, read the request and confirm the amount, network and destination.
If something looks wrong, stop signing or resubmitting transactions until the situation is understood. Keep non-sensitive details such as the transaction hash, network name and public address for troubleshooting, but never share a seed phrase, private key or verification code. Onchain transactions are generally not reversible by a wallet provider, so preventive checks matter more than recovery promises.
End the session
End the session is a distinct part of understanding DApp Connections. Connecting a DApp often allows it to see a public address or request actions; it does not automatically move assets. Asset impact usually comes later through a signed transaction or token approval. A DApp may request a public address, a message signature, a transaction signature or a token approval. These requests have very different consequences. Treat every prompt as a separate decision: verify the domain and contract, understand the request, then approve or reject it.
In practice, do not rely on interface color, icons or labels alone. Cross-check verifiable details such as the active network, public address, transaction hash, contract address and approval target. Before any action that changes onchain state, read the request and confirm the amount, network and destination.
If something looks wrong, stop signing or resubmitting transactions until the situation is understood. Keep non-sensitive details such as the transaction hash, network name and public address for troubleshooting, but never share a seed phrase, private key or verification code. Onchain transactions are generally not reversible by a wallet provider, so preventive checks matter more than recovery promises.
Security and risk reminder
Blockchain transactions are generally irreversible by a wallet provider. Third-party DApps and smart contracts can contain technical or business risks. Review every signature and approval independently, and consider revoking permissions you no longer use.