Stryke review

Stryke (formerly Dopex) positions itself as options execution infrastructure — routing orders across concentrated-liquidity AMM, order book, and RFQ paths, including a stated Paradigm RFQ integration — rather than running a single standalone book the way Derive or Paradex does. That makes it a different kind of entry on this list: it’s less “should I trade options here” and more “this may be part of how your order gets filled somewhere else,” depending on how deeply the routing integrates with the venues it touches.

What Stryke actually is

Stryke grew out of Dopex, one of the earlier Arbitrum-native options AMM protocols. The 2026 positioning shifts the emphasis toward infrastructure: instead of asking liquidity providers to bootstrap yet another isolated pool, Stryke’s pitch is routing an incoming order to whichever execution venue — its own concentrated-liquidity AMM design, an order book, or an RFQ counterparty — offers the best fill, with Paradigm RFQ cited as one of the integrated paths. A rebate mechanism (referenced on CT as “$sykAsh,” tied to realized losses) is part of the incentive design; confirm current mechanics directly rather than relying on a cited figure.

Why “infra, not venue” matters for how you evaluate it

A framing that circulated in 2026 CT discussion stacks the category like this: Derive is demand, Paradex is UX, Paradigm is liquidity, and Stryke is infrastructure. Whether or not you buy that exact stack, it’s a useful lens — Stryke’s value proposition depends on how much real order flow actually routes through it, not on a standalone TVL or OI figure the way a single-venue CLOB’s does. independent verification of current routed volume.

What Stryke does well—and what remains uncertain

• Pro: a genuinely different value proposition from a single-venue book — if the routing works as pitched, it could reduce fragmented liquidity across venue types rather than adding another isolated pool.
• Pro: builds on a multi-year Dopex lineage rather than starting from zero, with real operating history on Arbitrum specifically.
• Con: harder to evaluate than a standalone venue — its usefulness depends on integration depth and actual routed volume, neither of which we could independently verify here.
• Con: expansion plans (additional chains, additional integrations) are, as of this writing, plans rather than confirmed live deployments — check current status directly.
• Con: Stryke’s current audit status and live fee/rebate schedule remain unresolved — confirm both before relying on it.

Who should choose Stryke

Traders and builders more interested in execution routing and infra-level integration than in picking a single venue to trade on directly, and anyone evaluating whether Paradigm RFQ liquidity is reachable through multiple onchain paths, not just Paradex.

Risks specific to Stryke

Beyond standard options risk (see options vs perps), Stryke’s routing model adds a layer of dependency on the health and liquidity of the venues it routes into — if routed venues themselves are thin or a rebate program’s incentive cliff hits, the practical benefit of the routing layer can be smaller than the pitch suggests. As with any infra-layer protocol, confirm which specific execution paths are actually live and liquid today rather than which are listed as integrated.

What to verify before using Stryke

Stryke’s documented identity is an execution-routing layer with Dopex lineage; the uncertain part is how much live flow it routes and through which integrations. Verify current chain support, active execution paths, rebate conditions, and audit coverage in Stryke’s own documentation before treating a routing relationship or RFQ reference as evidence of usable liquidity.