WHY DEXTER
Dexter exists because perpetual trading usually forces one of two compromises: speed without clear control boundaries, or transparency without a usable trading surface.
#Why the venue is built this way
Dexter avoids that split by assigning different jobs to different layers.
The off-chain runtime owns execution coordination, risk transitions, funding, liquidation, and publication.
The contract layer owns collateral, withdrawal requests, treasury permissions, and settlement-critical references.
The gateway exposes that state through one venue surface instead of pushing raw runtime internals directly into the product.
This produces three practical differences.
First, the venue can keep execution responsive without pretending every action belongs on-chain.
Second, custody and protocol-owned balances stay easier to review because they are not mixed into runtime state.
Third, market posture is explicit: live, reduced, close-only, session-closed, and halted are treated as real operating states, not as interface decoration.
That is the point of Dexter.
The venue is not built around a simplified "everything is on-chain" story.
It is also not built around a black-box operator model.
It is built so speed, custody, and market-state discipline can coexist in one product.