How Extended's hybrid architecture works
Extended documents offchain matching with onchain Starknet validation and settlement. It also describes checks on price limits, account health and liquidations. The existence of offchain matching does not imply unlimited discretion over every fill; the documented onchain constraints matter.
Our interpretation separates ordering and availability from transaction validity and withdrawal behavior. A responsive interface does not prove that every dependency will remain available under stress. Equally, a matching outage would not by itself prove that settled account balances are invalid. These are different tests.
Team background and funding: primary versus secondary sourcing
The official team page describes the CEO's previous role leading crypto operations at Revolut and the CTO's exchange-building experience. These are project-supplied biographies, not independently audited credentials.
This edition has not reconciled a primary financing announcement for the reported strategic round. An investor's own announcement would be primary evidence too; it does not have to be hosted by Extended. We omit an unverified funding total from the thesis rather than treating a missing link as a negative finding about the company.
Sources: Extended Docs: Team ↗
No verified protocol token
As of this edition, no verified protocol-token launch or unlock calendar exists for Extended. The platform's XVS vault receipts are a distinct product mechanism and should not be confused with a protocol governance or value-accrual token. This means there is currently no token-based valuation angle to analyze — Extended today is a product-usage story, not a token-supply story.
Any future token, if launched, would need its own primary-sourced supply schedule, unlock calendar and value-accrual mechanism before an investor could responsibly model dilution or holder economics.
Sources: Extended Docs (root) ↗
Activity metrics: a rare case of fresher venue-level data
This edition freezes observations from the 22 September collection; current profile values can change independently. Rolling 24-hour volume: $596,325,312.65 (fetched 2026-09-22T13:21:57Z; source time unavailable; fetched). Open interest: $198,947,434.61 (fetched 2026-09-22T13:22:00Z; source time unavailable; fetched). Tvl: $120,238,887.00 (source time 2026-09-22T12:27:47Z; fresh). 30-day fees: $1,703,510.00 (fetched 2026-09-22T13:22:03Z; source time unavailable; fetched).
These are separately scoped measurements, not a synchronized financial statement. The source links identify the exact adapter or venue endpoint. Dated manual 7-day and 30-day volumes on the profile are not used here to infer a current turnover rate.
The native market aggregate excludes spot and includes both active and reduce-only perpetual markets. This prevents outstanding positions from disappearing merely because a market no longer accepts additional risk. The venue response supplies no aggregate observation timestamp, so we show fetch time instead.
Sources: Public source: rolling 24-hour volume ↗ · Public source: open interest ↗ · Public source: TVL ↗ · Public source: 30-day fees ↗
Execution and settlement risk considerations
The offchain-matching, Starknet-settlement split means an investor should separately assess two things: Extended's own infrastructure reliability and censorship-resistance for matching, and Starknet's proof-generation and finality guarantees for settlement. A failure or degradation in either layer could affect trader outcomes differently — a matching-layer issue might mean unfair fills or downtime, while a settlement-layer issue could affect withdrawal timing or collateral finality.
What would strengthen or weaken this thesis
The product case strengthens when comparable periods show retained users, usable depth and growing fee generation without a deterioration in execution. Transparent reporting of matching and settlement incidents would improve our ability to evaluate resilience.
It weakens with recurring execution problems or a material gap between documented protections and observable behavior. A future token should be analysed only after its supply and economic rights are defined. Missing aggregator revenue coverage alone is not proof that the business retains no revenue.
What we monitor next
- Track execution, availability and withdrawal behavior separately from settlement guarantees.
- Reconcile funding announcements with primary company and investor records.
- Compare consistent fee and revenue definitions across periods, alongside retained demand.
Frequently asked questions
Does Extended have a token?
No verified protocol-token launch or unlock calendar exists as of this edition. XVS vault receipts are a separate product mechanism, not a governance token.
How is Extended's architecture different from a typical perp DEX?
Order matching happens offchain for speed, while validation and settlement occur on Starknet. This creates two separate risk layers — matching-infrastructure risk and Starknet settlement risk — that should be assessed independently.
Is the reported $12.5 million eToro round confirmed by Extended itself?
A primary financing announcement has not been reconciled in this edition. A company or investor announcement would both count as primary evidence; a funding total is not used in this analysis.
Compare the evidence
Open the comparison desk →Source register
- Extended Docs: Technical Architecture · checked 2026-09-22
- Extended Docs: Team · checked 2026-09-22
- Extended Docs (root) · checked 2026-09-22
- Public source: rolling 24-hour volume · checked 2026-09-22
- Public source: open interest · checked 2026-09-22
- Public source: TVL · checked 2026-09-22
- Public source: 30-day fees · checked 2026-09-22
Research revisions
- 2026-09-22 — Initial edition after independent source, calculation and inference review.
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.
View current metrics →