I've been thinking about ZKML overhead for the past few days, and one thing stands out: it doesn't just affect performance—it determines which AI workloads actually make sense to verify with it.

The core tradeoff is straightforward. ZKML can require roughly 1,000–10,000× more computation than standard inference. OpenGradient doesn't hide this reality. Instead, it recommends ZKML for smaller, high-stakes models, while larger generative models are generally better suited to TEE-based verification or conventional inference.

As model complexity grows, so does the proving cost. That means today's largest LLMs are simply not an ideal fit for ZKML.

Small models. Strong guarantees.

What often gets overlooked is that this isn't unique to OpenGradient—it's a broader limitation of current zero-knowledge proof technology. A compact risk model with hundreds of parameters is a practical ZKML candidate today. A 70B-parameter LLM is not, regardless of the infrastructure behind it.

I actually appreciate that OpenGradient doesn't market ZKML as a one-size-fits-all solution just because it offers the strongest cryptographic guarantees. Choosing the right verification method for the right workload feels like the more honest engineering approach.

That said, the limitation is very real. Many of the high-stakes AI applications people most want to verify—especially large-scale reasoning models—still rely on TEE attestation rather than full ZKML proofs.

I've seen people insist on using the "most secure" option simply because it sounded better on paper, even when a more practical solution was the better engineering choice.

The question I'm still curious about is this:

As zero-knowledge proof systems improve, how much could the current overhead be reduced? And does OpenGradient have a roadmap or timeline for making ZKML practical for increasingly larger models?

@OpenGradient

$OPG #OPG #ZKML #AI #Crypto #Blockchain #VerifiableAI