CenturionDEX documentation
One execution layer for concentrated liquidity
Inspect the route before signing. Set explicit bounds. Monitor settlement after execution.
- Route path and fee tier surfaced before signature
- Execution bounds enforced through deadline and minimum output
- Post-trade observability for settlement quality
Sell
1.00
Buy
2,847.50
Execution infrastructure that stays legible under load.
Every primitive — from the router to the observability layer — is designed for transparency, safety, and production-grade reliability.
Scope, plainly stated.
The protocol surface builders can integrate against today — documented contracts, SDKs, and primitives.
Proof in production
Route transparency, execution guardrails, and settlement telemetry are surfaced as first-class primitives.
Route details available before execution signature.
Trade, route, provide, and compose.
Four protocol surfaces. One execution layer. Each ships with documented contracts, predictable settlement, and a clean SDK.
Inspect every swap before signing
Route, fee tier, deadline, and minimum output — surfaced before signature.
Multi-hop routing across pools
Splits orders across fee tiers and intermediate hops to minimize slippage.
Provide liquidity, earn fees
Concentrated positions, range orders, fee tiers — primitives for LPs.
Composable contracts and SDK
TypeScript SDK, Solidity periphery, and codegen for every protocol entrypoint.
Built with familiar tools
Use cases
For app builders
Add swapping features to any app.
For protocol developers
Build onchain with CenturionDEX primitives.