Architecture

WheelX separates off-chain route discovery and transaction preparation from user-authorized on-chain execution. Users retain custody of their assets and approve or sign transactions through their own wallets.

This diagram is a conceptual overview of the EVM execution flow. Individual routes may use different external protocols and execution steps.

Execution Flow

1. Quote and route preparation: WheelX's API or SDK evaluates available routes and prepares the transaction data required for execution.
2. User authorization: The transaction is returned to the user's wallet for approval and signature.
3. On-chain execution: Published WheelX EVM components support token approvals, DEX routing, and native-asset receiving flows.
4. External protocol execution: DEX liquidity and cross-chain transfers are executed through integrated external protocols according to the selected route.

Published EVM Components

• ERC20 Approval Proxy: Supports ERC20 token approval within applicable execution flows.
• Dex Router: Executes authorized on-chain routing and DEX interactions.
• WheelX Native Token Receiver: Receives native assets within supported transaction flows.
• Maker and Dispatcher: Published EOA addresses used by the WheelX execution system.

Contract and EOA addresses are listed on the Deployment Addresses page.

Security Model

• Users retain custody and authorize transactions from their own wallets.
• Contract and execution addresses are published for independent verification.
• Execution is separated from off-chain quote and route preparation.
• Available security reviews are published under Contract Audit Reports.