Support

identify the problem category first

Useful troubleshooting information includes a transaction hash, public address, network name and error message; a seed phrase or private key is never needed. This matters in practice because blockchain outcomes are determined by the selected network and the request that is signed, not merely by what a button is called. For identify the problem category first, prioritize information you can verify: the active network, public address, contract target and transaction status. Turning those details into a repeatable checklist is more reliable than reacting to vague interface messages.

For asset and transaction issues, verify the on-chain state first before deciding whether the problem is display, network selection or execution. It also helps to separate three layers: what the wallet displays, what the network has actually recorded, and what a third-party service claims. When something looks wrong, identify the layer first and then verify with a transaction hash, block explorer or explicit network parameters. No legitimate identify the problem category first workflow requires a seed phrase, private key or verification code to be sent to another person.

prepare non-sensitive information

For asset and transaction issues, verify the on-chain state first before deciding whether the problem is display, network selection or execution. It also helps to separate three layers: what the wallet displays, what the network has actually recorded, and what a third-party service claims. When something looks wrong, identify the layer first and then verify with a transaction hash, block explorer or explicit network parameters. No legitimate prepare non-sensitive information workflow requires a seed phrase, private key or verification code to be sent to another person.

Reject any “support” request that asks for keys, verification codes, remote control or screen sharing of sensitive information. If the action includes a signature, approval or contract call, inspect the permission scope and possible asset impact separately. Friendly labels are not a substitute for the underlying request. Check the target, asset, amount or allowance, network and final confirmation details before proceeding. This sequence reduces mistakes caused by urgency, phishing or the wrong network.

• Verify the network, address and public on-chain information relevant to prepare non-sensitive information.
• Never send a seed phrase, private key or verification code to anyone.
• For DApps or contracts, review each signature and approval scope separately.

troubleshoot using on-chain facts

Reject any “support” request that asks for keys, verification codes, remote control or screen sharing of sensitive information. If the action includes a signature, approval or contract call, inspect the permission scope and possible asset impact separately. Friendly labels are not a substitute for the underlying request. Check the target, asset, amount or allowance, network and final confirmation details before proceeding. This sequence reduces mistakes caused by urgency, phishing or the wrong network.

Useful troubleshooting information includes a transaction hash, public address, network name and error message; a seed phrase or private key is never needed. This matters in practice because blockchain outcomes are determined by the selected network and the request that is signed, not merely by what a button is called. For troubleshoot using on-chain facts, prioritize information you can verify: the active network, public address, contract target and transaction status. Turning those details into a repeatable checklist is more reliable than reacting to vague interface messages.

never disclose keys to anyone

Useful troubleshooting information includes a transaction hash, public address, network name and error message; a seed phrase or private key is never needed. This matters in practice because blockchain outcomes are determined by the selected network and the request that is signed, not merely by what a button is called. For never disclose keys to anyone, prioritize information you can verify: the active network, public address, contract target and transaction status. Turning those details into a repeatable checklist is more reliable than reacting to vague interface messages.

For asset and transaction issues, verify the on-chain state first before deciding whether the problem is display, network selection or execution. It also helps to separate three layers: what the wallet displays, what the network has actually recorded, and what a third-party service claims. When something looks wrong, identify the layer first and then verify with a transaction hash, block explorer or explicit network parameters. No legitimate never disclose keys to anyone workflow requires a seed phrase, private key or verification code to be sent to another person.

• Verify the network, address and public on-chain information relevant to never disclose keys to anyone.
• Never send a seed phrase, private key or verification code to anyone.
• For DApps or contracts, review each signature and approval scope separately.