Separate the information boundaries
The security boundary for Support should remain clear: a normal workflow does not require sending a seed phrase, private key, or verification code to an unknown site, third party, or support agent. Self-service support starts with public, verifiable information such as transaction hash, network, destination address, and error text. If the domain is uncertain, the network does not match, or the permission scope is not understood, rejecting the request and verifying the context is safer than “trying it once.” for a delayed deposit, check on-chain state first.
Protocol rules versus service terms
For Support, put the most important fact first: seed phrases, private keys, and verification codes are not troubleshooting inputs. This is not just terminology; it changes what should be checked next. Treat the current network, account, target, and expected outcome as one context. If any of those elements conflicts with the task you intended to perform, stop before the next confirmation. for a delayed deposit, check on-chain state first.
What the user can verify directly
Many mistakes around Support come from mixing two states that look similar but are not equivalent. for a missing asset, check network and token contract first. Ask whether the information you are reading is wallet-interface state, public on-chain state, or a third-party service’s internal state. They can be related without updating at the same time. after a suspicious signature, inspect approvals and subsequent transactions rather than continuing with unknown support contacts.
Handling third-party status
for a delayed deposit, check on-chain state first. In the full Support workflow, the highest-value checks happen before confirmation: verify the source, verify the network and target, and understand the result the request can create. A button labeled “continue” or “complete” does not describe the actual on-chain effect; parameters and permissions do. after a suspicious signature, inspect approvals and subsequent transactions rather than continuing with unknown support contacts.
Do not guess when evidence is missing
When something involving Support does not look right, prioritize evidence that can be checked independently. when a third party is involved, separate verifiable chain facts from that service’s internal policy. Record the transaction hash, network, address, contract, or error information that applies, then compare it with public on-chain records. This turns a vague mismatch into a specific troubleshooting question instead of encouraging repeated retries. seed phrases, private keys, and verification codes are not troubleshooting inputs.
Risk and support boundaries
For routine Support use, a repeatable sequence is more useful than reacting only when a warning appears. after a suspicious signature, inspect approvals and subsequent transactions rather than continuing with unknown support contacts. A practical order is: identify the environment, confirm the target, understand the permission, perform the action, save public evidence, and remove connections or approvals that are no longer needed. seed phrases, private keys, and verification codes are not troubleshooting inputs.
Key boundary
Service information should separate protocol facts, third-party terms, and market changes. When evidence is unavailable, do not invent an outcome. Support should also preserve the boundary that seed phrases and private keys remain under the user’s control.
Continue with a verified workflow
Review the network, address, request details, and security checks before you act.