> 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/support-contacts.md).

# Support Contacts

**Use the in-terminal Help button. Verify every other channel before sending anything.**

The current verified support path is the **`Help` button inside the GraphDex terminal**. It opens the active feedback and support form — that's the safest default channel because it starts from the official terminal.

{% hint style="danger" %}
**Support will never ask for your seed phrase**

If anyone — claiming to be GraphDex support, a moderator, or a team member — asks for seed phrases, private keys, passwords, one-time codes, or remote access to your device, **stop the conversation immediately**.
{% endhint %}

## Use the In-Terminal Help Button

To contact GraphDex from the terminal:

1. Open the **GraphDex terminal**.
2. Select **`Help`**.
3. Complete the external form that opens.
4. Include enough context for the team to review the request — see [Report a Bug](/graphdex-docs/help-and-feedback/report-a-bug.md) for what to include.

This is the canonical channel. Other channels exist, but this is the one to default to.

## Verify External Channels

If you contact GraphDex through **Telegram, X, email, or another external channel**:

* **Verify the destination** from an official GraphDex source before sending information.
* Scammers actively impersonate support accounts on every channel.
* **Do not trust unsolicited direct messages** — legitimate support doesn't message you out of the blue.

When in doubt, return to the terminal Help button and ignore unsolicited contacts.

## What Support Should NOT Ask For

Support does not need — and should never request:

* **Your seed phrase.**
* **Private keys.**
* **Wallet passwords.**
* **One-time codes / 2FA codes.**
* **Remote access to your device.**

If someone asks for any of those, end the conversation and use the official Help path. The request itself is the red flag — even if the person seems convincing or claims it's needed to "verify your account".

## Urgent Security Issues

If you believe your **wallet or seed phrase is exposed**:

1. **Move funds to a new wallet you control** — immediately, before waiting for a support response.
2. The compromised wallet should be considered fully exposed, including all approved contract permissions.
3. Then file the support request from the new account.

**GraphDex can review platform issues, but it cannot protect funds if a private key or seed phrase has already been exposed.** Speed matters; support comes second.

## 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/p55qs3SWLed6aQsMmJk8"><strong>Feedback</strong></a></td><td>Suggestions and non-urgent comments.</td><td><a href="/files/PvwZariSc5lrxmA3uidW">/files/PvwZariSc5lrxmA3uidW</a></td></tr><tr><td><a href="/pages/YZmAxluf5b4TsOcmr0o0"><strong>Report a Bug</strong></a></td><td>Things actively broken — what to send.</td><td><a href="/files/PvwZariSc5lrxmA3uidW">/files/PvwZariSc5lrxmA3uidW</a></td></tr><tr><td><a href="/pages/LC4oLkz3tnN9Jv7mafzw"><strong>Wallet Security Notes</strong></a></td><td>The full wallet-side security playbook.</td><td><a href="/files/BWULSHt4tqY255s7X9t1">/files/BWULSHt4tqY255s7X9t1</a></td></tr></tbody></table>

{% hint style="info" %}
The single best defence against support impersonation is to always start from the in-terminal Help button — let GraphDex come to the conversation, not a stranger to you.
{% endhint %}

## FAQs

<details>

<summary>How fast is support?</summary>

Response time depends on volume and severity. Urgent security issues should be paired with self-rescue actions (move funds first); routine requests follow normal queues.

</details>

<details>

<summary>Is there a phone number for support?</summary>

The canonical channel is the in-terminal Help button. Other channels, when verified, are listed by official GraphDex sources.

</details>

<details>

<summary>Someone DM'd me claiming to be GraphDex support. What do I do?</summary>

Don't engage. Legitimate support starts from your in-terminal Help submission, not from an unsolicited DM. Block, ignore, and report through the official channel.

</details>

<details>

<summary>Why does support need so much detail before responding?</summary>

The more context you include, the faster a reproduction or fix is possible. Sparse reports almost always cycle back asking for the same context — providing it upfront saves a round trip.

</details>

<details>

<summary>I lost access to my account. What now?</summary>

Use the in-terminal Help button from a fresh session if possible. If you've lost the seed phrase entirely, GraphDex cannot recover the wallet — the seed phrase is the only key.

</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/support-contacts.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.