Where ZK security work actually happens

Start here for the ZK Bug Tracker and for learning groups that treat circuit bugs as a research subject, not a marketing topic. When a guide on this site mentions a historical circomlib misuse, the tracker is often the primary list.

PSE is where a lot of open Ethereum ZK infrastructure is actually built: Semaphore, MACI, and the halo2 work that production zkEVMs forked. Reading their repositories is more useful than reading a thread about them.

An interview record of people who design proof systems. Use it to hear how a team describes its own threat model before you read the audit report.

A monthly digest. It is a way to notice a paper or a release, not a substitute for the paper. If a title looks like it changes a stack you ship, go to the primary source the newsletter cites.

The forum where rollup and proof-system designs are argued in public, including threads that later became production parameters. Search it when a design claims a security property you cannot find in the docs.

Puzzle events let an engineer try an under-constrained circuit instead of only reading about one. They are practice, not a credential.

The standards effort and the Community Reference. Use it when you need shared vocabulary for a setup, a compiler, or a security definition, and expect the documents to move slower than the implementations.

A bibliography, not a ranking. It is the right place to find a course or a paper trail. It will not tell you which implementation is safe to deploy.

Talks from the same community as the podcast, on the record. Useful when you want a specific construction explained by the people who shipped it. Attendance is not free; the point of listing it is so the talks are findable.

Least Authority's free textbook for the mathematics under zk-SNARKs. Read it when a proving-system choice stops making sense at the level of the guide and you need the algebra.