Whitepaper: Zero-Knowledge Proof, Web Technologies & the Future of Private Communication

1. Introduction
2. What is Zero Knowledge Proof?
3. Difference from Other Security Methods
4. Applicability on Web Technologies
5. ZKP’s Approach to Privacy and Anonymity
6. CHAOS & VOID Algorithms
7. Use Case: NOCBY
8. Security Scenarios and Anonymity
9. Conclusion & Our Future Plans

1. Introduction

To put it simply, ZKP (Zero Knowledge Proof) relies on solving complex mathematical problems to ensure the security of stored data. To solve these problems and access the data, powerful machines and sophisticated algorithms are required. But can ZKP be implemented using web languages? What are the limitations of ZKP?

2. What is Zero Knowledge Proof?

Imagine you're playing a simple game with a friend. Your friend thinks of a number, and in order to win the game, you have to guess all 10 of their chosen numbers. These numbers could be one-digit, ten-digit, or even infinitely large — there’s no limit. But your chances to guess are limited. So, is it really possible to win?

This is how the complexity of data stored using ZKP can be illustrated. The data is stored using encryption methods with infinite possibilities, and when access is needed, the encrypted data must be decrypted accordingly.

3. Difference from Other Security Methods

Today, there are very powerful encryption methods available. The key difference between these and ZKP is that ZKP can have an infinite variety of algorithms for all data, while other methods are restricted by strict rules and boundaries (for reasons such as ease of management and scalability). In contrast to traditional methods, ZKP brings chaos and randomness. Other systems can often be reverse-engineered or rely on one-way algorithms.

This doesn’t mean traditional methods are bad — it simply highlights that ZKP has no limitations, making it far more advanced in terms of #dataprivacy and #datasecurity.

Returning to our earlier example: If it’s already nearly impossible to guess a single number, what happens when you’re asked to guess 100 more?

4. Applicability on Web Technologies

ZKP is actually a concept; there’s no fixed rule or boundary to its application. Its core principle is: The data can be known only by the owner, and the owner doesn't need to prove it, yet the data is still valid.

To give a human analogy: if someone says "I can multiply six-digit numbers in my head," you have to accept that statement as true without requiring them to demonstrate it. It's kind of like madness ?

5. ZKP’s Approach to Privacy and Anonymity

For simple tasks, it can be implemented and is already being used (like storing user passwords in a one-way encrypted format). But due to management and optimization problems, it's not widely feasible. In traditional web environments, even optimizing CRUD operations in databases is a challenge, so data security often becomes a secondary concern—leading to data breaches and hacks.

Another core principle of ZKP is "privacy." One of its most significant advantages is the anonymity it provides. If data is stored in an "unencrypted" form, it violates the ZKP concept. As mentioned before, only the owner should be able to access/know the data, and proving it shouldn't be required.

6. CHAOS & VOID Algorithms

Due to the traditional database mindset in web languages, implementing ZKP is challenging because all stored data needs to be encrypted, decrypted, and displayed—which introduces major optimization and management problems.

Our "CHAOS" and "VOID" algorithms, developed with the #Web3.0 mindset, do not use classical databases (in fact, they don’t have a traditional database at all). They generate their own storage systems, and even we—the developers—cannot view the raw form of the stored data. (More technical details will be shared in future updates.)

7. Use Case: NOCBY

In reality, we have more than just two, but so far, we've only completed testing for two algorithms suitable for Web 3.0. These algorithms follow different logic structures and are intended for completely different application areas. For example, in our soon-to-be-launched NOCBY app, we use the "Devdeed VOID" algorithm.

NOCBY differs from traditional chat applications by storing all data in encrypted form. Unlike standard E2E systems, it offers 100% anonymity and doesn't rely on traditional databases.

8. Security Scenarios and Anonymity

What does this offer?

Even if all the data from NOCBY were stolen, it couldn’t be read—because every piece of data is encrypted with different algorithms. Let’s say your data is stolen. The raw data cannot be viewed, as it's encrypted and can only be decrypted with your personal decoder.

Let’s suppose someone tries to decrypt a message like "How are you?" without your decoder:

• First, they won’t even know what they’re trying to decrypt.
• Even if they guess the message is "How are you?", the probability of cracking it would involve computations with 18+ digits of randomness.
• Let’s say they somehow cracked that message—can they now decrypt another message like "I’m fine"? NO.
• They’d have to repeat the 18+ digit probability computation again.
• Let’s imagine they somehow get incredibly lucky and decrypt both messages. Can they tell who you are? NO.

Why? Because our system is built on 100% anonymity. No one besides you and the people you interact with can know who you are—and isn't that how it should be?

9. Conclusion & Our Future Plans

In short, with our product built upon the ZKP concept, you can communicate securely and anonymously with high-level data protection.

Don’t forget to follow us to learn more about our ZKP-based storage concepts and to be among the first users!