Bilateral positions through solvers
SYMMIO describes a hybrid clearing and settlement protocol, rather than a central order book or liquidity pool. A trader sends an intent; a solver can accept the other side, and collateral and settlement are recorded on-chain. The core documentation lists perpetuals among supported derivative types, and the production Perps Hub page documents solver endpoints.
This establishes an execution layer with a perp capability. The same documentation also lists options and other derivative types, including possible instruments. A potential asset list is not a current market roster. The eligible perp cohort must be built from actual current symbols and executed positions, not from every product the architecture could support.
Sources: SYMMIO current overview ↗ · SYMMIO core concepts ↗ · SYMMIO Perps Hub endpoints ↗
Thena, Vibe and SwapBased are overlapping identities
SYMMIO’s current overview names Thena and Vibe among frontends using its derivatives service. Its frontend license grants SwapBased the right to make production use of the licensed work; that grant alone does not prove a live perp route. The operator names Thena and Vibe as users of its shared service, while their exact present-day market routes still require checking.
A branded trading screen can create a useful customer experience and may receive separate fees, but a fill settled in SYMMIO should appear once in a venue execution total. Adding each frontend provider row to the SYMMIO row would count shared positions more than once. Conversely, a frontend’s own volume might include any alternate route; that has to be tested before attributing every frontend fill to SYMMIO.
Sources: SYMMIO current overview ↗ · SYMMIO frontend use grants ↗
Protocol fees and token rights need their own ledger
The SYMMIO overview states a policy that settlement fees from subnets flow to SYMM stakers. That is a source claim about program terms. It is not a verified amount paid in any particular period or a basis to infer value per token. The article records the term without assigning holder flow.
A separate rights review would version the staking terms, identify eligible accounts and contracts, and compare promised routing with dated transfers or an audited report. Solver fees, affiliate fees, protocol settlement fees and trading notional must remain distinct.
Sources: SYMMIO current overview ↗
What a non-overlapping daily adapter needs
A meaningful daily series needs the deployed SYMMIO contracts, perp-only symbol IDs, filled or settled action types, UTC boundaries, quote units and revisions. It must deduplicate transactions by execution ID across affiliate frontends and account for solver versus trader sides of each bilateral position. Options and other derivative agreements should not silently enter a perp total.
Current official endpoints and architecture give a path for that work, but no completed 30-day venue-wide cohort has been reconciled here. The status is a verified shared perp execution product in the expansion inventory, not an approved comparable volume or open-interest ranking entry.
Sources: SYMMIO core concepts ↗ · SYMMIO Perps Hub endpoints ↗ · SYMMIO current overview ↗
What we monitor next
- Map current perpetual symbol IDs and deployed contracts to production solver fills.
- Check each affiliate for alternate routes and deduplicate shared execution IDs.
- Verify fee routing terms and observed distributions separately from trading activity.
Frequently asked questions
Compare the evidence
Related research
Source register
- SYMMIO current overview · checked 2026-10-07
- SYMMIO core concepts · checked 2026-10-07
- SYMMIO Perps Hub endpoints · checked 2026-10-07
- SYMMIO frontend use grants · checked 2026-10-07
Research revisions
- 2026-10-07 — Initial independently reviewed product and metric-scope audit.
AI-assisted research checked against cited sources. Facts, assumptions and interpretation are distinguished; this is not a financial audit or a recommendation tailored to you. Editorial standards.
Compare protocols →