Start here if you operate DerivaDEX infrastructure
Use the operator route when your questions involve node operation, restricted control surfaces, or operational trust and safety context.What the public docs cover for operators
| Need | Public first stop | What this public route actually provides |
|---|---|---|
| Prepare a first operator-backed localnet baseline | Setting Up a DerivaDEX Node | Public-safe first-success path for mode selection, shared prerequisites, and baseline discipline before deeper operator procedures |
| Verify whether an operator-backed environment is actually ready | How to Verify Operator Localnet Readiness | A focused readiness procedure for mode, contract, and dependency checks |
| Troubleshoot attestation, recovery, monitoring, update, or tuning gaps | How to Troubleshoot SGX Attestation Issues, How to Handle Node Downtime and Recovery, How to Set Up Node Monitoring and Alerting, How to Update Node Software Safely, or How to Optimize Node Performance | Public-safe operational procedures for the first recurring node-operations failure classes |
| Look up fixed node-operations facts | Node Operations Reference | Factual mode, contract, readiness, and public-boundary lookup |
| Understand the operating model | How DerivaDEX Works | The hybrid execution and settlement model, plus the role of operators in the public trust story |
| Understand sequencing, execution, and finality | Request Lifecycle: Sequencing, Execution, and Finality | Public explanation of deterministic sequencing, receipts, and update propagation |
| Understand restricted API-family boundaries | Operator & Restricted APIs | Boundary summary, authoritative source ownership, and public-route handling for restricted operator and compliance surfaces |
| Understand public safety controls | Trading Safeties and Guards | Publicly documented validation, solvency, and safety constraints that affect trust and system behavior |
| Escalate documentation or restricted-surface questions | Support Channels | Public support routing rather than a private operator manual |
Public docs boundary
This route is intentionally not a full node-operations runbook. The public docs currently provide:- boundary summaries for restricted operator and compliance-oriented APIs
- public-safe localnet mode, readiness, and baseline-contract guidance for first operator-backed setup work
- public-safe node-operations procedures for SGX troubleshooting, recovery classification, monitoring baselines, controlled update flow, and signal-driven tuning
- public explanation of sequencing, safety, and settlement posture
- public reference pages for safeguards, contract addresses, and governance-relevant controls
- support routing when a question requires the owning operational process
- a full restricted endpoint catalog for operator-only or compliance-only surfaces
- a full private node deployment, monitoring, upgrade, or incident-response manual
- private operational credentials, internal escalation paths, or non-public infrastructure procedures
Recommended path
- Read Setting Up a DerivaDEX Node for the public-safe first-run path.
- Read Node Operations Reference for the fixed mode, contract, readiness, and monitoring facts.
- Use How to Verify Operator Localnet Readiness for the first focused environment check.
- Use How to Troubleshoot SGX Attestation Issues or How to Handle Node Downtime and Recovery when the environment is already failing.
- Use How to Set Up Node Monitoring and Alerting, How to Update Node Software Safely, and How to Optimize Node Performance once the environment is healthy enough for controlled operations work.
- Read How DerivaDEX Works and Request Lifecycle: Sequencing, Execution, and Finality for the wider system context.
- Read Operator & Restricted APIs when you need to confirm whether a surface is intentionally public, restricted, or compliance-oriented.
- Use Troubleshooting and Support Channels for operational escalation paths.
Handoff map
| If the question becomes… | Use this public route | Then do this |
|---|---|---|
| a restricted API-family visibility question | Operator & Restricted APIs | confirm the boundary and source artifact before asking for deeper access through the owning operational process |
| a public safety or solvency question | Trading Safeties and Guards | anchor the question in the documented safeguard or failure mode before escalating |
| a docs mismatch or missing public statement | Support Channels | include the exact page URL, route, and conflicting statement |
| a private operational runbook request | Support Channels | request the correct owner rather than assuming the public docs are the right carrier |