Support guidance uses network context, transaction hashes, contracts and device conditions for troubleshooting. Support does not need seed phrases, private keys or verification codes and should not require remote control to “verify” a wallet.
For troubleshooting, network name, public address, transaction hash, error message and steps are usually enough. Do not send seed phrases, private keys, verification codes or screenshots containing them.
Do not rely on a button label or a familiar-looking page as the reason to continue. Compare the request with the on-chain target, network state and expected result, and stop when those pieces do not line up.
If a transaction has been submitted, check its hash on the correct network to determine whether it is pending, successful or failed before diagnosing interface sync or network selection.
A common mistake is to treat a normal-looking interface as proof that the underlying blockchain action is correct. Public addresses, transaction hashes, contract addresses and network parameters provide independent ways to verify what is happening.
For connection or signing problems, verify the DApp domain, selected network, account and request type. Never enter a recovery phrase into a web page to fix a connection issue.
A repeatable order of checks is more reliable than memory. Review source, network, account, target and expected outcome each time so the same safety logic carries across wallets and DApps.
If phishing, malicious approval or device compromise is suspected, stop signing and transferring, disconnect the suspicious page and review approvals and transaction history from a trusted device.
When a task involves a third-party contract, bridge, validator or web service, separate that external risk from the wallet itself. A wallet can display and sign a request, but it cannot guarantee the safety of outside code or services.
Seed phrases and private keys remain under the user’s control. Legitimate support should not ask for a seed phrase, private key or verification code. Review address, network and amount before transferring; blockchain transactions generally cannot be unilaterally reversed by a wallet. Third-party DApps and smart contracts carry risk, so review spender and permission scope and consider revoking unused approvals.