> For the complete documentation index, see [llms.txt](https://graphdex-1.gitbook.io/graphdex-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://graphdex-1.gitbook.io/graphdex-docs/help-and-feedback/help-center.md).

# 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.

{% hint style="success" %}
**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.
{% endhint %}

## When to Use Help

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><a href="/pages/p55qs3SWLed6aQsMmJk8"><strong>Feedback</strong></a></td><td>Send product feedback — what worked, what didn't, what's missing.</td><td></td></tr><tr><td><a href="/pages/YZmAxluf5b4TsOcmr0o0"><strong>Report a Bug</strong></a></td><td>Submit a bug report with the right context attached.</td><td></td></tr><tr><td><a href="/pages/zVHQSJGOhNXlOmHc6rdt"><strong>Support Contacts</strong></a></td><td>Every officially supported way to reach the GraphDex team.</td><td></td></tr></tbody></table>

## 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

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><a href="/pages/LC4oLkz3tnN9Jv7mafzw"><strong>Wallet Security Notes</strong></a></td><td>Custody, seed phrases, and how GraphDex's non-custodial model works.</td><td></td></tr><tr><td><a href="/pages/5Xes96FGqPBItzknZigD"><strong>Execution Risks</strong></a></td><td>What's expected behaviour on a Solana trading flow vs. an actual bug.</td><td></td></tr><tr><td><a href="/pages/OMivUziEbyoA9jTgesYW"><strong>Risk of Fast Execution</strong></a></td><td>Settings that change order outcomes — read before reporting "the order behaved oddly".</td><td></td></tr><tr><td><a href="/pages/71OY9SZk9Ui76jk5BOF8"><strong>First Safety Checklist</strong></a></td><td>The list of pre-flight checks every new account should run.</td><td></td></tr><tr><td><a href="/pages/pzgFCR77vWkUAAUEWT9Z"><strong>Privacy Policy</strong></a></td><td>What the team can and can't see in a report you send.</td><td></td></tr><tr><td><a href="/pages/jLUguKqvKJaYie6ap58J"><strong>Terms of Use</strong></a></td><td>Product terms that frame what's in scope for support.</td><td></td></tr></tbody></table>

{% hint style="info" %}
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.
{% endhint %}

## FAQs

<details>

<summary>How do I send a report?</summary>

Open the `Help` button on the bottom toolbar — it opens the external feedback form. Complete the fields that apply to your case.

</details>

<details>

<summary>What should a good bug report include?</summary>

* 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.

</details>

<details>

<summary>What absolutely must never go in a report?</summary>

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.

</details>

<details>

<summary>Can I send feature requests through Help?</summary>

Yes. Feature requests, "this is confusing", and general product feedback all flow through the same form. See [Feedback](/graphdex-docs/help-and-feedback/feedback.md).

</details>

<details>

<summary>The form has a field that doesn't apply to my case — what do I do?</summary>

Leave it blank, or note that it doesn't apply to your case. Don't fabricate a value just to fill a field.

</details>

<details>

<summary>Where are the official support contacts?</summary>

See [Support Contacts](/graphdex-docs/help-and-feedback/support-contacts.md) for every officially supported way to reach the team.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://graphdex-1.gitbook.io/graphdex-docs/help-and-feedback/help-center.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.