Official community resources
| Resource | Use it for | URL |
|---|---|---|
| Governance Forum | Proposal discussion, idea-stage governance threads, and upgrade review | forum.derivadex.com |
| DIPs repository | Proposal specifications and implementation history for mature governance work | gitlab.com/derivadex/dips |
| Legacy public docs | Historical governance and trading walkthroughs that still provide context for older public references | docs.derivadex.io |
| Community support | Public trading and integration help when docs are not enough | Discord |
| Institutional and developer resource maps | Public route maps for diligence, integration, and education | Community & Support |
| AI tooling guide | MCP and skill discovery for AI-assisted use of the current docs surface | Use DerivaDEX Docs with AI Tools |
Choose the right resource by job stage
| If you are in this stage… | Best resource | Why | | --- | --- | | learning the current public product or API surface | docs.derivadex.com first | current Mintlify routes are the active public authority | | discussing an idea or reviewing a governance concept before it is formalized | Governance Forum | forum discussion is earlier-stage than formal proposal history | | reading a mature governance proposal or historical implementation trail | DIPs repository | DIPs are the proposal and implementation archive, not the first discussion venue | | interpreting an old screenshot, link, or community reference | legacy public docs | use legacy docs for continuity, not for current authority | | seeking human help after published docs are exhausted | Discord | community help belongs after self-serve public docs checks |When to use each
- Use the Governance Forum for early-stage discussion and proposal review.
- Use the DIPs repository when the idea has reached a formal proposal or implementation stage.
- Use the legacy public docs for historical continuity, not as the canonical current docs surface.
- Use Discord when you need help after checking docs, FAQ, and troubleshooting.
How the official surfaces fit together
| Surface | Main role | Not the right choice for |
|---|---|---|
docs.derivadex.com | current canonical public docs | historical continuity or free-form community discussion |
| Governance Forum | discussion, debate, proposal iteration | canonical technical reference or final implementation history |
| DIPs repository | mature proposal artifacts and implementation lineage | early-stage brainstorming |
| Legacy public docs | continuity for older routes and concepts | overriding the current Mintlify docs |
| Discord | community help and clarification after self-serve docs | acting as the canonical spec or policy source |
Boundary note
The current canonical public docs surface is docs.derivadex.com. Use the legacy docs and forum as supporting official resources, but prefer the current public Mintlify routes when two sources cover the same reader task.Legacy continuity warning
The legacy docs are still useful for historical context, but they can lag the current public route structure and current API-boundary posture. Use them to interpret older links, screenshots, or forum references, not to override the current Mintlify routes.When to escalate from docs to community channels
Escalate from docs into Discord or forum surfaces only when one of these is true:- the public docs do not answer the question after you checked the owning route
- two public routes appear inconsistent
- an older forum, DIP, or legacy-doc link no longer matches the current public surface
- you need discussion or clarification rather than a factual reference lookup