Why regulation appears in the product surface
DerivaDEX does not treat regulation as a separate legal appendix detached from trading or integration behavior. The public docs surface makes visibility boundaries, restricted surfaces, and market-protection rules explicit because those controls change how users interact with the system.Governance plus regulated operations
DerivaDEX combines public governance with a regulated digital-asset operating posture. The DAO shapes protocol direction and parameter changes, while the operating surface still needs explicit public boundaries around KYC, restricted APIs, and user-protection controls. This is why the public docs separate:- public versus restricted API families
- risk and solvency reference pages versus broader explanations
- governance participation routes versus support requests for policy clarification
What this means in practice
The compliance posture changes how the docs are organized and how readers should interpret them:| Public docs pattern | Why it exists |
|---|---|
| explicit visibility labels on API families | not every technically real surface is a public-by-default integration contract |
| dedicated governance routes | governance participation is public and action-oriented, not buried inside generic policy text |
| public risk and solvency references | protections that materially affect traders and builders belong in the public contract surface |
| boundary-summary pages for restricted families | public docs should describe the existence and audience of restricted surfaces without pretending to publish private manuals |
Why this is not just a legal issue
Readers often treat compliance as though it belongs only to legal review. On DerivaDEX, that is too narrow.- traders care because market protections, liquidation posture, and access boundaries affect how the venue behaves
- builders care because visibility, auth, and restricted-surface boundaries affect what can be integrated publicly
- governance readers care because proposals and public decision making can change operational or market parameters
What this page does and does not answer
This page explains the public operating posture. It does not replace:- jurisdiction-specific legal advice
- private KYC or onboarding workflows
- unpublished policy manuals
- commercial or enterprise agreements
What this changes for readers
- Traders can see that risk controls and liquidation protections are part of the public product contract.
- Builders can see which surfaces are public, which are restricted, and which require additional operational context.
- Governance readers can follow proposals through the forum and DIP process without confusing discussion-stage ideas with live runtime guarantees.
How to read the public compliance story correctly
The most reliable reading order is:- start with the platform and trust model
- move to governance and regulated-operating-posture explanation pages
- move to factual references for limits, safeguards, and governance mechanics
- escalate only when the question depends on an unpublished surface or private process
Sources
- For Governance and Compliance for the current public governance and operating-context route
- Trading Safeties and Guards for public market-protection and execution-safety facts
- Margin Requirements for the capital and liquidation vocabulary used in governance and policy discussions
- Community Resources for the official governance forum, DIPs repository, and legacy-doc continuity boundaries
- Governance Forum for the live public discussion surface used before or alongside formal proposal work
- DIPs repository for mature governance specifications and implementation-linked proposal artifacts
- Digital Assets Supervision and Regulation in Bermuda for the statutory digital-asset regulatory framework administered by the Bermuda Monetary Authority