Zero-knowledge proof (ZKP) verifies only the fact required by a service instead of requiring users to submit their full personal information. BBATON applies this principle to an anonymous verification structure so only the required verification result, such as whether a user is an adult, is delivered.
Prove what matters.
Reveal nothing else.
As personal-data governance becomes more important, verification systems are being designed to confirm whether a condition is satisfied without revealing a user's identity. ZKP verifies only true or false and is structured so the rest of the data remains hidden.
If a claim is true, a valid proof must pass verification. In practice, this means legitimate users should be able to prove required conditions reliably.
A proof value must not be manipulated, forged, or used to deceive the verifier through a bypass. The structure is designed so user data cannot be arbitrarily altered or circumvented through blockchain-based controls.
The verifier must not obtain any information that could identify the user beyond whether the proof value is valid. BBATON is also designed so that it cannot know who the user is.
In production, the user's personal information, the proof generated on the device, and the service that interprets the result should remain separated. The key is that the service can receive only the result it needs without access to raw source data.
Identity documents, birth date values, and personal identifiers remain on the user's device or within a user-controlled area. BBATON is also designed not to collect the user's personal information.
A request for a condition such as adult status is sent to the user's device, and the device generates a proof and sends it to BBATON. BBATON verifies only whether that proof is valid.
The proof value verified by BBATON is returned to the client. That proof does not contain the user's personal information; it contains only whether the requested verification is true or false.
BBATON does not handle personal information. The client sends a verification request, the device generates the proof required for that request, and BBATON only verifies and returns the result.
At initial registration, the required document information is read and converted into personal information and verification materials that remain only on the user device.
Original identity documents and source values are not uploaded to a central server or blockchain. All information that could identify the user remains in the user's possession.
When the client requests a condition, the user device creates a proof from local information and BBATON verifies it. Raw identity information is not transmitted.
BBATON is not an identity-verification service. It does not verify who a user is; it verifies whether a specific condition is satisfied.
What is actually needed is only whether the user is an adult, yet unnecessary personal information is exposed together with the result. The purpose of collection and the scope of exposed information do not match.
The service checks only the result required by policy and does not know original values such as the name, address, or birth date. The verification purpose and the collected information align.