Community
CRX is software run by an operator — a company, not a DAO — and the operating desk answers directly. This page routes each role to its fastest path and lists what to bring with a question.
Where to reach CRX?
Through the operator. CRX is software run by an operator: a company, not a DAO. When a firm reaches out, the operating desk answers directly. There is no support queue between the firm and the network.
The fastest path depends on the role.
| Role | Goal | Reach for |
|---|---|---|
| A trading firm (taker) | To onboard a desk and start sending RFQs | The onboarding flow, then the operator directly |
| A market maker | To list a desk and quote pairs | The operator; makers are approved one by one |
| A builder | To wire the API, an SDK path, or an agent | Developers → Introduction (~2 min), then the operator for access |
| A partner | To offer a deliverable forward to its own customers | The operator; partner terms are agreed directly with CRX |
How is the network governed?
By the operator, not by a token vote. There is no governance forum to lobby and no proposal to pass. Changes to pairs, sessions, and contracts are operator decisions, published in the docs.
- Pair and session changes land in
config/pairs.jsonand surface on Pairs & Marks API (~3 min). - The model itself lives in How CRX works (~3 min).
How to report a problem or ask a question?
Bring it to the operator with the on-chain facts attached. Every trade settles on-chain. Most questions are about a real trade, a real address, or a real mark, and those are all readable on-chain.
Before reaching out, gather what can be read directly:
- The address and the agreement id, if the question is about a position.
- The pair label and the on-chain mark, if the question is about pricing.
- The relayer response or error, if the question is about the API.
This is not a barrier; it is the shortest path to an answer. The operator reads the same chain the firm does, and a question that names the address resolves in one round trip.
Support is direct: the firm reaches the operating desk, not a ticket queue.