zk proofs aren't just for rollups. the more interesting use case is verifiable exchange execution

most of the zk conversation in ethereum right now is about rollups. proving block validity, compressing state, bridging trustlessly. all important stuff.

but there's a use case that i think is more immediately impactful and barely anyone talks about: using zk proofs to make exchange matching engines verifiable.

here's the problem. every CLOB-style DEX runs a matching engine, and almost all of them are black boxes. your order goes in, a fill comes out, and you trust that the engine matched you fairly. you have no way to verify it. even the "decentralized" ones. the matching layer is the single biggest trust surface on any exchange and it's the one nobody can actually check.

the fix isn't moving matching fully on-chain. dydx v4 went that direction and you pay for it in throughput, because every fill has to go through consensus. for a CLOB that's a hard ceiling on what you can offer.

the more interesting path: keep matching off-chain for speed, but commit batched state transitions with validity proofs. the engine stays fast, but every batch of fills becomes cryptographically verifiable. no fill can be reordered, front-run, or fabricated without the proof failing. you get execution speed and provability without forcing a tradeoff between them.

this feels like it matters more for end users than zk rollups honestly. rollups prove that a block was valid. exchange proofs prove that your specific trade was matched correctly. one is infrastructure-level, the other is directly about your money.

curious why this isn't getting more attention in the ethereum zk community. is it a tooling problem? a "nobody's built it yet" problem? or does the market just not care enough about execution verifiability yet?