Scope note
This page is the public starting point for institutional evaluators, market makers, compliance teams, and technical diligence readers. It maps the public resources that exist today and states which enterprise-only details are not published on this docs surface.Choose your institutional reading mode
| If you are evaluating… | Start here | Then continue |
|---|---|---|
| platform model and custody/trust boundaries | What is DerivaDEX? | How DerivaDEX Works and Trusted Hardware and Security Model |
| public API and integration posture | For Builders | API Reference, Rate Limits and Access Tiers, and Error Reference |
| market structure, risk, and execution protections | Trading Safeties and Guards | Margin Requirements, Price Feeds and Mark Price Inputs, and Funding Rate Logic |
| governance and operating-context posture | For Governance and Compliance | Governance Process and Public Decision Reference, Governance Mechanics and Voting Threshold Reference, and Regulatory and Compliance Approach |
Institutional onboarding map
| Need | Start here | Why |
|---|---|---|
| platform and operating-model overview | What is DerivaDEX? | frames the platform, account model, and trust boundaries before diligence turns into line-item review |
| market availability and product baseline | Supported Markets and Constraints | captures the current public product posture and deployment caveats |
| public API and transport diligence | For Builders and API Reference | routes technical teams into the current public REST and realtime contract surface |
| contract and governance diligence | Reference and For Governance and Compliance | covers contract addresses, governance mechanics, and safety references |
| operating-context and compliance posture | Regulatory and Compliance Approach | explains the public compliance and governance story without inventing a private legal handbook |
| one disciplined pass across the current public diligence surface | How to Run a Public Institutional Diligence Review | turns the route map into one repeatable institutional review workflow |
| the public onboarding reading order before any enterprise-specific escalation | Institutional Onboarding Public Baseline | separates the public baseline from any private onboarding workflow |
Public diligence packet
| Topic | Public route |
|---|---|
| margin, liquidation, and solvency controls | Margin Requirements, Trading Safeties and Guards, and Price Formation, Risk Controls, and Solvency |
| contract surfaces and deployment targeting | Smart Contract Addresses and Core Contract Reference and Smart Contract Facet, Selector, and Event Reference |
| governance process and execution constraints | Governance Process and Public Decision Reference and Governance Mechanics and Voting Threshold Reference |
| API rate posture and lifecycle semantics | Rate Limits and Access Tiers, Order and Account Event Reference, and Error Reference |
| trusted-compute and security model | Trusted Hardware and Security Model and Cryptographic Security Model |
| public diligence and market-maker evaluation map | Institutional Diligence and Market-Maker Evaluation Reference |
What this page helps you avoid
Use this page to avoid three common diligence mistakes:- treating public explanation pages as though they were already a private diligence room
- reading only governance or only API docs when the institutional question actually spans both
- inferring unpublished SLAs, commercial terms, or private onboarding steps from public route presence
Market-maker evaluation routes
| If the evaluation is about… | Best public route |
|---|---|
| transport, latency, and state-management posture | Implement High-Frequency Trading Strategies, Optimize WebSocket Connection Performance, and Performance Engineering for Strategy Builders |
| execution guards, price bands, and solvency behavior | Trading Safeties and Guards, Price Feeds and Mark Price Inputs, and Funding Rate Logic |
| venue model compared with centralized exchange assumptions | How to Migrate from Binance or Bybit to DerivaDEX and Binance and Bybit Client Migration Mapping |
| public market-maker review boundaries | Market Maker Evaluation and Program Boundaries |
Regulatory and public-policy resources
| Public resource | Use it for |
|---|---|
| Regulatory and Compliance Approach | public explanation of governance, compliance, and restricted-surface boundaries |
| Digital Assets Supervision and Regulation in Bermuda | external operating-context source already referenced by the docs |
| Community Resources | official public governance and legacy continuity surfaces |
Support and escalation routes
| Need | Public route |
|---|---|
| documentation clarification during diligence | Support Channels |
| public governance or proposal history | Community Resources |
| AI-assisted exploration of the current public docs surface | Use DerivaDEX Docs with AI Tools |
| conceptual explanation of why institutional diligence spans multiple doc families | Institutional Diligence, Market Structure, and Public Boundaries |
Publication boundary
This public docs surface does not currently publish a private due-diligence room, dedicated institutional SLA, rebate schedule, enterprise custody runbook, or jurisdiction-by-jurisdiction legal packet. Use the published routes above first, then escalate through Support Channels when the public contract is insufficient.When the public packet is not enough
If a diligence question depends on a non-public operating detail, treat that as a publication-boundary issue, not as an omission you should fill by inference. Use Support Channels and name:- the specific public route you checked
- the exact unanswered question
- whether the gap is commercial, technical, governance-related, or compliance-related