Dexter whitepaper
DEXTER IN ONE VIEW
Dexter is a hybrid perpetual venue.
Sections 1
Read 1 min
Whitepaper chapter
It keeps live execution off-chain, keeps custody and treasury-sensitive balances contract-bound, and keeps market posture explicit at the product layer.
| Domain | Dexter's approach |
|---|---|
| Trading coordination | One ordered runtime for execution, funding, liquidation, and publication |
| Custody and settlement | Contract-bound collateral, withdrawal requests, root history, and proof-gated exits |
| Market posture | Explicit states such as live, reduced, close-only, session-closed, and halted |
| Protocol value | Treasury, insurance reserves, and participation-linked records kept separate from user funds |
| Safety model | Narrow gateway boundaries, proof and challenge rails, and visible degraded states |
#The operating idea
To the user, Dexter should feel like one venue.
Underneath that surface, it should still be obvious where matching happens, where collateral lives, how prices are admitted, and how protocol-owned value is controlled.
That is the main design choice running through the whole product.
Speed is allowed where coordination needs speed.
Stricter boundaries stay in place where ownership, settlement, and protocol value need to remain reviewable.