> 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/report-a-bug.md).

# Report a Bug

**Something broke? Tell us in a way the team can reproduce — that's what makes the fix fast.**

A bug report is most useful when it gives the team a clear path to repeat the issue. This page is a checklist for everything that helps — and the things that should never appear in a bug report no matter what.

{% hint style="warning" %}
**Never include secrets**

Seed phrases, private keys, wallet passwords, and one-time codes don't belong in any bug report — not even when support seems to need them.
{% endhint %}

## Useful Details

Include as many of these as you can:

* **Page or section** — where the issue happened.
* **Short description** — one or two sentences summarizing what's wrong.
* **Steps to reproduce** — what you did before the issue appeared.
* **Expected behaviour** — what you thought would happen.
* **Actual behaviour** — what actually happened.
* **Device type** — phone, tablet, desktop.
* **Browser or Telegram client** — version when known.
* **Relevant context** — wallet address, transaction hash, token address, or order details (no secrets, see below).

A clear path to reproduce gets a fix faster than three paragraphs without one.

## Account and Wallet Issues

For account or wallet bugs, add:

* **Sign-in method** used to access the account.
* **Connected wallet type** — Phantom, MetaMask, etc.
* **Network** — Solana, Ethereum, others as relevant.
* **Wallet address** if relevant to the issue (public address only).
* **Exact error message** when one appeared, copy-paste verbatim.

**Never include:**

* Seed phrases.
* Private keys.
* Wallet passwords.
* One-time codes / 2FA codes.

If a request seems to need any of those, it's not a legitimate request — stop and verify the channel through official support.

## Trading Issues

For trading-related bugs:

* **Token address or pair.**
* **Order type** — Market / Limit.
* **Amount.**
* **Time of the attempt** — UTC if possible.
* **Transaction hash** when one was created.
* **Trading Settings** at the time — Slippage, Priority, Bribe.

If a transaction **reached the blockchain**, verify it in a block explorer first and include the transaction hash. The on-chain record is the ground truth.

## Attachments

If the form supports file uploads:

* Attach **only materials that help explain the issue.**
* **Remove private information** before uploading — crop screenshots to avoid revealing balances, addresses, or other context you don't need to share.
* No videos longer than the bug actually requires.

## 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>Non-urgent product input and suggestions.</td><td><a href="/files/PvwZariSc5lrxmA3uidW">/files/PvwZariSc5lrxmA3uidW</a></td></tr><tr><td><a href="/pages/zVHQSJGOhNXlOmHc6rdt"><strong>Support Contacts</strong></a></td><td>The right channel for direct help.</td><td><a href="/files/PvwZariSc5lrxmA3uidW">/files/PvwZariSc5lrxmA3uidW</a></td></tr><tr><td><a href="/pages/kGGY16v3DG6hCVobbNZN"><strong>Help Center</strong></a></td><td>The overview of every help-side option.</td><td><a href="/files/PvwZariSc5lrxmA3uidW">/files/PvwZariSc5lrxmA3uidW</a></td></tr></tbody></table>

{% hint style="info" %}
For urgent security issues — exposed seed phrase, suspected wallet compromise — move funds to a new wallet first. See [Wallet Security Notes](/graphdex-docs/wallet/wallet-security-notes.md).
{% endhint %}

## FAQs

<details>

<summary>How long until my bug is fixed?</summary>

Depends on severity and reproducibility. A clean reproduction path is the single biggest accelerator — vague reports always take longer than precise ones.

</details>

<details>

<summary>Should I screenshot the bug?</summary>

When it's visual or layout-related, yes. Strip sensitive info (wallet addresses, balances) that isn't relevant to the bug before uploading.

</details>

<details>

<summary>What's the difference between a bug report and feedback?</summary>

Bugs are things broken now. Feedback is everything else — suggestions, friction, requests, general comments. See \[Feedback]\(feedback.md).

</details>

<details>

<summary>Why does the team need my Trading Settings?</summary>

Trade-related bugs often depend on the execution profile (Slippage, Priority, Bribe). Without those values, reproducing the bug is guesswork.

</details>

<details>

<summary>I can't reproduce the bug myself. Should I still report it?</summary>

Yes — describe what you remember and the conditions you were in. Even a partial report can correlate with other reports the team is tracking.

</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/report-a-bug.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.