Scope note
This page is the public onboarding baseline for institutional readers. It does not replace a private onboarding process, but it does show which public routes should be read before asking for anything enterprise-specific.Public onboarding sequence
| Step | Public route | Why it comes first |
|---|---|---|
| platform model and trust boundaries | What is DerivaDEX? | frames the venue and strategy/account model before diligence turns into implementation questions |
| compliance and governance posture | For Governance and Compliance and Regulatory and Compliance Approach | anchors the current public compliance story and restricted-surface boundaries |
| public API and access-tier posture | API Reference and Rate Limits and Access Tiers | establishes the current public transport and quota baseline |
| product, safety, and liquidation controls | Supported Markets and Constraints, Margin Requirements, and Trading Safeties and Guards | covers the public risk and product contract before operational onboarding questions |
| settlement and contract targeting | Smart Contract Addresses and Core Contract Reference and Price Formation, Risk Controls, and Solvency | closes the loop on public contract and solvency posture |
Public answers to common onboarding questions
| Question | Public route |
|---|---|
| what is the public compliance baseline | Regulatory and Compliance Approach |
| what are the current public API access tiers | Rate Limits and Access Tiers |
| how are settlement and withdrawal timing explained publicly | Product and Trading Specifications and Request Lifecycle: Sequencing, Execution, and Finality |
| where should technical diligence start | How to Run a Public Institutional Diligence Review |
| how should public onboarding questions be escalated | Support Channels |
What you should leave this page with
After reading the public onboarding baseline, you should know:- which public routes define custody, settlement, and trust boundaries
- which public routes define transport, rate, and product posture
- which public routes define governance and compliance framing
- which questions belong in public docs and which ones cross into private onboarding or diligence-room territory