User Support

Identify the type of issue

For identify the type of issue, the goal is not to memorize labels but to build a repeatable decision sequence: confirm the current network and account context, understand what the requested action changes, and then verify the resulting state on-chain. Service information should explain the mechanism before discussing potential outcomes. For PoS, validators or staking, rewards come from network rules and validation activity. Results can vary with network conditions, validator performance, service fees, exit queues and market prices, so they should never be presented as fixed or guaranteed returns. Identify the type of issue also connects to other wallet tasks. Network choice affects fees and transaction visibility, contract interaction can affect approvals and asset state, and security habits apply across creation, backup, transfers and Web3 use. This page focuses specifically on user support so the guidance can be applied to a real task rather than treated as a generic feature list. The key is to verify network context, understand what the requested action changes, and keep sensitive credentials outside webpages and support conversations.

Prepare non-sensitive information

For prepare non-sensitive information, the goal is not to memorize labels but to build a repeatable decision sequence: confirm the current network and account context, understand what the requested action changes, and then verify the resulting state on-chain. Before participating, users should understand how their assets change state on-chain, what exit conditions apply, whether waiting periods may occur and what role any third-party service plays. Unverified claims about partnerships, licenses, rankings, user counts or guaranteed yields should not be used as decision criteria. When something looks wrong, break prepare non-sensitive information into four questions: what address or contract is involved, which network is active, what action is being requested, and what result should be visible on-chain. This is usually more reliable than repeating the same click. This page focuses specifically on user support so the guidance can be applied to a real task rather than treated as a generic feature list. The key is to verify network context, understand what the requested action changes, and keep sensitive credentials outside webpages and support conversations.

A practical review sequence

1. Confirm the active network and the intended account
2. Verify the address, contract or DApp source
3. Read the exact action, amount and permission scope
4. Verify the public on-chain result after completion

Common self-service checks

For common self-service checks, the goal is not to memorize labels but to build a repeatable decision sequence: confirm the current network and account context, understand what the requested action changes, and then verify the resulting state on-chain. Support and update content should follow a minimum-information principle. Troubleshooting normally requires only non-sensitive data such as the network name, public address, transaction hash, visible error message and approximate action time. Seed phrases, private keys and verification codes should never be provided to another person. For an unfamiliar common self-service checks issue, keep verifiable non-sensitive evidence such as a public address, network name, transaction hash and visible error text. Sensitive credentials are not troubleshooting material and should not be given to support staff. This page focuses specifically on user support so the guidance can be applied to a real task rather than treated as a generic feature list. The key is to verify network context, understand what the requested action changes, and keep sensitive credentials outside webpages and support conversations.

Protect privacy and avoid scams

For protect privacy and avoid scams, the goal is not to memorize labels but to build a repeatable decision sequence: confirm the current network and account context, understand what the requested action changes, and then verify the resulting state on-chain. Service information should explain the mechanism before discussing potential outcomes. For PoS, validators or staking, rewards come from network rules and validation activity. Results can vary with network conditions, validator performance, service fees, exit queues and market prices, so they should never be presented as fixed or guaranteed returns. Protect privacy and avoid scams also connects to other wallet tasks. Network choice affects fees and transaction visibility, contract interaction can affect approvals and asset state, and security habits apply across creation, backup, transfers and Web3 use. This page focuses specifically on user support so the guidance can be applied to a real task rather than treated as a generic feature list. The key is to verify network context, understand what the requested action changes, and keep sensitive credentials outside webpages and support conversations.