Stop reading about ZK.
Build one proof that makes it click.
In one live session you see how private data can be checked without being exposed. You leave with a working age proof, the recording and enough understanding to judge the next ZK demo you see.
This started as a Rustmeet talk.
I showed this age-proof pipeline live at Rustmeet Kraków. People kept asking for the code, so I turned it into a workshop where you build it yourself.
You are not buying a faceless course. You build with me live, ask questions and keep the recording.
Check the fact without seeing the private data.
A service may need to know that someone is over 18. It does not need the birth date. Zero knowledge lets you prove the useful answer without handing over the private value behind it.
Three reasons it is worth your time
You are not here to collect more ZK words. You are here to learn the part AI will not check for you: whether the proof says the thing you think it says.
AI will not check soundness.
Claude can help write code. It will not tell you whether the proof proves the right claim. That is the part we inspect live.
Stop reading. Build one.
This is the jump from “I know the words” to “I built the first proof once”. You leave with a working age proof and a recording you can come back to.
Age checks are becoming product decisions.
Digital identity and selective disclosure are moving from papers into product requirements. This gives you a concrete mental model before you buy, build or recommend a solution.
You do not need a current project to justify the session. Building one small proof is already useful if ZK is on your radar.
Private data goes in, one claim comes out, and the verifier checks only that claim. That is the shape you build live.
Digital identity and age checks are becoming product conversations. This is the technical model, not legal advice.
You can open the code and use it
You leave with a small working proof, not just notes. The next day you can run it again, change the inputs and see exactly where the verifier accepts or rejects.
Know fast if this is for you
You do not need a math, blockchain or security background. You do need to be comfortable reading code during the workshop.
For you if
- You write software and can read Rust during a live session.
- ZK feels interesting, but still too abstract.
- You want the Rust/ZK fun, but also want to understand what age-check systems actually prove.
- You want one working build before going deeper.
Not for you if
- You want a passive webinar with no code.
- You want a math lecture from first principles.
- You cannot read Rust code at all yet.
Build once live, watch it again when you need it
Private data in, one answer out
You see how a system can check a claim without exposing the sensitive data behind it.
Mostly live build, not a lecture
You see the full path from setup to verifier, with a review segment where a circuit looks fine but proves the wrong thing.
Set up the repo
You get the code running locally, read the age-claim flow and see what stays private before touching the circuit.
Build the proof
You build the age proof path in halo2: witness, constraint, proof generation and verifier result.
Break and review
You review a circuit that compiles and still proves the wrong thing, then see how this proof flow can fit into web and iOS apps.
Adam
I write Rust, in blockchain since 2016. I do ZK in production and mentor developers who want to understand it beyond buzzwords.
I showed this pipeline at Rustmeet Kraków. The room kept asking for the code, so I turned it into a workshop where you build it yourself.
“The ZK Course helped me break through the wall of ZK moon math and complex terminology.”
“The course is well structured, guiding you through the basics of ZK and explaining the math in an understandable way, before moving on to more complex topics, debugging, and real-life use cases, all backed by plenty of examples.”
“Adam is a very good and patient teacher with production-grade ZK experience. I also really appreciated his responsiveness and willingness to help whenever I had questions.”
“In my experience, even the current models can still hallucinate once you get into the more advanced ZK topics. Since the field is still relatively new and very complex, it can be hard to tell whether an explanation is correct if you’re learning on your own.”
“Adam has an incredible mix of mathematical/cryptography and smart contract/software engineering knowledge.”
LinkedIn recommendation, architecture director“Adam was an amazing mentor and colleague and I certainly learned a lot from him.”
LinkedIn recommendation, Cardano innovation team colleague“The training is perfectly structured, and Adam’s knowledge and teaching skills make it the best source of blockchain technology information I’ve found.”
Earlier blockchain and cryptography training attendee“The training is practical, and the examples make it incredibly engaging. I believe it will be money well spent.”
Earlier blockchain and cryptography training attendeeFirst run price. Card or Apple Pay. No Stripe account needed. Company invoice available.
Book your seat
Sign-ups close 22 July 2026, or when the 10 seats sell out.
Card or Apple Pay. If the workshop does not reach 5 people, you get your money back. 14-day money-back guarantee.
Questions
Do I need to know math?
No. I explain only what you need to understand what is being checked and what stays hidden.
Do I have to code live in front of everyone?
No. You build at your own pace, or you just watch it later from the recording.
What do I need to build along live?
Rust and cargo on your machine, plus the editor you work in. You get setup instructions before the workshop.
What tools are used?
Rust and halo2. You do not need to know halo2 before the workshop.
How long do I have access to the materials?
12 months from purchase. That includes the recording, workshop code and materials.
Will this help me choose a ready-made Age Validator?
It is not a vendor comparison. But after building one small proof yourself, you know what to ask: what is signed, what stays private, what the proof says and what the verifier checks.
Is this about eIDAS 2.0?
Not directly. This is not legal advice. The workshop gives you the technical model behind selective disclosure: private data goes in, one claim comes out and the verifier checks that claim.
Do I need a Stripe account?
No. You pay by card or Apple Pay. Stripe is just the payment processor.
What if I want a refund?
14-day money-back guarantee. Sign-ups close 14 days before the workshop, so your two weeks to change your mind are always there.
Can I share or publish the code?
It is yours to use, reuse and build on in your own projects. Keep the workshop code itself off public repos.