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.
The encryption key is sharded among the nodes, and MPC is utilized to reconstruct the information in memory during payload delivery.
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.
Component Breakdown:
Client-Side (User Device) | |
Component | Component |
Authentication & Encryption | User connects their wallet or email |
Social Account Integration | Users attach social accounts |
Blockchain Address Integration | Users can add multiple blockchain addresses for multi-chain support. |
Biometrics | Palm based vector data |
Data Processing Layers | |
- Transformation | Data is normalized for consistency. |
- Enrichment | Additional context is added to the data. |
Multi-Party Computation | |
- Encryption | All of the above data is encrypted client-side. |
- Sharding | The encryption key is sharded across nodes. |
Updation & Verification | |
Updation Enginer | Users can update the nonsensitive metadata values. |
Verification Engine | Issues and verifies credentials using SyncID Registery |
Last updated