near.com
Research published; excluded from additive venue totals
Funding and privacy-oriented access to Hyperliquid. Exact RWA instruments remain to be verified.
Primary source ↗ · Read our analysis →Home / Coverage
COVERAGE / CHECKED 2026-09-22
What belongs in PerpsAtlas?
A map of perpetual venues, products and interfaces. Our eleven tracked profiles are a research universe, not an exhaustive list of every perp exchange.
The tracked universe
All eleven projects have a perp product. Some also provide other instruments. A verified RWA tag identifies documented traditional-market perps; an absent tag means this coverage review did not establish that scope, not that a venue can never offer it.
| Project | Classification | What we include and separate |
|---|---|---|
| Veranta / Avantis | Perpetual venue | Crypto and traditional-market perps. Avantis / Veranta is one tracked project, not two exchanges. Source ↗ |
| Ostium | Perpetual venue | Perpetual instruments spanning crypto and traditional assets. No ownership of the referenced asset is implied. Source ↗ |
| edgeX | Perpetual venue | Perpetual exchange. Use the pinned perp adapter; do not substitute EDGE-token futures on another exchange. Source ↗ |
| Extended | Perpetual venue | Perps across crypto, equities, FX, commodities and indices. Planned unified-margin products must not be counted as already live. Source ↗ |
| GRVT | Perpetual venue | The market-data specification identifies perpetual instruments. Keep strategies and other account balances separate from perp turnover. Source ↗ |
| Variational | Perp application within a derivatives protocol | Omni trades perps across crypto and traditional markets. Pro is a separate customized-derivatives settlement product. Source ↗ |
| SynFutures | Multi-product venue with perps | Perpetual futures qualify. Dated futures, spot aggregation and the separate RWA product must not be silently included in perp volume. Source ↗ |
| Paradex | Multi-product venue with perps | Perpetual futures qualify. Spot and options are separate instruments, including perpetual options where offered. Source ↗ |
| Reya | Perpetual venue | A trading venue with perp activity. Infrastructure and token announcements require dated checks; a roadmap is not proof of completed rollout. Source ↗ |
| Hyperliquid | Execution ecosystem with perps | Separate validator-operated perps, HIP-3 markets and spot. Frontends and builders can overlap with parent-venue totals. Source ↗ |
| Aster | Multi-product venue with perps | Perpetuals qualify, including traditional assets. Spot, Earn and distinct perp modes require separate metric and fee scopes. Source ↗ |
Expansion and interfaces
These are coverage candidates or separate interfaces, not additions to the ranking total. Ranking admission requires verified market identity, reproducible data, matching time windows and no double counting.
GMX
Scope confirmed; data onboarding next
Pool-based perps and swaps; perp activity needs its own adapter scope.
Primary source ↗Lighter
Scope confirmed; data onboarding next
Matching and liquidation design documented. Review current instrument metadata and metric definitions.
Primary source ↗dYdX
Scope confirmed; data onboarding next
Current chain and indexer scope must be pinned; do not merge legacy deployments without reconciliation.
Primary source ↗Jupiter Perps
Scope confirmed; data onboarding next
Separate the perp program from Jupiter swaps, lending and other products. Verify current market list.
Primary source ↗Orderly
Scope confirmed; aggregation policy required
Shared perp orderbooks can serve multiple frontends. Identify overlapping totals before ranking.
Primary source ↗RWA is an underlying market, not a different contract category
A gold perpetual belongs here. A spot-only tokenized gold claim does not enter the perp ranking. A perp on a network token does not turn that network into an exchange.
RWA perpetuals versus tokenized ownership →A recorded classification can change
We check the primary product description and then the metric adapter. Product descriptions alone do not certify an API aggregate. A new spot product, builder deployment or renamed token triggers a scope review before comparable totals change.
Ranking and data methodology →