Architecture and Identity Flow
Last updated
Last updated
Welcome to the technical documentation of the Zyphe Platform, where we bridge Self-Sovereign Identity (SSI), Account Abstraction, and decentralized compliance workflows to deliver privacy-preserving KYC and AML experiences for both users and businesses.
This guide walks through a series of diagrams that detail our system's architecture, data flow, and logic β designed for developers, integrators, and technical stakeholders.
This documentation includes three key system diagrams that cover the major functional areas of the Zyphe platform:
Understand how a user goes from uploading an identity document to getting a Verifiable Credential (VC) stored in a secure vault, with built-in AML compliance checks.
β‘οΈ Topics covered:
Vault creation
Document verification
VC issuance
AML checks
Business-specific requirements
Data sharing and update flows
How the platform handles data deletion requests while respecting active business data retention policies.
β‘οΈ Topics covered:
Conditional vault data deletion
Temporary storage logic
Revoking business access
Privacy compliance by design
A deep dive into the identity model using ED25519 keys and counterfactual smart wallets, enabling users to control access to their data and credentials through an account-abstracted architecture.
β‘οΈ Topics covered:
Keypair generation
VC binding to smart contract wallets
Identity factory
SCW (Smart Contract Wallet) verification and proxy flow
ED25519 & SECP256K1 key infrastructure
Verifiable Credentials (VCs)
Decentralized Storage
Account Abstraction & Smart Contract Wallets (SCW)
AML/PEP Screening Integration
Proxy Re-Encryption (via Lit or similar)
Each page in this documentation explains:
The purpose and scope of the diagram
A breakdown of key steps and decision points
The privacy and compliance principles involved
Any smart contract or cryptographic operations relevant
If you're building on or integrating with Zyphe, these flows will help you understand our SSI-driven architecture and how we enable trustless compliance at scale.
Letβs dive in π