Zk with HTML/CSS

There are many ideas and applications for combining Zero Knowledge Proof and HTML/CSS. Some ideas are suggested below.These ideas would be implemented in WASM.

Privacy-preserving web forms:
Zero-knowledge proofs can be used to verify the legitimacy of data input into web forms. The user is required to enter personal information, but its validity is verified without the information being transmitted to the web server. This allows the legitimacy of the information to be verified while still protecting privacy.

Anonymous authentication systems:
Zero-knowledge proof can be used to prove that a user meets certain criteria. For example, it can verify that the user is over 18 years of age or has certain attributes. However, individual user information is not revealed and anonymity is preserved.

Visual Confidentiality of Websites:
Using HTML/CSS, visual information can be incorporated into websites. Using zero-knowledge proofs, it can be verified that the certifier knows the visual information. For example, you could create a website that verifies that the certifier knows a particular password or secret image.

These are just some ideas; there are many possibilities for combining zero-knowledge proofs and HTML/CSS.

Waiting list
In online shopping, prove that the number of products you want and the number of people who are currently considering buying the same product are correct.

Some idea will not be evaluated UX-wise (they may be encompassed by RISC-zero)
I seek your opinion.

Just a thought process that would be required:

ZK works purely in the mathematical domain. When it comes to integrating with, say, authentication systems or visual systems, we need to find a fault-proof way of information retrieval. This information can then be encoded and used in ZK circuits.

Traditionally, blockchains help here (ZK rollups do this, they prove that a certain set of transactions have executed over a past state, bringing it to the present state without needing to share the exact transactions).

In your cases, we will need to find out

  1. A fault-proof way of finding a person’s age (presently, the users themselves cannot be trusted, or the government issued ID card can be faked)
  2. A fault-proof way of retrieving the visual rendering of the screen (To prove that the content was indeed rendered on the screen)