Human Verification
Human Verification in Zero is used to determine whether or not a Handle is operated by a real human identity. The ZNS Human Verification process, outlined herein, is an alternative to both centralized verification processes and automated verification processes, such as Twitter’s infamous blue check or a CAPTCHA system, respectively.
Verification in Zero is loosely modeled off of the simple approach introduced by HumanityDAO in 2019. Unlike blue check systems utilized in services like Instagram and Twitter, verification in Zero is not intended to serve as a symbol for popularity, notoriety, or status, it is merely to determine if an individual is human or not.
Initially, there will be three tiers of identity verification in ZNS, which will result in a different level of Omega tokens being issued to a Member within the ZNS DAO (outlined in Section Verification is managed by creating a Choice in the ZNS DAO to request and issue one or more ZNS DAO Omega tokens to a Member’s account. Prior to starting this process, a Member must already have a registered Handle, which is associated to their zId and Ethereum account, by having purchased a new ZNS Registry or Registry Entry and staking Infinity.
The Member may submit a Choice of type ‘identity’ to a DAO. By default, one Omega token is requested in the amount parameter for the Choice. The Member may choose to increase this number if they feel they deserve more Omega tokens in zDAO. Active and early contributors to the Zero ecosystem are likely to request and receive more Omega due their being less participants. A Member's total Omega within the ZNS DAO relative to the total amount of issued reputation in zDAO determines a Member's voting weight (choice making authority) within the ZNS DAO. This number can also be used as a proxy by developers to determine the probability an individual account is human.
When a verification Choice is submitted, existing Omega holders in the ZNS DAO can vote as to whether or not they believe the account is a human. Verification Choices require the Member to submit third party proof of identity. Initially, the ZNS DAO will allocate different amounts of Omega tokens for three tiers of Identity verification:
  • Tier 1: Online Accounts: Access to a unique, pre-existing account for a major online service, that has not already been linked to a Handle in zDAO. Valid examples include Twitter, Facebook, GitHub, and Behance, and require the Member to post their public zId within a public post on at least one of these services.
  • Tier 2: Government Issued ID: An encrypted and password-protected photo of a government issued ID, such as an identity card, birth certificate, or passport.
  • Tier 3: Formal KYC: Formal KYC using a globally regulated third party service, such as
Verification is entirely optional and not required to utilize the Zero system, but may be used by developers to create applications that require varying levels of identity verification.
Copy link