Skip to main content

Understand the system design

Use explanations when your primary question is why the platform behaves as it does.

Choose the right explanation

If you want to understand…Start here
the platform model end to endHow DerivaDEX Works
why the architecture differs from other venues or stacksWhy DerivaDEX Is Architected Differently
how the hybrid fast-path and checkpoint model stays coherentUnderstanding the Hybrid On-Chain and Off-Chain Model
sequencing, execution, receipts, and finality as a system storyRequest Lifecycle: Sequencing, Execution, and Finality
how the diamond contract layer fits into the public integration surfaceSmart Contract Architecture and Upgrade Boundaries
how the public docs connect safety controls to user protectionConsumer Protection Mechanisms
how signing, encryption, attestation, and checkpoints fit togetherCryptographic Security Model
pricing, funding, risk controls, and solvency as one mechanism setPrice Formation, Risk Controls, and Solvency
governance, compliance, and trusted-compute postureDecentralized Governance in Practice, Regulatory and Compliance Approach, and Trusted Hardware and Security Model
how institutional diligence should connect market structure, integration posture, and public-boundary limitsInstitutional Diligence, Market Structure, and Public Boundaries
confidential ordering changes strategy assumptionsFront-Running Prevention, Confidential Ordering, and Strategy Impact
why DerivaDEX uses a central limit order book in DeFiCentral Limit Order Book in DeFi
latency-sensitive design choices matter for builder workflowsPerformance Engineering for Strategy Builders
cluster durability and later settlement finality are kept separateConsensus, Checkpointing, and Finality

Core explanations

Boundary rule

Explanation pages tell you why the system is structured this way. If you need exact values, events, or rules, continue into Reference. If you need execution steps, continue into How-to Guides.
Last modified on April 13, 2026