zkMe Docs
Ask or search…
K
Links

High Level User Stories

This chapter presents a high-level solution overview of the zkMe network through long-form User Stories for the following zkMe Identity Layer Stakeholders:

1. The Holder (End User)

  1. 1.
    The Holder wants to leverage owned off and cross-chain credentials (e.g. a government issued ID card), in order to gain access to permissioned/access controlled services (e.g. permissioned yield pools) on any chain-ecosystem.
  2. 2.
    The Holder wants to reveal as little information about him/herself as possible and stay anonymous for as long as possible in order to avoid any party (incl. the Issuer, Verifier or Regulator or any other uninvolved party) to benefit or abuse the link between his/her Identity and public service consumption patterns.
  3. 3.
    The Holder values the following metrics (from high to low priority):
    • Low PII Data Sharing Rates
    • Low Average Time to Service (i.e. average time it takes for a user to onboard to a permissioned service)

2. The Verifier (Service Provider)

  1. 1.
    The Verifier needs to fulfill a degree of user due diligence before onboarding a user in order to either
    • fulfill internal business needs (e.g. targeted service provision),
    • reduce fraud (e.g. remove bots & duplicate accounts),
    • avoid jurisdiction (e.g. not provide services to residents of certain countries), or
    • fulfill compliance requirements (e.g. enhanced customer due diligence during onboarding).
  2. 2.
    The Verifier requires a solution that is fully decentralized and cost-effective in order to minimize the financial impact of introducing user verification services.
  3. 3.
    The Verifier requires a solution that is data minimized and secure from accidental (internal and/or external) user data misuse and leaks in order to fulfills it’s requirements under global data privacy regulations such as EU’s GDPR.
  4. 4.
    The Verifier values the following metrics (from high to low priority):
    • High User Verification Retention Rate (i.e. how many users do not drop-off during the verification process)
    • Low Crossover Error Rate (i.e. a combination error of false positive and false negative user verifications)
    • Low Costs per Verification

3. The Operator

Documentation coming soon.

4. The Regulator

  1. 1.
    The Regulator wants to protect Holders (within its legislation) to access unregistered financial services in order to protect the Holder from intransparent risks.
  2. 2.
    The Regulator requires the ability to recover the real Identity of a Holder in case formal bad actor proceedings are initiated against the Holder.

5. The Issuer

5A. The Credential Issuer

Documentation coming soon.

5B. The Issuer-Algorithm Developer

Documentation coming soon.