Talk to Support
Ask for private help and return to your conversation history when the issue is account-specific.
TL;DR
- Use private support for issues that should not be posted publicly.
- Include useful context, but never share a recovery phrase or private key.
- Reopen conversation history to follow the same issue.
Private Support is for account, wallet or transaction context that should not appear in public feedback. It can help investigate an issue, but it cannot reverse a confirmed on-chain action.
Choose private Support for private context
Use public feedback for product ideas that others can review. Use Support when the issue depends on your account, a safe transaction identifier or a conversation that should remain private.
Start or return to the same conversation
Return through conversation history when you have new evidence for the same issue. That keeps the relevant context together and avoids creating competing requests.
Share enough context without sharing access
Describe the page or action, what you expected, what happened and any safe error text. A public transaction hash can help with an on-chain issue. Remove account secrets and private recovery material before sending.
Support never needs wallet control
Never send a recovery phrase, seed phrase or private key. Do not move funds or sign an unexplained request because somebody claims it will verify or recover the account.
Common questions
What should I include when an action failed?
Include the page, intended action, approximate sequence, safe error text and a public transaction hash if one exists. Check platform status first when several live surfaces appear affected.
Can I follow an existing issue without opening a duplicate?
Yes. Open Support conversations, choose the existing conversation and add the new safe detail there.
What if Support appears to ask for a secret or signature?
Stop and reopen the trusted route yourself. Recognise official support and links explains how to verify the destination and reject unsafe requests.