High Level Architectural Overview

zkMe Network is an innovative Digital Identity approach designed to unify, standardize and process digital identities across all ecosystems (across all chains, web2, and even web1 environments). This decentralized, permissionless, and composable zk-Identity Layer leverages (among others) a combination of cutting-edge ZKP, FHE, and MPC technologies to allow for truly universal, secure and versatile verification, management, and monetization of Credential Data. In the zkMe Network, one Identity is the abstract term describing the unique collection of any number of trusted and verifiable Credentials. Each Credential represents a collection of trusted facts the Credential Holder owns & manages in Self-Sovereignty in a Self-Sovereign Identity Wallet (SSI). The trust is in the Credential is ensured by the temper-proof MeChain infrastructure and the trustless access to a trusted Issuer. An Issuer is the creator of a Credential within the zkMe Network. Such an Issuer can either be a "Centralized Issuer" or a "Decentralized Issuer". A Centralized Issuer is an entity trusted by other Stakeholders in the Network directly 'issuing' Credentials on the zkMe Network. A Decentralized Issuer is a programmatic bridge to a trusted Issuer that is not part of the zkMe Network in order to 'automatically issue' Credentials without the introduction of a new intermediary Centralized Issuer. Verifiers are the consumers of Credentials within the zkMe Network. Operators run the infrastructure of the zkMe Network. Operators either run Validator or Storage nodes. Guardians oversee the correct operations of the zkMe Network. Unlike other cross-chain solutions that primarily focus on asset transfer between different chains, zkMe specializes in creating a seamless, unified Identity user experience. The zkMe Network consists of an Application Layer, an Execution Layer, and a Data Layer. The Application Layer hosts all Issuers (the 'MeChain ecosystem') that provide Credential data through the zkMe Network, including the zkMe protocol. The Execution Layer provides the necessary functionality to process & secure Credential and Asset flow on MeChain (PoS Consensus & Validator ), the Credential flow across Chains (Identity Oracle), ability to run arbitrary code (EVM-Compatibility), and built-in value carrier in form of the $ZKME token. The Storage Layer provides the necessary functionality to store, protect, and retrieve Credential data.