We are evaluating adoption of zero-knowledge proofs (ZKP), which verify only the fact a service needs.
PROVE WHAT MATTERS. REVEAL NOTHING ELSE.
ZKP checks true or false without revealing identity.
Only a correct proof should pass.
Proof values must not be forged or bypassed.
The verifier should not be able to infer who the user is; we are evaluating adoption of this principle.
The point: your service gets the result without the raw data.
We are evaluating a structure in which IDs and personal identifiers stay on the user’s device.
We are evaluating an approach in which the verifier checks only that the proof is genuine.
In a ZKP design, the client receives just true or false — no personal data.
We are evaluating a design in which the device generates the proof and BBaton verifies it and returns the result.
In the design we are evaluating, proof material is created and kept on the device at first enrollment.
In the design we are evaluating, original IDs do not go to a server or the blockchain.
In the design we are evaluating, BBaton verifies only the device’s proof, and original data is not transmitted.
BBaton confirms conditions, not identities.
Adult status was all that was needed, yet personal data is exposed.
The service confirms what it needs without seeing the original data.