Scope note
This page is the structured lookup surface for institutional evaluators, market makers, and diligence teams reading the current public docs contract. It does not publish a private diligence room, bespoke commercial terms, or a private onboarding checklist.Public diligence artifact families
| Diligence area | Primary public routes |
|---|---|
| platform model and product baseline | What is DerivaDEX?, Supported Markets and Constraints, Product and Trading Specifications |
| execution safety, risk, and solvency | Trading Safeties and Guards, Margin Requirements, Price Formation, Risk Controls, and Solvency |
| technical integration and transport posture | API Reference, Rate Limits and Access Tiers, Order and Account Event Reference |
| contract and upgrade surfaces | Smart Contract Addresses and Core Contract Reference, Smart Contract Facet, Selector, and Event Reference, Smart Contract Architecture and Upgrade Boundaries |
| governance, token, and proposal controls | Governance Process and Public Decision Reference, Governance Mechanics and Voting Threshold Reference, DDX Token Specifications, Governance Proposal Templates and Requirements |
| regulatory and public-boundary posture | Regulatory and Compliance Approach, Institutional Resources, Support Channels |
Minimum public diligence checklist
| Evaluation question | Primary public evidence | What to verify |
|---|---|---|
| what exactly is the trading and market-structure model | What is DerivaDEX?, Central Limit Order Book in DeFi, Product and Trading Specifications | product scope, order model, settlement posture, and market constraints |
| how private write requests are authorized and recovered | REST Authentication, Request Signing Reference, Error Reference | signing, replay-window policy, encryption, and error recovery classes |
| how live state is reconciled | Realtime Connection Model, Order and Account Event Reference | bootstrap rules, ordering fields, reconnect posture, and event-family semantics |
| how on-chain upgrade and governance control works | Smart Contract Addresses and Core Contract Reference, Smart Contract Facet, Selector, and Event Reference, Governance Process and Public Decision Reference | address targeting, diamond routing, governance evidence chain, and upgrade boundaries |
| what remains outside the public contract | this page plus Support Channels | whether the missing item is private, restricted, deployment-conditional, or simply unpublished |
Market-maker evaluation surfaces
| If the evaluation is about… | Primary public routes |
|---|---|
| low-latency client behavior and ordered-state handling | How to Implement High-Frequency Trading Strategies, How to Optimize WebSocket Connection Performance, Performance Engineering for Strategy Builders |
| order validity, price bands, and liquidation behavior | Product and Trading Specifications, Trading Safeties and Guards, Margin Requirements |
| pricing and funding mechanism assumptions | Price Feeds and Mark Price Inputs, Funding Rate Logic |
| exchange-model differences from CEX workflows | How to Migrate from Binance or Bybit to DerivaDEX, Binance and Bybit Client Migration Mapping, Central Limit Order Book in DeFi |
Public operational and compliance surfaces
| Topic | Current public route |
|---|---|
| institutional routing and due-diligence map | Institutional Resources |
| regulated operating-context explanation | Regulatory and Compliance Approach |
| public governance and policy discussion anchors | Community Resources |
| documentation clarification and unresolved-boundary escalation | Support Channels |
Evidence to capture during a diligence pass
| Evidence item | Why keep it |
|---|---|
| exact public route and heading | identifies the public contract actually relied on |
| deployment-conditional caveat | prevents a baseline code constant from being treated as a universal live promise |
| unresolved-boundary classification | distinguishes private, restricted, unclear, and deployment-conditional gaps |
| escalation target | keeps follow-up precise when the public surface is insufficient |
Public-boundary limits
| Topic | Current public status |
|---|---|
| private diligence room | not published on this Mintlify surface |
| dedicated institutional SLA | not published on this Mintlify surface |
| bespoke rebate schedule or market-maker commercial agreement | not published as a public docs contract |
| enterprise custody or settlement runbook | not published as a public docs contract |
| jurisdiction-by-jurisdiction legal packet | not published as a public docs contract |