Help Center
Help is the way to reach the GraphDex team — bug reports, support requests, and product feedback all flow through one form.
The Help button on the bottom toolbar opens an external feedback form. Use it whenever something doesn't behave as expected, or when you have product feedback that the team should see.
Help isn't only for incidents. It's also the right channel for "this is confusing" reports, missing-context complaints, and feature requests. The more concrete the report, the faster the team can act on it — exact page, exact action, exact wallet / transaction / token / order identifier when relevant.
There's one hard line: never include your seed phrase, private keys, wallet passwords, or one-time codes. Support never needs them; a report that contains them is a report you can't safely send.
One form, every report
Open Help from the bottom toolbar and tell the team what you ran into — bug, confusion, or a feature you'd like to see.
When to Use Help
Send product feedback — what worked, what didn't, what's missing.
Submit a bug report with the right context attached.
Every officially supported way to reach the GraphDex team.
WHAT TO REPORT
Help is the right channel for all of these — even if the issue feels small.
Sign-in / connection problems — wallet won't connect, OAuth flow breaks, sign-in modal misbehaves.
Wallet or account issues — balances look wrong, account-level controls don't respond, wallet selector errors out.
Trading flow errors — order panel rejects an action, presets don't apply, transaction fails for an unclear reason.
Data issues — incorrect or confusing numbers in Research, Pulse, Wallet, Earn, or Referrals.
Feature feedback — something is confusing, missing, or hard to find.
General product feedback — anything else the team should see.
BEFORE YOU SEND
A 30-second sanity check before opening the form turns most reports from "unclear" into "actionable".
Confirm you're on the official GraphDex terminal — domain
terminal.graphdex.io.Refresh the page and check whether the issue still happens.
Note the page and section where the issue happened.
Collect relevant identifiers: wallet address, transaction hash, token address, order ID.
Note your device, browser, and whether you're using desktop browser, mobile browser, or Telegram.
If a field on the form doesn't apply to your case, leave it blank or explain that it isn't relevant.
WHAT NOT TO SHARE
A short list, hard rule:
Never share your seed phrase or recovery phrase.
Never share private keys.
Never share wallet passwords or vault passwords.
Never share one-time codes (SMS / authenticator / email).
GraphDex support will never ask for any of the above. Any request that does is a phishing attempt.
More to Explore
Custody, seed phrases, and how GraphDex's non-custodial model works.
What's expected behaviour on a Solana trading flow vs. an actual bug.
Settings that change order outcomes — read before reporting "the order behaved oddly".
The list of pre-flight checks every new account should run.
What the team can and can't see in a report you send.
Product terms that frame what's in scope for support.
The Help button opens an external form — complete it with enough context for the team to understand what happened, and leave fields blank when they don't apply.
FAQs
How do I send a report?
Open the Help button on the bottom toolbar — it opens the external feedback form. Complete the fields that apply to your case.
What should a good bug report include?
The page and section where the issue happened.
What you did, what you expected, what actually happened.
Wallet address, transaction hash, token address, or order ID when relevant.
Your device, browser, and whether you were on desktop, mobile browser, or Telegram.
A note if you've already tried refreshing the page.
What absolutely must never go in a report?
Seed phrases, private keys, wallet passwords, vault passwords, and one-time codes. GraphDex support will never ask for any of these — a request that does is a phishing attempt.
Can I send feature requests through Help?
Yes. Feature requests, "this is confusing", and general product feedback all flow through the same form. See Feedback.
The form has a field that doesn't apply to my case — what do I do?
Leave it blank, or note that it doesn't apply to your case. Don't fabricate a value just to fill a field.
Where are the official support contacts?
See Support Contacts for every officially supported way to reach the team.
Last updated