> For the complete documentation index, see [llms.txt](https://onchain-cc.gitbook.io/onchain-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://onchain-cc.gitbook.io/onchain-docs/resources/support.md).

# Support & Community

{% hint style="warning" %}
Only trust official links. Scammers impersonate support — the team will **never** DM you first, and no legitimate agent will ever ask for your seed phrase, private key, or wallet access. If someone does, it's a scam. Report and block.
{% endhint %}

***

## Official Channels

| Channel            | Link                                                   | Purpose                                                   |
| ------------------ | ------------------------------------------------------ | --------------------------------------------------------- |
| **Discord**        | [discord.gg/ZwjRVnM25w](https://discord.gg/ZwjRVnM25w) | Primary support — help channels, community, announcements |
| **X / Twitter**    | [@Onchaincc](https://x.com/Onchaincc)                  | Announcements and updates                                 |
| **In-app support** | **Get support** in the terminal menu                   | Live chat with the support team                           |
| **Website**        | [onchain.cc](https://onchain.cc)                       | The official terminal and these docs                      |

When in doubt about any link, navigate directly to [onchain.cc](https://onchain.cc) and use the official links there.

***

## Getting Help

**In the terminal:** open the menu → **Get support** for live chat.

**On Discord:**

1. Join the official server: [discord.gg/ZwjRVnM25w](https://discord.gg/ZwjRVnM25w)
2. Head to the help channel and describe your issue clearly — include the transaction signature if it's about a specific trade (find it in your wallet's transaction history or the confirmation screen).
3. A team member or moderator will respond. The community channels have answered most common issues already.

***

## What Support Can Help With

* How any product works — Spot, Perps, Trenches, Predictions, Swap
* Troubleshooting failed or stuck transactions
* Fees, gas, funding, and transfer questions
* Colosseum — points, rank, quests, loot boxes, session results
* Login and wallet connection issues
* Reporting bugs, scam accounts, or phishing

## What Support Cannot Do

onchain.cc is self-custody — some things are impossible by design:

* Recover funds sent to a wrong address
* Reverse confirmed on-chain transactions
* Access your wallet or move funds on your behalf
* Recover a lost seed phrase or private key — only you hold these
* Guarantee outcomes in Colosseum scoring or prize disputes

If you lose your seed phrase, that wallet's funds cannot be recovered by anyone. Store it securely and offline.

***

## Security Reminders

* The team will **never** DM you first.
* Never share your seed phrase or private key with anyone, ever.
* Always verify you are on **onchain.cc** before connecting a wallet — bookmark it and use the bookmark.


---

# 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://onchain-cc.gitbook.io/onchain-docs/resources/support.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.