Each individual or entity that enrolls into the Everest Platform will receive their own records under the subdomains kyc.ever.eth, human.ever.eth, and kyb.ever.eth. The status for an individual can be queried at kyc.ever.eth, receiving back either a ZK proof, or a null set signifying that the address is not known. Ever.eth names can be queried via the ENS Manager App, block explorers like Etherscan, as well as directly from any full node.
The publication of this universal address set for queries improves not only the discoverability of KYC, Humanness and KYB statuses, but ensures that the VASPs, governments, and individuals who rely on that data are connected with the right information authority.
Everest through ENS is empowering wallet holders and financial institutions to privately and seamlessly share attributes (e.g., human & unique, or name) and/or credentials (i.e. KYC status, proof of age) using Ethereum.
Similar to ENS’ L2 gateway “bridge” concept, Everest’s L2 gateway oracle is able to privately and cost-effectively share zero-knowledge proofs of one’s human-uniqueness or a verified credential — all privately and strictly under the users’ control. Leveraging Everest’s L2 identity DAO and ENS’ records for human-readable keys, Everest’s MPC architecture and DAO governance ensure that only the user (no government, regulator, or even Everest) can see, verify or share their data.
To expand upon this baseline service, which uses custom subdomains and record types under the subdomains kyc.ever.eth and human.ever.eth, Everest will be proposing a dedicated text record. (How your project can have its own ENS record.)