# Overview

Jomo Connect enables applications to easily verify user data from various onchain or offchain sources via zero knowledge proof without getting user's raw data exposed to anyone. 

## Glossary

<table><thead><tr><th width="137.33333333333331">Term</th><th>Definition</th><th>Example</th></tr></thead><tbody><tr><td>VC</td><td><p>A verifiable credential is a statement about some piece of information, that is verifiably attested by an attester.</p><p>A VC could be about someone or something, or not be about a specific entity. It could be bound to an unique identifier, or could just be stored by anyone anywhere.<br><br>All VCs created for users by Jomo are stored in the form of EAS attestations.</p></td><td><ul><li>Statement: The Earth is a sphere</li><li>Attester: Columbus</li><li>Signature: Columbus signing on the Statement</li></ul></td></tr><tr><td>Private VC</td><td>A private VC is a VC that nobody except for its owner, knows about its detailed contents in the statement. The general public only sees a deterministically encrypted form of the statement but not the raw data.</td><td><ul><li>Actual content (only the VC owner knows): passport number, country, issue and expiry date, name, etc</li><li>Statement: Some sort of hash of the content above</li><li>Attester: Government</li><li>Signature: The NFC chip on the physical passport containing a signature of the statement</li></ul></td></tr><tr><td>Attributes</td><td><p>A data attribute is a field→value pair within a VC content.</p><p>Note that for private VCs, other than the owners themselves, no one else should know what attributes and their values exist in a private VC</p></td><td><ul><li>&#x3C;company_name, Jomo></li><li>&#x3C;passport_issue_country, USA></li></ul></td></tr></tbody></table>

## Use Cases

The private VC verification framework enables users to use their private data and get benefits by proving they qualify for them, without revealing any tangible private information.

Example use cases include proving that:

* I have donated to Gitcoin in total value of X (private information: all addresses I own)
* Smart contracts I deployed over different chains have acquired activities of amount Y (private information: all addresses I own)
* My Github repositories have a total stars of Z (private information: my github handle)
* I have worked at company A for > B years (private information: who I am)
* Owns a house valued > $1M (private information: my home address, house value)

## Example Experience

* User is redirected to Jomo Connect when you try to verify the private information of a user

<figure><img src="/files/VrE5MozblSUr430PwMKe" alt="" width="563"><figcaption></figcaption></figure>

* User connects to the corresponding data source and have Jomo generate a private VC for them.

<figure><img src="/files/1gLcU4oUwH7Nnd4nVG0T" alt="" width="375"><figcaption></figcaption></figure>

* Jomo Connect frontend generates zero knowledge proof based on the user's private VC

<figure><img src="/files/ItVwp0iraU31vaEbYhVP" alt="" width="375"><figcaption></figcaption></figure>

* You receive the zero knowledge proof and associated additional data

<figure><img src="/files/CFoirC5Qn93IM8eZyJNq" alt="" width="375"><figcaption></figcaption></figure>

* You verify the proof and additional data are valid with Jomo Connect Smart Contract or Backend
* (Optional) Jomo Connect backend verifies the proof and share with you the validness of the proof and any corresponding results via a callback or subsequent API calls
* You customize the UX based on the result

<figure><img src="/files/0GNQdWoV3pyIHsm4j6FN" alt="" width="563"><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.jomo.id/build-with-jomo-connect/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.