Protocol Overview
At its core, ApStation transforms a user’s swap request into a dynamic execution route that pulls from the most competitive liquidity pools on the network. Every route is validated in real time based on live pool conditions, trading fees, and slippage constraints.
Aggregated Liquidity
ApStation actively scans and integrates the most liquid and efficient AMMs available on HyperEVM.
Routing sources are updated dynamically. As new DEX protocols or liquidity pools launch on HyperEVM, ApStation can automatically detect and route through them.
This ensures users always benefit from the widest liquidity coverage across both volatile and stable pools, without ever needing to know where liquidity lives.
Routing Algorithm
ApStation uses a custom-built routing engine, optimized for HyperEVM’s latency, composability, and trading fee structures.
Each route is evaluated using:
Per-pool fee models — Fees can vary by pool and DEX version. Our engine accounts for this precisely, even within multi-hop paths.
Real-time liquidity depth — The router prioritizes paths with low slippage and low price impact.
Slippage-aware quoting — Quotes include a minReceived check to protect users from sudden market movement.
Supported route types:
Single-hop (Token A → Token B)
Multi-hop (Token A → Token B → Token C) ApStation builds these paths dynamically when a direct swap would result in worse execution.
Slippage & Execution
ApStation includes on-chain slippage protection by default. Every trade includes a minimum acceptable output check — if the actual received amount falls below the threshold (due to price movement), the transaction is automatically reverted.
Slippage is customizable by the user
All routing logic is non-custodial — no tokens are held by ApStation at any point
Transactions are atomic and irreversible only after successful settlement
This ensures users are never overcharged or under-delivered on execution — even during volatile market conditions.
Execution Flow
User submits a swap request via the ApStation interface
The router scans available pools across integrated DEXs
It calculates all viable paths based on:
Token pair availability
Pool fees
Slippage estimates
Execution reliability
The best route is selected and shown to the user
Upon confirmation, the trade is sent on-chain for execution
If slippage is too high at execution time, the transaction fails gracefully with no token loss
Last updated