KEK DEX

KEK DEX is the execution interface within the KEK ecosystem.

It provides user-authorized, non-custodial trade execution for strategies that have already passed validation and testing.

KEK DEX does not generate strategies and does not control or modify strategy logic. It exists to execute validated decisions — not to make them.

Omnichain Execution Layer

KEK DEX is Omnichain and built on Orderly Network's decentralized exchange infrastructure layer. Orderly provides the underlying orderbook-based trading infrastructure and a shared liquidity layer that applications can build on.

What this page covers

The role of KEK DEX in the strategy lifecycle
How execution and custody boundaries are enforced
How KEK DEX integrates with the broader KEK system
What KEK DEX does — and does not — do

What KEK DEX is

KEK DEX is the execution surface for strategies that have been:

Generated (KEK Mix)
Backtested and optimized
Validated through paper trading
Explicitly authorized by the user for execution

Execution is optional. Validation is mandatory.

Role in the KEK system

KEK DEX exists at the final stage of the strategy lifecycle.

Its sole responsibility is execution — only after:

Strategy generation
Backtesting and optimization
Paper trading validation
Explicit user authorization

KEK DEX keeps execution separated from intelligence and validation so strategies cannot "skip the process."

Execution model

KEK DEX provides:

User-authorized execution

Trades occur only when explicitly authorized by the user.

KEK DEX does not execute autonomously.

Non-custodial infrastructure

KEK never takes custody of user assets or private keys.

Execution operates through user-controlled authorization and supported venue infrastructure.

Omnichain execution on Orderly Network

KEK DEX routes execution through Orderly Network's omnichain decentralized orderbook infrastructure, which is designed to support high-performance trading for builders without requiring them to build the matching engine or bootstrap liquidity themselves.

Third-party execution rails

Trades are executed through external infrastructure providers and exchange-layer rails (Orderly).

KEK does not intermediate custody and does not act as the counterparty.

Strategy isolation

KEK DEX executes validated strategy outputs but does not modify:

Strategy logic
Parameters
Risk rules
Validation artifacts

Execution is isolated from research and intelligence layers by design.

Custody & authorization boundaries

KEK DEX enforces strict boundaries:

KEK never has custody of user funds
KEK cannot initiate trades without authorization
KEK cannot access or store private keys
KEK cannot modify positions directly
Execution remains separated from intelligence and validation layers

Users retain full control over when and how execution occurs.

What KEK DEX does not do

KEK DEX does not:

Generate strategies
Evaluate performance
Override validation requirements
Store private keys
Execute trades autonomously
Modify strategy logic

It is an execution interface — not a decision engine.

Security & risk considerations

KEK DEX is designed to reduce operational and custody risk by:

Maintaining non-custodial execution boundaries
Separating execution from strategy generation and validation
Requiring explicit user authorization for trade execution
Relying on established exchange infrastructure (Orderly's orderbook and liquidity layer)

This structure minimizes single points of failure and prevents "execution-first" behavior.

How KEK DEX fits into the system

KEK DEX connects to the broader system as follows:

KEK Mix → Validation & Paper Trading → Monitoring & Refinement → KEK DEX (Optional Execution)

Execution remains downstream of validation at all times.

Why this matters

This design ensures that:

Capital is never exposed to untested strategies
Execution risk is minimized through strict authorization boundaries
Custody remains fully user-controlled
Responsibility boundaries are explicit and auditable

KEK DEX exists to execute decisions — not to make them.