explaingit

mimoo/awesome-zk-ai

Analysis updated 2026-05-18

29HTMLAudience · researcherComplexity · 1/5Setup · easy

TLDR

A curated knowledge base and website mapping cryptographic techniques for verifiable and private AI training and inference.

Mindmap

mindmap
  root((awesome-zk-ai))
    What it does
      SoK on trustworthy AI
      Generated reference site
      Papers with provenance
    Tech stack
      HTML
      Static site generator
    Use cases
      Pick a crypto technique
      Find who is building what
      Locate specific papers
    Audience
      Researchers
      ZK and crypto engineers

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Get oriented on which cryptographic technique fits a given AI verifiability or privacy problem.

USE CASE 2

Look up which companies and research groups are building in a specific corner of verifiable or private AI.

USE CASE 3

Find papers and provenance data for a specific claim type, like proving model accuracy or proving correct training.

What is it built with?

HTMLStatic Site

How does it compare?

mimoo/awesome-zk-aiactivetk/nandemo-syoumeidaniellockyer/terraform-log-viewer
Stars292929
LanguageHTMLHTMLHTML
Setup difficultyeasyeasyeasy
Complexity1/53/51/5
Audienceresearchergeneralops devops

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min

In plain English

This repository is a curated knowledge base about making AI systems trustworthy, built and maintained by the security research group zkSecurity. Despite the zk in its name, zero-knowledge proofs are just one of several techniques it covers, not the whole focus. The main way to browse it is a generated website with a dedicated page for every approach and every paper, where every number shown is pulled directly from the underlying data along with where that number came from. The project organizes the field around two questions: which phase of a model's life you are protecting, either when it is running (inference) or when it is being trained, and which property you actually want, either proof that something was done correctly (verifiability) or protection of the data and model while computation happens (privacy). Each of those four combinations is covered by a different set of cryptographic and non cryptographic techniques, including zero-knowledge proofs, secure multi-party computation, fully homomorphic encryption, and trusted hardware, each with very different cost and trust tradeoffs. Verifiability proves correctness to a third party but is roughly a thousand times more expensive computationally, while privacy hides data from a counterparty at the cost of heavy communication or encrypted computation. Within the verifiability side specifically, the project further splits things by what exactly is being proven, from the cheapest claim that a specific output came from a specific input, up through proving a model's accuracy on a dataset, and the most expensive claim that a model was trained correctly on specific data. There is also a landscape page mapping out which companies and research groups are actually building in each of these areas, noting that genuinely focused zkML companies are a small group, while most other activity comes from broader cryptography, encryption, or decentralized AI projects adding related language to their existing work.

Copy-paste prompts

Prompt 1
Explain the difference between proving inference and proving training in the awesome-zk-ai framework.
Prompt 2
Using the awesome-zk-ai landscape, list the main companies working on ZK based inference for AI models.
Prompt 3
Summarize the cost and trust tradeoffs between verifiability and privacy approaches in this project's map.
Prompt 4
Point me to papers in awesome-zk-ai about fully homomorphic encryption for private AI inference.

Frequently asked questions

What is awesome-zk-ai?

A curated knowledge base and website mapping cryptographic techniques for verifiable and private AI training and inference.

What language is awesome-zk-ai written in?

Mainly HTML. The stack also includes HTML, Static Site.

How hard is awesome-zk-ai to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is awesome-zk-ai for?

Mainly researcher.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.