Why consumer protection is a system property
Consumer protection on DerivaDEX is not one isolated feature. It is the combined effect of:- pre-trade validation
- margin and liquidation controls
- mark-price and price-deviation guards
- insurance-fund and ADL backstops
- public governance and support visibility
Why this page is not the same as a policy page
This page explains the protection model at a system level. It is not a promise that trading losses cannot occur, and it is not a replacement for the factual reference pages that define the actual guards, thresholds, and stressed-path behaviors.The first protection layer: stop bad requests early
The platform rejects unsupported products, malformed order shapes, unsafe notional sizes, and clearly invalid signing or account-state requests before they become live exchange state. This is the first consumer-protection layer because it prevents many avoidable failures from turning into open market risk.The second protection layer: constrain live trading risk
Once a request is admissible, other controls still matter:- mark-price based margining determines when a position becomes unsafe
- taker-deviation guards prevent executions beyond bounded market context
- liquidation handling cancels pending orders and moves unsafe accounts into a controlled unwind path
The third protection layer: solvency backstops and bounded failure handling
Insurance-fund participation and ADL exist because real markets can exceed ordinary book liquidity or risk assumptions. Public docs need to explain that these are backstops, not ordinary user workflows. They are part of consumer protection because they address what happens after the normal risk controls have already been stressed.Protection also depends on public visibility
Consumer protection is not only about runtime code paths. It also depends on readers being able to see:- which rules govern trading and liquidation
- which surfaces are public versus restricted
- where governance discussion and change proposals happen
- how to escalate when the docs do not explain an observed behavior
What consumer protection does not mean
Consumer protection does not mean:- every trade is profitable
- liquidation can never occur
- every API or operational surface is public
- support or governance discussion replaces the protocol’s actual risk mechanics
Sources
- Trading Safeties and Guards for the main validation, execution-guard, liquidation, ADL, and guarantee facts
- Margin Requirements for liquidation-threshold and solvency vocabulary
- Price Feeds and Mark Price Inputs for mark-price and price-input posture
- Regulatory and Compliance Approach for the public-boundary and operating-posture context
- Support Channels for the escalation path when a public behavior still needs clarification