It's also a dangerous system if someone successfully steals or fakes identity. Unless it can be made impossible to fool the system.
In our system, no identity information is stored on the blockchain. Identities are verified through a third-party certification agency, and then a zero-knowledge proof is used to communicate to the blockchain that the identity is verified without disclosing any identity information. You would need the agreement of multiple actors in order to trace someone's identity from their address, but these actors are bound by contract to only cooperate in situations such as government compliance and to not act maliciously.
I see, so what is the main purpose of your network? Is it mostly about the innovative proof of work?
Besides the use of innovations like RPOW and sharding, Usechain is special because it will be the first public blockchain built on a mirror identity protocol. Through technological innovations and adding the dimension of identity, Usechain will solve the Impossible Trinity and achieve a balance between scale, security, and decentralization. In addition, Usechain's mirror identity protocol supports KYC and government compliance, so the blockchain can provide infrastructure for decentralized apps in various industries that require identity information. Hence, we see Usechain as a leader of the Blockchain 3.0 era, where blockchain can truly be integrated into financial services, sharing economy applications, and more.
At lot of stuff in that one paragraph
As for the mirror identity protocol, does it mean that every user of the network has to disclose ID information to the network while keeping control over it and once ID info is required from an APP or something else, the user can provide that info? Will it be with zk-proofs?Network users will disclose identity information to a reliable third-party certification agency, but not directly to the blockchain. Communicating identity authentication to the blockchain will indeed be done through a zero-knowledge proof. While there will be no identity information stored directly on the main chain, the interface will contain relevant calls for identity information that support a variety of different requirements for applications that involve identity.
Ok but doesn't that also create a lot of risk if a third party certification agency holds all the ID info of people? Are there ways to abuse that ID info or how will it be tied to the original owner? Just trying to understand the full scope of your protocol.
