# Marcus Tan, Head of Compliance & Risk at Meridian Exchange — read of Fraud Signal, June 15 2026

> 9 years in financial compliance, 4 in TradFi clearing, 5 running risk and AML at a Singapore-licensed crypto exchange with about 80 staff and a regulator that emails me personally.

## How I got here

We got a letter two weeks ago from MAS asking us to document our wash trading detection methodology. Our current setup is Chainalysis for chain analytics plus a homemade rules engine that one of our senior devs built in 2022 and is now undocumented because he left. I Googled "crypto exchange wash trading detection software" and this came up on page two, below Solidus Labs and above some GitHub repo. I clicked because the headline actually named the behavior I was looking for.

## What I clicked first

"Detect suspicious account behavior, wash trading patterns, and compliance violations before they become liability." Fine. That's what I need. I kept reading because it mentioned "pump-and-dump orchestration, front running, and wash trading" specifically, not just the usual "fraud" catch-all that tells me nothing. Then I hit "Used by emerging exchanges across Asia Pacific and EMEA" and I sat up a little. That's my region. Those are my peers.

## Where I paused

The stats block: "96% Suspicious pattern detection rate vs. manual audit / 47ms Average signal latency per transaction / 1.2M+ Transactions analyzed per hour."

I stopped there for maybe two minutes. No methodology. No link. No "in a study of X exchanges over Y months." Just numbers on a dark background. The 47ms number is oddly specific. Specific numbers usually mean either it's real and tested, or someone put effort into making it look real. I genuinely could not tell which.

Then I scrolled down and found this: "Honest disclosure: we don't have live customers on this idea yet."

## What I distrusted

That sentence undid the whole page for me. "Used by emerging exchanges across Asia Pacific and EMEA" is literally two screens above "we don't have live customers on this idea yet." That is not a tension. That is a contradiction. Either there are live users or there are not. Pick one.

The 96% detection rate also now has no grounding at all. Tested against what? A synthetic dataset? Their own benchmarks? The page implies a product in production. The footer says it is a strategy package someone else needs to go build.

Also: "Your regulators will notice." I do not want my compliance vendor speaking to my regulators in an ad headline. That is either overconfident or they do not understand how regulatory relationships work.

## What would convince me

A single named exchange, with a compliance officer willing to put their name next to a quote saying what specifically changed after deployment. Not revenue impact. Not "peace of mind." Something like: "We flagged 14 coordinated wash trading accounts in the first week that our rules engine missed, and here is the pattern it caught." That level of specificity. One real case. The APAC/EMEA geography mention could become credible if even one reference contact existed.

Also, if the 47ms latency stat came from a published benchmark with methodology I could read, I would take the whole page more seriously.

## What I'd ask in an email reply

1. The page says you have no live customers yet. Who ran the detection engine that produced the 96% and 47ms numbers, and against what data?

2. What does "deploy in production within 48 hours" actually mean in a licensed exchange context? We have change management requirements and a dev environment freeze window. Does 48 hours include integration with our order book, or is that a separate engagement?

3. The Fermi estimate shows Year-1 take-home of negative $83,800 and 1-in-11 odds of meaningful success. That's you scoring your own product's business viability. Why would I buy compliance infrastructure from a studio that rates its own idea's financial upside at 2 out of 10?

## Verdict: dismissive

The page is genuinely well-structured and names real problems I have. But the "no live customers" disclosure combined with the "Used by emerging exchanges" claim is disqualifying for a compliance purchase. I cannot put this in front of my CTO or our legal team. If someone builds this and it actually works, I would look at it again in 18 months.

---
*Memo by skeptic persona, generated 2026-06-15. Studio breaks own self-grading loop.*