Unique and Innovative Features

It has been our mission to bring the ZKP technology to the world of Web2 development environment as a software development framework with the main focus to mitigate the PII leak issues.

Why Is OZKi Unique?

OZKi is unique because currently, it is the only stand-alone developer's toolkit for the traditional Web2 development which supports ZKP-based authorization flows without requiring the use of blockchain.

In its current form, OZKi is a stand-alone developer's framework, however it can also be used as the building block to build service-based authorization flow such as Proof-as-A-Service.

Innovative Features

We designed OZKi to support the following features in mind:

Proof-based Authorization

OZKi enables the proof-based authorization models. The proof-based authorization flow can be used to replace the traditional sign-in process where:

• The user (prover) does not need to reveal his/her PII to the server, thus protecting the PII.

• The server (verifier) can reliably verify if the user does have PII attributes which meet certain requirements or constraints.

With this model, it is possible to design a system based on the concept of ID-less server design where the server does not need to refer nor store any or some of the PII. The complete or partial elimination of the PII being stored on the server is a very effective way to mitigate the PII leak issues.

Additional Security Layer

In addition, OZKi Framework also adds security layer to address the two problems which exist in the core ZKP module:

• Secure end-to-end PII retrieval from the source The user will not be able to tamper with the retrieved PII as the oracle signs the data and the proof function always verifies the validity of the signature at the beginning of the function.

• Mitigation of proof replay attack OZKi enforces the concept of proof expiration whose period is configurable by the user and the default is 5 minutes. The proof must be used exactly once before it expires. An expired proof will fail the verification process. The OZKi proof verifier also can detect attempts to replay the proof while the proof has not expired.

Minimal ZKP Exposure

OZKi is also designed to abstract away the ZKP-specific artifacts from the web developers. The developers do still need to program the proof function in circom, but many of the zkp moving parts are hidden behind the typescript interfaces. Users can write their own custom proof functions and interact with them in the javascript/typescript programming environment by subclassing the ProofGenerator or ProofVerifier class.