Architecture
Offchain route discovery, block-consistent pricing and onchain settlement.
The request flow
Background quoter checks qualify local models and quarantine mismatches. Unsupported state uses verified RPC recovery. The API returns unsigned data to the wallet.
The browser consumes the same versioned API exposed to integrators. In fast mode, a background worker publishes immutable, block-consistent pool snapshots. Quotes use exact integer math, cached topology and shared gas pricing without synchronous blockchain RPC. Cold or unsupported markets use bounded verified RPC recovery. The swap builder then checks the configured executor and preflights the transaction from the actual sender when allowance permits.
Local RPC and archive state
The API and primary HyperEVM light-node RPC are colocated in Tokyo. The backend uses a loopback connection for the primary RPC. A separately configured archive provider supplies verified historical state when the primary node cannot. These private runtime endpoints and credentials are not sent to the frontend.
Low network latency does not imply historical-state support. Every pinned state read checks its actual EVM block context; quotes also enforce block hash and freshness. A response that silently returns latest state for an older block is rejected. If both providers cannot satisfy the required snapshot, Path returns an error.
Fast adapters cover all six DEXes on the core HYPE/WHYPE, USDC and USD₮0 graph, including the qualified concentrated pools and HyperSwap/Ramses volatile constant-product pools. Other pool types use verified recovery. Heads and fees are read each block; liquidity events invalidate tick caches, with periodic authoritative reconciliation. Missing ticks are never approximated. Background samples compare exact local outputs with onchain quoters across blocks and amounts; mismatches quarantine the adapter and invalidate its quotes. Verified recovery retains synchronous winner checks. Full sender-specific simulation always remains part of swap building.
HyperEVM versus HyperCore
A future HyperCore integration would need its own quote, account, transfer and settlement model. It cannot be enabled by adding a DEX factory address. Current source discovery and DexScreener filtering explicitly target HyperEVM.
Data and signing boundaries
| Component | Responsibility |
|---|---|
| Web app / Reown | Token selection, review and user wallet connection on chain 999. |
| Fastify API | Discovery, quote search, unsigned transaction building and public reads. |
| PathExecutor | Designed to execute approved routes with onchain minimum and callback checks. |
| Persistent data | JSON pool inventory and SQLite activity/order event journals when configured. |
| Path Limit v2 resolver | Separate private process: pool checkpoints, order scans, full-size routes, simulation and signing within gas budgets. |
| PathMarketReader | Qualified onchain pool history; no mandatory external oracle feed. |
Market swaps are signed by the user wallet. Limit orders use onchain escrow and a separate keeper workflow. The deployer key is not part of the API runtime or a frontend bundle.