Let's find out what problem zkpass solves and what role it can play in web3! And get those breakthroughs in technology.

Authentication includes Strong Authentication(e.g, deterministic identity required by KYC) and Light Authentication(e.g., OAuth authorization in Github mailboxes)

   Identity solves the problem of "who I am,"while authentication addresses the problem of "proving someone is what they claim to be"In the phvsical world people's identity is directly authenticated by their ID passport","driver's license,'"bank cards," and other tvpes of proofs issued byrelevant authorities,In the digital world, people's identity is indirectly authenticated by their "social accounts," "cell phone numbers," "deposit accounts" and other data which trusted media file with the authorities.Currently, both physical and digital worlds are inseparable from the very source of identity authentication: the authorities, because they create people's identitv information and store it in the trusted medium of Web2So the Web3 privacy identity protocol we are about to develop will inevitably need to cite Web2's data sources, There are many examples of such citations for identityauthentications The typical one is the address identity authentication which a project owner undertakes on the Web2 social platform to prevent Witch Attacks on airdrop marketing campaigns.

An Improved KYC Model a natural idea is adopted to develop a complete decentralization mode of Web3 and to remove KYC service providers from the whole KYC process through ZKP(Zero-Knowledge Proofto protect private data from being leaked. We define a new KYC model wherein .The verifier communicates directly with identity issuers to obtain the authentication results .The prover generates a proof of KYC Verification Passed and sends it to the verificr; .The verifier verifies the legitimacy of the proof and performs subsequent business logic processing based on the verification results.

This improved KYC model allows the prover absolute control over his or her private data and eliminates any risk of private data leaking to third parties because of ZKP Since the user communicates directly with the identity issuerthe identity issuer can return almost all of the user's information as long as Token Verification passes(the user holds the user ID and password),substantially enhancing the entire system's KYC capability. According to the KYC request of the verifier,the user can return proof that only satisfies the KYC request preciselythus further ensuring private data is not leaked to the verifier.

Unfortunately, this improved KYC model also has some further problems ·Compatibility: The system requires that each traditional Web2 identity issuer's data must be introduced into a decentralized Web3 network and that their interfaces are compatible. In the current Web3 domain,there is no such solution that does not rely on third parties. Anti-cheating and security:The lack ofeffective oversight over the communication process between the prover and the identity issuer and the process of proof generation allows the prover to forge proofs to deceive the verifier, For example, if Alice wants to prove to Bob that herTwitter account has more than 3000 followers: Alice could send a request to a fake"Twitter," get a return result of 300000 followers and construct a proof for Bob to verify. Without any network communication, Alice can even directly forge a local return result of 300,000 followers based on the format of the data returned by Twitter and construct a proof for Bob to verify,in which case Bob can still verify the data without being able to confirm the source

To solve all the problems mentioned abovewe proposed an earth-breaking model of KYC: zkPass.

zkPass zkPass is a decentralized KYC solution based on MPC(Multi-PartyComputation and ZKP (Zero-Knowledge Proof) which aims to overcome the various flaws in the current KYC system, eliminate the pain points related to identity authentication and protect user privacy while expanding KYC capabilities.

zkPass allows users to anonymously prove their identitystatements to third parties(other project parties/verifiers) through their credentials with the Web2 identity issuer, In converting Web2 customer identity credentials into anonymous credentials there is no need for a centralized server (traditional KYC platforms) or trusted hardware (TEEctc).The zkPass Protocol is the perfect alternative to the traditional KYC service provider,providing businesses and users with a higher level of KYC solutions utterly decentralized way.

Business users or proiect parties can conveniently integrate their existing projects with zkPass and gain far greater KYC capabilities byconducting on-chain gueries through the API qateway but cannot collect user datazkPass offers a combination of multiple KYC templates,allowing busincsses to choose a solution that applics to them, In the meantime, based on their individual KYC needs,business users can expand various existing KYC templates via zkPass Kitsuch as identity verification. address verification,or social-related verification

For regular users, zkPass is a useroriented KYC solution that eliminates user privacy breaching from the protocol layer while easing the pain of new account opening and repeated KYC redos,Once users complete the KYC verification. they can immediately ioin a related business in the zkPass ecosystem zkPass provides a faster. cheaper. and more efficient way of KYC experience with the reusable KYC and authentication approach while all the data remaining under the control of the users Finally, I would like to say that zkpass is a very good project, and it will be the most important and most useful in web3 in the future. Below is a link to donate, let's support zkpass together.