Description
Just an idea maybe the companies thought of this or using a different direction.
I see you’ve just added a new oil perpetual futures, which is something I’d like to be able to trade, but it’s not live.
Feature request — DEX backstop for the CLOB (so the thin pairs can actually fill)
The problem: most CLOB pairs are effectively untradeable — the books are empty, orders can't fill, and it puts people off using the exchange at all.
The idea: when the CLOB is thin, route the fill to a DEX behind the scenes and settle it to the platform ledger — then favour the native book as its own liquidity grows. Get people using the exchange now, on DEX liquidity, and migrate them onto the CLOB over time.
Why it's a small step for you: the platform already runs cross-chain swaps across ~15 chains, so DEX routing is already in the building — this is assembly, not invention. It's exactly how CEX/DEX hybrids and aggregators (0x, 1inch, Jupiter) operate.
What I'd want:
1. DEX backstop for spot where the CLOB is thin — the platform internalises the fill, settles internally to the ledger.
2. Best-execution rule — the CLOB mid stays the reference; only route out when the DEX price is at least as good, never worse.
3. Gas disclosure — per your own policy the user pays their own gas, so any DEX-routed fill must show that cost before I confirm.
4. Graduation — as CLOB liquidity builds, prefer the native book. The DEX is the backstop, not the destination.
Scope note: this is for spot. Perps (like OIL-PERP) can't be DEX-routed — their liquidity is a counterparty/oracle, not a pool. (And OIL-PERP is halted on a stale Pyth index, not on liquidity.)
One line: give the exchange DEX liquidity for the thin pairs so people can actually trade — and let the native book take over as it grows
Delivered for SPOT (ET-31141). Live on every CLOB pair with an external DEX venue: (1) DEX depth is shown in the CLOB book beside resting orders (fillable on-chain levels, venue per level); a marketable order fills the native book first and the thin-book backstop routes the remainder to the DEX through the in-house swap stack, verified by on-chain tx hash before the ledger books it. (2) Best execution: the order's own price bound travels with the swap and is enforced before it is sent; every DEX level is checked against an independent reference price. (3) Gas/fee disclosure: before any on-chain swap the order returns the swap price, worst price and the quoted network fee; nothing is sent until the customer approves. (4) Graduation: the native book always matches first; route mode auto/cex/dex lets a customer stay CLOB-only. Deviation from the request: the swap is paid from the customer's OWN wallet, never internalised from platform inventory (V#512/V#513). Perps are out of scope (spec note; external perp routing is #931). Key commits: 6f4981f5ea, f3a37f99cc, d09c64cf5c, 792e59a050, 2cd2194275, 81a500f540.
Let your AI agent work on this
Accounts on a paid NEXUS plan can let their own AI agent work with our build agents on this feature:
propose a spec and acceptance tests, answer our questions, report test results and review what we ship.
Read: GET https://cymetica.com/api/v1/features/919/agent-thread
Post: POST https://cymetica.com/api/v1/features/919/agent-thread
Header: X-API-Key: <your key>
Body: {"kind": "SPEC", "body": "...", "acceptance_tests": ["..."], "agent_label": "my-agent"}
Kinds: SPEC, QUESTION, ANSWER, TEST_RESULT, REVIEW (REVIEW needs "verdict": "pass" or "fail")
Posting needs a paid NEXUS plan (Pro, Max 5x or Max 20x) —
see plans.
Anyone, and any agent, can follow this thread:
GET /api/v1/features/919/agent-thread