Skip to main content

Start here for governance, safety, and compliance context

Use this route when you need to understand how DerivaDEX explains governance, trust boundaries, and restricted operational surfaces without starting from trader or builder workflows.

What this route answers first

This page is the public explanation entrypoint for readers asking questions such as:
  • how DerivaDEX describes governance and operational accountability publicly
  • where the public docs surface explains market protections and solvency controls
  • which operational or compliance-oriented surfaces are intentionally not published as full public manuals
It is especially useful when you are reviewing the platform as:
  • a governance participant
  • an institutional diligence reader
  • a legal or compliance reviewer working from public materials only
  • a partner trying to understand which deeper surfaces are public versus restricted
It is not a legal policy page and it is not a private operator runbook. It is the route that explains how the public documentation is organized for governance, trust, and compliance-oriented readers.

Public posture at a glance

DerivaDEX presents governance, safety, and operating posture across several public docs layers rather than one monolithic policy document:
  • explanation pages answer why the system is structured the way it is
  • reference pages answer what controls, limits, and protocol facts are publicly documented
  • tutorial and how-to pages cover the governance actions that public readers can actually perform
That split is deliberate. Governance and compliance readers often need both public rationale and concrete controls, but those belong in different documentation quadrants.

The public trust story in three layers

LayerWhat it answersBest route type
Platform and trust modelWhat DerivaDEX is, why it is structured this way, and where its trust boundaries stopGetting Started and Explanation
Concrete controls and governance mechanicsWhat limits, thresholds, addresses, voting mechanics, and safety rules are publicly documentedReference
Public actions a reader can actually takeHow to vote, delegate, propose, post, or escalate through public channelsTutorials and How-to Guides

Choose the right next route

If you need to understand…Best next route
the public operating model firstWhat is DerivaDEX?
why governance, trusted compute, and safety boundaries existExplanation routes, especially Decentralized Governance in Practice, Regulatory and Compliance Approach, and Trusted Hardware and Security Model
exact public controls, limits, and contract surfacesReference routes such as Trading Safeties and Guards and Smart Contract Addresses and Core Contract Reference
one governance actionthe relevant governance tutorial or how-to guide
official discussion or clarification channelsCommunity Resources and Support Channels
institutional diligence routing rather than one governance actionInstitutional Resources
  1. Read What is DerivaDEX? for the public overview and operating posture.
  2. Read How DerivaDEX Works, Why DerivaDEX Is Architected Differently, Decentralized Governance in Practice, and Regulatory and Compliance Approach for system and policy context.
  3. Read Trading Safeties and Guards, Margin Requirements, Governance Process and Public Decision Reference, Governance Mechanics and Voting Threshold Reference, DDX Token Specifications, and Smart Contract Addresses and Core Contract Reference for concrete controls and governance-relevant protocol facts.
  4. Use Your First DAO Proposal, Cast Your First Governance Vote, How to Submit a Governance Proposal, How to Create a Governance Forum Post, How to Delegate Voting Power, How to Participate in Security Council Elections, and How to Propose New Asset Listings for common governance actions.
  5. Use Community Resources and Support Channels when you need the official discussion surfaces or a documentation clarification.

Public evidence anchors

TopicPublic anchorWhy it belongs in a governance/compliance read
governance discussion and proposal reviewGovernance ForumPublic forum for proposal discussion and governance context
mature proposal and implementation historyDIPs repositoryHistorical decision and implementation trail
regulated operating-context framingDigital Assets Supervision and Regulation in BermudaPublic operating-context anchor for the Bermuda regime referenced in the docs

What public docs intentionally do not publish

The public docs are not trying to masquerade as a private diligence room. They intentionally do not publish:
  • private operator procedures
  • private compliance workflows or unpublished KYC manuals
  • private market-maker terms, support arrangements, or diligence packs
  • legal advice or venue-specific legal opinions

Public boundaries that matter

The public docs make three important boundary distinctions:
  1. Governance participation is public and user-facing. Proposal, voting, delegation, and public discussion flows are documented as public tutorials and how-to guides.
  2. Safety and solvency controls are public reference material. Margin rules, liquidation posture, price protections, and system safeguards are documented as factual reference because they affect user trust and integration correctness.
  3. Restricted operational and compliance surfaces are not silently treated as public APIs. When a surface is operator-oriented, compliance-oriented, or product-specific, the public docs summarize its boundary and source ownership instead of pretending that every deeper contract is publicly published.

Restricted-surface taxonomy

Surface familyPublic posture
Operator / Client RequestBoundary-summary only
KYC OperatorBoundary-summary only
Copy Trading REST and RealtimeProduct-specific boundary-summary only

How to read the public trust story correctly

If you need to evaluate DerivaDEX as a governed and safety-conscious system, read the docs in this sequence:
  • start with the public platform overview to understand the operating model
  • move to explanation pages to understand why governance, safety controls, and trusted-compute boundaries exist
  • move to reference pages for the exact public facts that those explanations rely on
That order matters because the public docs separate rationale from mechanism instead of collapsing everything into one policy page.

Reader-specific next steps

Licensing and policy questions

This public docs surface does not currently publish a standalone licensing policy page or private legal guidance. Use this route for documented governance and safety context. If a published docs statement about governance, licensing posture, or restricted surfaces appears incomplete or inconsistent, use Support Channels to request a documentation clarification.

Boundary rule

Use this page for public governance/compliance orientation, not as a legal opinion, internal operator policy, or private compliance runbook.
Last modified on April 13, 2026