Extended Perps
Best for documented on-chain trading
How it rates
- Documentation published at a public address
- Deployed across 2 chains
- No audit report linked in the public dataset at this check
Each indicator scores 2, 1 or 0. A pillar is the points earned over the points available; the overall score is the weighted sum. Every source below is public — check any of them yourself.
- Not metIndependent audit published with a linked report
No audit report linked in the public protocol dataset at this check.
defillama.com/protocol/extended-perps - Not metAudit count recorded in an independent dataset
0 audit(s) recorded.
defillama.com/protocol/extended-perps - MetProtocol tracked by an independent analytics platform
Listed with published TVL and history.
defillama.com/protocol/extended-perps - Met
- MetApplication reachable at a public address
Reachable without an account at this check.
app.extended.exchange
- MetDocumentation published where fees are described
Documentation reachable for fee review.
docs.extended.exchange/ - Met
- MetIndependent dataset publishes protocol economics
TVL and change history published independently.
defillama.com/protocol/extended-perps - PartialFee model documented publicly
Documentation available; specific fee tiers not captured at this check.
docs.extended.exchange/ - Met
- MetTracked with published total value locked
TVL $123m at this check.
defillama.com/protocol/extended-perps - Met
- Met
- Not met
- MetListed on the independent dataset for over a year
Listing date recorded in the dataset.
defillama.com/protocol/extended-perps
- MetIndependent analytics page published
Public protocol page with history.
defillama.com/protocol/extended-perps - Not metAudit documentation linked publicly
No audit report linked at this check.
defillama.com/protocol/extended-perps - Met
- MetProtocol identity and chains disclosed
Chains and category published: Derivatives.
defillama.com/protocol/extended-perps - Met
- Met
- Met
- Met
- Not met
- Met
A perpetuals venue holding $123m across two chains, built on validity-proof infrastructure for high-throughput order matching.
Our assessment
Extended runs perpetual markets on validity-proof infrastructure designed for high-throughput matching, holding $123m across two chains. The architecture is the reason to consider it and the reason to read carefully.
Why the execution layer matters for perps
Perpetuals need frequent order updates, fast liquidations and low-latency funding calculations. On a chain where each action is a slow, costly transaction, the market either becomes expensive to make or unsafe to liquidate. Building on infrastructure designed for throughput addresses the real constraint rather than working around it.
Validity proofs versus optimistic settlement
A validity-proof system produces cryptographic proof that state transitions were computed correctly, rather than assuming correctness and allowing a challenge window. For a derivatives venue this matters: withdrawal finality without a multi-day challenge period changes how quickly a trader can exit, which is precisely what they want during stress.
Evidence gaps
No audit report was retrievable at a public address at this check, and several transparency indicators returned nothing. For a newer venue running novel infrastructure, published review would matter more than for an established protocol whose code has survived years of attack.
Who it suits
Extended fits traders who want fast on-chain perps with proof-based settlement and are comfortable with a newer protocol. Traders prioritising audited evidence should compare GMX, Avantis or Ostium.
How rivals compare
| Service | Score | Best for | |
|---|---|---|---|
| GMX V2 Perps | 9.3 | audited, multi-chain deployment | Read → |
Frequently asked
Does this score mean Extended Perps is safe to use?
No. It measures what an outsider can verify: linked audits, published documentation and independently recorded market data. Contract behaviour is not tested by us.
Where does the TVL figure come from?
An independent public analytics platform, queried at the verification date. Anyone can re-run the same query.
Why do some protocols score zero on audits?
Because no audit report is linked in the public dataset. It records what a user can reach, not a claim that no audit was ever performed.