Home / Crypto and prediction market exchanges
For exchanges
The dispute platform for high-volume exchanges
For crypto venues and US-regulated event markets, user disputes route through a notice and an informal period before arbitration, and that notice often lands as an email to a legal inbox. SpyroLex runs the whole function as cases your team controls: legal intelligence on the shape of your exposure, an AI mediator, a live dashboard, the complaint reports regulators ask for, mass-claim playbooks, and the window before arbitration itself. A named person decides every outcome, and every step is on the record.
Legal intelligence
Read your exposure before it becomes a filing wave
SpyroLex reads the shape of your dispute exposure across every open and past matter, so your team sees a filing wave forming while there is still room to act. It surfaces clusters by claim type and by claimant counsel, flags the early signatures of an organised mass-arbitration campaign, and benchmarks settlement ranges against comparable past cases. It is analysis of your own record, restricted per organisation, not legal advice and not a prediction: a named person reviews each finding and decides what to do.
- Emerging claim clusters, grouped by claim type and by claimant counsel.
- The early signs of an organised mass-filing campaign, surfaced inside the informal window.
- Open disputes ranked by escalation risk, benchmarked against comparable past cases.
The window before arbitration
The informal period in your terms, run as a case
Your terms already give you this period to settle a dispute. SpyroLex makes sure you use it, and that you can show you did.
- 1
The notice arrives
A notice sent to your legal inbox opens a case with the date it arrived, so the informal period is counted from the right day.
- 2
Checked against your terms
The case is read against the clause that applies and what your terms ask a notice to contain, with similar past cases beside it.
- 3
Worked inside the period
The deadline stays in view. The reply, and any offer, is drafted for a named person to approve or change.
- 4
Settled, or ready to go on
A settlement both sides accept, or the whole file, from notice to final offer, exported for counsel and for the arbitration your terms name.
This window is where the cost is decided. Under consumer arbitration rules the user pays a small fee, about 250 dollars, and the platform pays the rest: the filing, the case management and the arbitrator. A mass-arbitration wave costs thousands of dollars to initiate plus a non-refundable fee for every case. A dispute settled inside the window never reaches that bill.
The platform
Everything the dispute function needs, on one record
SpyroLex runs the full arc of a consumer dispute, so more resolve before they reach paid arbitration and every one that proceeds carries a complete record.
AI mediator
A second lens on every claim. SpyroLex reads both sides against your own terms and drafts a resolution for a named person to approve or change before anything is sent.
- Reads both sides against your own terms and drafts a resolution a named person approves or edits before it is sent.
- Takes the cases that repeat: stalled withdrawals, disputed trades, funds not released on time, event-market outcome queries.
- The model proposes only and cannot write to the record, and the whole step can be switched off.
Live dispute dashboard
One live view of every open dispute, by type, stage, outcome and age against the informal-period deadline your terms set running.
- Every open dispute by type, stage, outcome and age, the cases nearest their deadline shown first.
- Where claims cluster: held withdrawals, wrong-network transfers, frozen accounts, fee and delisting appeals, scam reports, contested outcomes.
- It reports on the record and does not change it, and any view can be switched off.
Regulator-ready complaint reports
The complaint record you already keep, assembled into the reports each regime asks for, reviewed by a named person before release.
- The EU record of every complaint and the measures taken, built from entries logged with the user and the time.
- UK complaint-handling and ombudsman reporting, grouped by type, exported in open formats.
- You stay the filer and the owner of what is reported, and SpyroLex produces the record it is built on.
Mass-claim playbooks
When hundreds of near-identical demands land at once, each opens as its own case on its own deadline and is answered from a template your team approved in advance.
- Approved templates for the demands that arrive in volume: delayed or failed withdrawals, missing funds, contested settlements.
- A wave of hundreds answered the same way and quickly, each case kept separate, each response signed by a named owner.
- Every response logged with the user and the time, in an append-only record, and any step can be switched off.
Prediction markets
Disputes over how a market resolved
On an event exchange the hardest disputes are about the outcome: whether the event happened, what the resolution source said, and whether the contract settled right. A US-regulated event exchange has to provide its participants with a way to resolve disputes, and an outcome review can have to be decided within a day.
SpyroLex runs the review as a case. The contract terms and the resolution source are on file, the evidence is attached as it comes in, and the committee or officer who decides records the determination with reasons and the time, in an append-only record. When a trader challenges the result, the record shows how it was reached.
Member discipline runs the same way: a panel, a hearing and an appeal, on your own rulebook.
Control and the record
A named person decides, and the record holds
Every function drafts for a person to approve or change, any function can be switched off, and the full security architecture goes to your team in writing before go-live.
Restricted per organisation
Each organisation sees only its own cases, and traffic is encrypted in transit.
The model has no write path
The model suggests and never writes the record. Anything that enters the file is entered by a named person.
An append-only record
Case actions are logged with the user and the time, in an append-only record, so later changes are detectable.
Yours to export
Export any case, or all of them, in open formats, as a term of your contract.
Hosting, residency, source code in escrow, and how your cases may be used, by any AI model or anyone else, are written into the contract.
Questions exchanges ask first
Does this replace the arbitration clause in our terms?
No. Your terms stay as they are. SpyroLex runs the informal step they already set out, and if a claim goes on to arbitration, the full file goes with it.
Does the AI mediator decide anything, or act as a neutral?
No. It reads the claim and the response and drafts a second view, a suggested framing or resolution, for a named person on your team to approve, change or discard. It is not a neutral, nothing it produces is binding, and the model has no way to write to the record. You can switch it off.
What does the live dispute dashboard show?
Every open claim in one view: its stage from the first notice through the informal period, the clock on each deadline, who holds it, and what is outstanding. Access is restricted per organisation, and every action is logged with the user and the time, in an append-only record.
What is legal intelligence, and does it predict how cases will go?
It reads across your own claim data to surface patterns: clusters of similar claims, a common defect driving complaints, and the early shape of a filing wave before it lands. It does not predict how an arbitrator will rule, and it decides nothing. It drafts the pattern for your team to act on, and like every function it can be switched off.
Can it handle a wave of near-identical notices?
Yes. Each notice keeps its own case and its own deadline, and notices of the same kind are answered from a template your team approved, so a wave of hundreds is handled the same way and quickly, with a named owner signing each response.
How should we think about the append-only record in a legal or regulatory dispute?
As a reliable operational record, not a legal guarantee. Each step is logged with the user and the time, in an append-only record, and later changes are detectable. The complaint reports are structured to the record each regime expects, but you remain the filer and the compliance owner, and how a court or regulator weighs any record is their decision.
Does it cover disputes over how an event contract resolved?
Yes. An outcome review runs as its own case, with the contract terms, the resolution source and the evidence on file, and the determination recorded with reasons and the time.
See alsoIn-house dispute teamsFinancial and insurance disputesWhat the record keeps
See the platform run on your own disputes
Book a working sessionBring your dispute clause and a few recent cases. Sessions run 45 minutes, and we reply within one business day.