> For the complete documentation index, see [llms.txt](https://docs.oppassport.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oppassport.xyz/system-framework/architecture-overview.md).

# Architecture Overview

The system architecture includes the front-end web interface, back-end services, smart contracts, and a database for tracking user achievements and badge issuance. The architecture is designed to ensure privacy and security through the integration of ZK technology.<br>

## OP Passport Creation Flow

The creation of an OP Passport involves several steps, integrating both off-chain and on-chain processes to ensure a secure, verifiable, and privacy-preserving digital identity. Here's a summarized flow:

1. **User Eligibility & Initiation:**
   * A user eligible for creating an OP Passport initiates the process through the Passport frontend.
2. **Passport Creation Request:**
   * The request is sent to the OP Passport API, which creates the passport, updates the database, and sends a task to GCP Cloud Task for further processing.
3. **Safe Wallet Creation:**
   * A Safe wallet is created for the user, which will store their digital identity.
4. **Attestation Process:**
   * The Attestation API constructs the necessary EAS schemas for the passport and user achievements.
   * The system attests the passport and achievements on-chain using the Ethereum Attestation Service (EAS).
5. **Finalization:**
   * The passport and associated achievements are recorded on-chain with their respective EAS IDs and transaction hashes (TxHash).
   * The OP Passport API updates the passport with all relevant on-chain data, completing the process.

This flow ensures that each user's governance participation and achievements are securely documented, providing a verifiable and transparent on-chain identity.

<figure><img src="/files/38qSgulJbn5QUQTz9LGN" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.oppassport.xyz/system-framework/architecture-overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.