Use a trusted device and have the address, network and transaction details you need to verify. No page should ask you to enter a seed phrase, private key or recovery phrase.
Confirm the source
“Confirm the source” deserves its own checkpoint when working with DApp Connections. It can affect network selection, account control, transaction confirmation or permission scope, so a single interface label should not be treated as the full story.
In a DApp Connections workflow, build a short verification chain: confirm the source, confirm the target, review the permission or amount, then verify the on-chain result. This helps prevent different networks, contracts or sessions from being mixed together.
The goal is not to click through quickly but to make each step reviewable. Prepare only the non-sensitive information you need, verify details during the action, and confirm the result afterward using wallet history or a block explorer.
After working through “Confirm the source,” keep only the non-sensitive references you may need later, such as a transaction hash, network name or public address. Do not store or forward a seed phrase, private key, recovery phrase or verification code.
- Confirm the network and account related to “Confirm the source”
- Verify the source or DApp domain
- Read the actual transaction, signature or approval request
- Check the resulting transaction state and any permissions left behind
Start a connection
“Start a connection” deserves its own checkpoint when working with DApp Connections. It can affect network selection, account control, transaction confirmation or permission scope, so a single interface label should not be treated as the full story.
In a DApp Connections workflow, build a short verification chain: confirm the source, confirm the target, review the permission or amount, then verify the on-chain result. This helps prevent different networks, contracts or sessions from being mixed together.
If a network, address, amount, permission or signature differs from what you expected, stop the flow. Do not let urgency, countdowns or someone claiming to be support push you past a check you would normally make.
After working through “Start a connection,” keep only the non-sensitive references you may need later, such as a transaction hash, network name or public address. Do not store or forward a seed phrase, private key, recovery phrase or verification code.
- Confirm the network and account related to “Start a connection”
- Verify the source or DApp domain
- Read the actual transaction, signature or approval request
- Check the resulting transaction state and any permissions left behind
Review account requests
“Review account requests” deserves its own checkpoint when working with DApp Connections. It can affect network selection, account control, transaction confirmation or permission scope, so a single interface label should not be treated as the full story.
In a DApp Connections workflow, build a short verification chain: confirm the source, confirm the target, review the permission or amount, then verify the on-chain result. This helps prevent different networks, contracts or sessions from being mixed together.
For an important transfer or an unfamiliar route, a small test can help reveal obvious problems with the address, network or recipient support before you continue. It does not remove all risk, but it adds a useful checkpoint.
After working through “Review account requests,” keep only the non-sensitive references you may need later, such as a transaction hash, network name or public address. Do not store or forward a seed phrase, private key, recovery phrase or verification code.
- Confirm the network and account related to “Review account requests”
- Verify the source or DApp domain
- Read the actual transaction, signature or approval request
- Check the resulting transaction state and any permissions left behind
Disconnect unused sessions
“Disconnect unused sessions” deserves its own checkpoint when working with DApp Connections. It can affect network selection, account control, transaction confirmation or permission scope, so a single interface label should not be treated as the full story.
In a DApp Connections workflow, build a short verification chain: confirm the source, confirm the target, review the permission or amount, then verify the on-chain result. This helps prevent different networks, contracts or sessions from being mixed together.
The goal is not to click through quickly but to make each step reviewable. Prepare only the non-sensitive information you need, verify details during the action, and confirm the result afterward using wallet history or a block explorer.
After working through “Disconnect unused sessions,” keep only the non-sensitive references you may need later, such as a transaction hash, network name or public address. Do not store or forward a seed phrase, private key, recovery phrase or verification code.
- Confirm the network and account related to “Disconnect unused sessions”
- Verify the source or DApp domain
- Read the actual transaction, signature or approval request
- Check the resulting transaction state and any permissions left behind
Important reminder
Seed phrases and private keys should remain under the user’s control and should never be sent to anyone. On-chain transactions generally cannot be unilaterally reversed by a wallet, and third-party DApps, smart contracts, bridges or staking services can introduce technical, market and operational risks.