Know what is behind a route.
HyperMatch selects between execution venues. Each route needs an explicit market model, verified permissions and a working exit. Integration stages are listed below.
Current directory
Hyperliquid
Public BTC and ETH order-book data is connected. HyperCore testnet is the first execution target; signed order execution still requires funded end-to-end verification.
Official APIHIP-3 markets
The console reads the xyz:GOLD order book for evaluation. A gold symbol does not establish equivalence to MT5 XAUUSD. Contract units, oracle, trading hours, collateral and deployer rules must be checked separately.
HIP-3 specificationgTrade
A candidate for FX and higher-leverage routes. On 19 September 2026, official parameters showed up to 1,000x on selected major FX pairs and 250x on XAU/USD gold. Session and news restrictions can lower those limits. Execution uses an oracle and collateral vaults. The workspace includes a synthetic paper model; no live gTrade adapter is enabled.
Official pairs & leverageGMX
A candidate for a separate adapter. Pool capacity, oracle execution and order creation/fill stages need their own checks. No GMX account connection or trading connector is enabled here.
Official SDKdYdX
A separate chain and signing model. Permissioned keys are a basis for future integration, subject to market coverage and account-mode validation. The adapter is not enabled.
Permissioned keysVenue availability and market specifications can change. A listing is not an approved route or a promise of execution.
How routes qualify
- Match the actual contract: source units, destination quantity, quote direction and trading session.
- Confirm a permitted, funded destination account and fresh market data.
- Compare expected execution, fees, funding and exit cost at the intended size.
- Reject routes with unknown permissions, insufficient capacity or an unverified exit.
Collateral is not automatically shared across venues. Each eligible destination needs its own available margin. A route change applies to new decisions; existing positions remain at their original venue.
Independent & partner venues
The adapter design supports established protocols and independently operated venues under the same acceptance standard. Market data, fees, execution evidence, account permissions and withdrawal rules must be inspectable.
HyperMatch supports persistent principal paper accounts with positions, margin, realized P&L and a dealer ledger. Administrators distinguish agency, principal and hybrid configurations. Each published venue identifies its counterparty, pricing and custody terms. Real customer deposits and principal live trading are not enabled.