On this page
Prepare before you beginFollow the action in orderWhat to verify at each stepCommon mistakes and recovery thinkingA practical security checklistReview after completionPrepare before you begin
Before starting DApp Connections, gather the information related to domain verification, account selection, and connection requests. Before connecting to a DApp, verify the domain and purpose. After connecting, continue to review every signature, approval and transaction separately. Do not search for recovery material on an unfamiliar site or skip a network, address or permission check simply because the workflow looks familiar. Good preparation makes later anomalies easier to notice.
Key point: network matching
During the action, treat network matching and disconnecting as separate checkpoints rather than one combined confirmation. When a state related to session permissions appears, make sure it belongs to the intended network and object. If the request differs from what you expected, stop and re-check instead of submitting the same request several times.
After completion, keep enough public information to review the result. Revisit domain verification, confirm that account selection and connection requests match the intended outcome, and make sure network matching has not left an unnecessary permission behind. On-chain transactions generally cannot be reversed by a wallet alone, so post-action review is part of the workflow, not an optional extra.
Follow the action in order
Before starting DApp Connections, gather the information related to account selection, connection requests, and network matching. Before connecting to a DApp, verify the domain and purpose. After connecting, continue to review every signature, approval and transaction separately. Do not search for recovery material on an unfamiliar site or skip a network, address or permission check simply because the workflow looks familiar. Good preparation makes later anomalies easier to notice.
Key point: disconnecting
During the action, treat disconnecting and session permissions as separate checkpoints rather than one combined confirmation. When a state related to domain verification appears, make sure it belongs to the intended network and object. If the request differs from what you expected, stop and re-check instead of submitting the same request several times.
After completion, keep enough public information to review the result. Revisit account selection, confirm that connection requests and network matching match the intended outcome, and make sure disconnecting has not left an unnecessary permission behind. On-chain transactions generally cannot be reversed by a wallet alone, so post-action review is part of the workflow, not an optional extra.
What to verify at each step
Before starting DApp Connections, gather the information related to connection requests, network matching, and disconnecting. Before connecting to a DApp, verify the domain and purpose. After connecting, continue to review every signature, approval and transaction separately. Do not search for recovery material on an unfamiliar site or skip a network, address or permission check simply because the workflow looks familiar. Good preparation makes later anomalies easier to notice.
Key point: session permissions
During the action, treat session permissions and domain verification as separate checkpoints rather than one combined confirmation. When a state related to account selection appears, make sure it belongs to the intended network and object. If the request differs from what you expected, stop and re-check instead of submitting the same request several times.
After completion, keep enough public information to review the result. Revisit connection requests, confirm that network matching and disconnecting match the intended outcome, and make sure session permissions has not left an unnecessary permission behind. On-chain transactions generally cannot be reversed by a wallet alone, so post-action review is part of the workflow, not an optional extra.
Common mistakes and recovery thinking
Before starting DApp Connections, gather the information related to network matching, disconnecting, and session permissions. Before connecting to a DApp, verify the domain and purpose. After connecting, continue to review every signature, approval and transaction separately. Do not search for recovery material on an unfamiliar site or skip a network, address or permission check simply because the workflow looks familiar. Good preparation makes later anomalies easier to notice.
Key point: domain verification
During the action, treat domain verification and account selection as separate checkpoints rather than one combined confirmation. When a state related to connection requests appears, make sure it belongs to the intended network and object. If the request differs from what you expected, stop and re-check instead of submitting the same request several times.
After completion, keep enough public information to review the result. Revisit network matching, confirm that disconnecting and session permissions match the intended outcome, and make sure domain verification has not left an unnecessary permission behind. On-chain transactions generally cannot be reversed by a wallet alone, so post-action review is part of the workflow, not an optional extra.
A practical security checklist
Before starting DApp Connections, gather the information related to disconnecting, session permissions, and domain verification. Before connecting to a DApp, verify the domain and purpose. After connecting, continue to review every signature, approval and transaction separately. Do not search for recovery material on an unfamiliar site or skip a network, address or permission check simply because the workflow looks familiar. Good preparation makes later anomalies easier to notice.
Key point: account selection
During the action, treat account selection and connection requests as separate checkpoints rather than one combined confirmation. When a state related to network matching appears, make sure it belongs to the intended network and object. If the request differs from what you expected, stop and re-check instead of submitting the same request several times.
After completion, keep enough public information to review the result. Revisit disconnecting, confirm that session permissions and domain verification match the intended outcome, and make sure account selection has not left an unnecessary permission behind. On-chain transactions generally cannot be reversed by a wallet alone, so post-action review is part of the workflow, not an optional extra.
- Check domain verification in the correct network and request context before confirming.
- Check account selection in the correct network and request context before confirming.
- Check connection requests in the correct network and request context before confirming.
- Check network matching in the correct network and request context before confirming.
- Check disconnecting in the correct network and request context before confirming.
Review after completion
Before starting DApp Connections, gather the information related to session permissions, domain verification, and account selection. Before connecting to a DApp, verify the domain and purpose. After connecting, continue to review every signature, approval and transaction separately. Do not search for recovery material on an unfamiliar site or skip a network, address or permission check simply because the workflow looks familiar. Good preparation makes later anomalies easier to notice.
Key point: connection requests
During the action, treat connection requests and network matching as separate checkpoints rather than one combined confirmation. When a state related to disconnecting appears, make sure it belongs to the intended network and object. If the request differs from what you expected, stop and re-check instead of submitting the same request several times.
After completion, keep enough public information to review the result. Revisit session permissions, confirm that domain verification and account selection match the intended outcome, and make sure connection requests has not left an unnecessary permission behind. On-chain transactions generally cannot be reversed by a wallet alone, so post-action review is part of the workflow, not an optional extra.