Confirm the domain before visiting
Confirm the domain before visiting is easier to manage when the interface label is separated from the actual on-chain object. In the context of DApp Connections, review the network, address, contract, request type and expected result rather than relying on a token name, icon or a single status line. Similar-looking addresses and asset symbols can exist on different networks while their states remain independent.
A practical way to work with Confirm the domain before visiting is to break the action into source, destination, permissions or amount, network state and final outcome. When domain is involved, keep information that can be checked independently, such as a transaction hash, contract address, block status or the selected network. This makes it easier to distinguish a delayed interface from the real on-chain result.
Security remains part of Confirm the domain before visiting. A legitimate wallet flow does not require you to send a seed phrase, private key or verification code to another person or type those credentials into an unfamiliar website. Treat wallet connection, message signing, transaction signing and token approvals as separate requests, and stop when the domain, contract, allowance or result does not match what you intended.
- Confirm the network, address or contract involved in Confirm the domain before visiting
- Keep verifiable public information when domain is involved
- Never send a seed phrase, private key or verification code to anyone
Start a wallet connection
Start a wallet connection is easier to manage when the interface label is separated from the actual on-chain object. In the context of DApp Connections, review the network, address, contract, request type and expected result rather than relying on a token name, icon or a single status line. Similar-looking addresses and asset symbols can exist on different networks while their states remain independent.
A practical way to work with Start a wallet connection is to break the action into source, destination, permissions or amount, network state and final outcome. When connect is involved, keep information that can be checked independently, such as a transaction hash, contract address, block status or the selected network. This makes it easier to distinguish a delayed interface from the real on-chain result.
Security remains part of Start a wallet connection. A legitimate wallet flow does not require you to send a seed phrase, private key or verification code to another person or type those credentials into an unfamiliar website. Treat wallet connection, message signing, transaction signing and token approvals as separate requests, and stop when the domain, contract, allowance or result does not match what you intended.
- Confirm the network, address or contract involved in Start a wallet connection
- Keep verifiable public information when connect is involved
- Never send a seed phrase, private key or verification code to anyone
Review account and network access
Review account and network access is easier to manage when the interface label is separated from the actual on-chain object. In the context of DApp Connections, review the network, address, contract, request type and expected result rather than relying on a token name, icon or a single status line. Similar-looking addresses and asset symbols can exist on different networks while their states remain independent.
A practical way to work with Review account and network access is to break the action into source, destination, permissions or amount, network state and final outcome. When account is involved, keep information that can be checked independently, such as a transaction hash, contract address, block status or the selected network. This makes it easier to distinguish a delayed interface from the real on-chain result.
Security remains part of Review account and network access. A legitimate wallet flow does not require you to send a seed phrase, private key or verification code to another person or type those credentials into an unfamiliar website. Treat wallet connection, message signing, transaction signing and token approvals as separate requests, and stop when the domain, contract, allowance or result does not match what you intended.
- Confirm the network, address or contract involved in Review account and network access
- Keep verifiable public information when account is involved
- Never send a seed phrase, private key or verification code to anyone
Evaluate each signature request
Evaluate each signature request is easier to manage when the interface label is separated from the actual on-chain object. In the context of DApp Connections, review the network, address, contract, request type and expected result rather than relying on a token name, icon or a single status line. Similar-looking addresses and asset symbols can exist on different networks while their states remain independent.
A practical way to work with Evaluate each signature request is to break the action into source, destination, permissions or amount, network state and final outcome. When network is involved, keep information that can be checked independently, such as a transaction hash, contract address, block status or the selected network. This makes it easier to distinguish a delayed interface from the real on-chain result.
Security remains part of Evaluate each signature request. A legitimate wallet flow does not require you to send a seed phrase, private key or verification code to another person or type those credentials into an unfamiliar website. Treat wallet connection, message signing, transaction signing and token approvals as separate requests, and stop when the domain, contract, allowance or result does not match what you intended.
- Confirm the network, address or contract involved in Evaluate each signature request
- Keep verifiable public information when network is involved
- Never send a seed phrase, private key or verification code to anyone
Disconnect sessions you no longer need
Disconnect sessions you no longer need is easier to manage when the interface label is separated from the actual on-chain object. In the context of DApp Connections, review the network, address, contract, request type and expected result rather than relying on a token name, icon or a single status line. Similar-looking addresses and asset symbols can exist on different networks while their states remain independent.
A practical way to work with Disconnect sessions you no longer need is to break the action into source, destination, permissions or amount, network state and final outcome. When disconnect is involved, keep information that can be checked independently, such as a transaction hash, contract address, block status or the selected network. This makes it easier to distinguish a delayed interface from the real on-chain result.
Security remains part of Disconnect sessions you no longer need. A legitimate wallet flow does not require you to send a seed phrase, private key or verification code to another person or type those credentials into an unfamiliar website. Treat wallet connection, message signing, transaction signing and token approvals as separate requests, and stop when the domain, contract, allowance or result does not match what you intended.
- Confirm the network, address or contract involved in Disconnect sessions you no longer need
- Keep verifiable public information when disconnect is involved
- Never send a seed phrase, private key or verification code to anyone