# Technical Architecture

SyncID is a reference point that is linked to the user's crosschain wallet addresses and social accounts through a dynamic SBT (soul-bound token) which the user has full control over. 

Its architecture is designed to offer a Sybil-resistant solution for digital identity, combining proof of personhood authentication for dApps, advanced encryption, decentralized storage, and multi-party computation to ensure the integrity and privacy of user identities.

* **Data Encryption & Storage**\
  \- SyncID starts by ensuring robust data encryption. All sensitive user data such as personal web2 identitifiers and biometrics is encrypted directly on the device.

<mark style="color:yellow;">The encryption key is sharded among the nodes, and MPC is utilized to reconstruct the information in memory during payload delivery.</mark>

* **Privacy-Preserving Data Use**\
  SyncID strictly controls access to decrypted data through user permissions, preserving privacy. SyncID issues an on-chain credential embedded with anonymized sensitive data and related metadata, allowing for identity verification.&#x20;

## **Component Breakdown:**

<table data-header-hidden><thead><tr><th width="313"></th><th></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>Client-Side (User Device)</strong></mark></td><td></td></tr><tr><td><strong>Component</strong></td><td><strong>Component</strong></td></tr><tr><td>Authentication &#x26; Encryption</td><td>User connects their wallet or email</td></tr><tr><td>Social Account Integration</td><td>Users attach social accounts</td></tr><tr><td>Blockchain Address Integration</td><td>Users can add multiple blockchain addresses for multi-chain support.</td></tr><tr><td>Biometrics</td><td>Palm based vector data</td></tr><tr><td><mark style="color:blue;">Data Processing Layers</mark></td><td></td></tr><tr><td>- Transformation</td><td>Data is normalized for consistency.</td></tr><tr><td>- Enrichment</td><td>Additional context is added to the data.</td></tr><tr><td><mark style="color:blue;">Multi-Party Computation</mark></td><td></td></tr><tr><td>- Encryption</td><td>All of the above data is encrypted client-side.</td></tr><tr><td>- Sharding</td><td>The encryption key is sharded across nodes.</td></tr><tr><td><mark style="color:blue;"><strong>Updation &#x26; Verification</strong></mark></td><td></td></tr><tr><td>Updation Enginer</td><td>Users can update the nonsensitive metadata values.</td></tr><tr><td>Verification Engine</td><td>Issues and verifies credentials using SyncID Registery</td></tr></tbody></table>


---

# 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://syncs-organization.gitbook.io/copy-of-syncai-network-whitepaper/features/syncid/technical-architecture.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.