lucasaschenbach/content-commitment-protocol

Welcome to Zertify!

AI developement is reaching it's tipping point with newest projects like Sora or Dall-E. This will even further accelerate the already exponential growth of one of the problems we are adressing. Deepfakes.

Our main goal is to deliver a seemless but secure solution for data signatures to Ethereum. We strongly focused on building a proof of concept that shows the feasibility of our architecture. For this, we chose to leverage zk-technology and proof folding to ensure safety and scalability.

The Architecture

At it's core, Zertify uses a commitment(C) that connects the signature to the signed piece of data.

The commitment is generated from the original piece of data(c₀). Along with the proof(𝞹) there will always be a record of the operations(phi) that have been performed with the piece of data. introducing one of our advanced safety feature.

Post-Compromise Security: If a key-pair is compromised, the original owner will be informed about any fraudulant on-chain activity and as soon as the key-pair is used further uses can be invalidated by a smart contract that has been issued.

Proof of Concept: Scalable Proofs

The main issue with previous solutions is theire lack of adaptibility. Huge amounts of data are beeing processed everyday and there is an increasing trend in fraudulent activities like deepfakeing or manipulation.

Our solution achieves high scalability by folding the operation records which lets it keep a constant size.

Updatability: The commitment should be infinitely updatable without invalidating any authorizations. Each update should only requiring the information available from the previous step. The update operations(functions) must be public.

Deployments

Base-Sepolia: 0x3e3fB8eee312F3c84B2d9baA15D0bE40d5dab255 Arbitrum-Sepolia: 0x3e3fB8eee312F3c84B2d9baA15D0bE40d5dab255 Sepolia: 0xBBB05E9C9755C1a6171077527e6675559683366c