Proof of humanity with zero-knowledge proofs
- Problem
- Bots drained airdrops and DAO votes; KYC was not an option.
- Built
- A feasibility assessment, then a proof-of-concept prototype.
- Scale
- Six trust levels, L0 to L5
A proof of concept is a working prototype that proves the one thing your product depends on, measured against an acceptance plan you sign before we build. We build it in two-week sprints with acceptance criteria you sign, and the prototype, code and documents are yours. A prototype is not a production launch: when it passes, the next step is the build.
| Proves | the one thing your product depends on |
|---|---|
| Measured | against the acceptance plan you sign |
| Process | two-week sprints, acceptance criteria you sign |
| Price | Fixed price per written scope |
| You own | prototype, code, documents |
What you get
How it runs
Fit
Use it when you
Skip it when
Proof
FAQ
No. It proves the one thing your product depends on. When it passes, the build is the next step, run by our R&D team on your product or with dedicated engineers.
Then the study did its job before you paid for a build. You keep the evidence and the options that remain.
You do. Results, code and documents go to your repositories.
No. We publish nothing from client research, and we name a client only where the client agreed.
Yes. We test radios and sensors in our own hardware lab, each against a written acceptance plan.
A proof of concept has a fixed price per written scope.
Next step
A 30 minute call with Mykhailo. You leave with a clear view of scope, risks and next step.
Mykhailo Tiutin
CTO, Vareger
