Architecture & Trust Model

SyncNexa is built on a tripartite trust architecture connecting Issuers (Universities), Holders (Students), and Verifiers (Businesses / Relying Parties). Cryptographic signatures and zero-knowledge circuit validation ensure that no single party holds unnecessary information.

The Decentralized Trust Triad

Zero-Knowledge Verification

Traditional verification forces students to hand over copies of their government ID or student card. SyncNexa replaces this with a mathematical proof: the verifier poses a challenge ($C$), and the student's device computes a zk-SNARK proof ($pi$) demonstrating that:

• The credential was signed by an authorized university in the SyncNexa trust registry.
• The current timestamp falls between valid_from and valid_until.
• The credential has not been revoked by the issuing institution.
• The student possesses the corresponding private device key without revealing it.

System Topology

The SyncNexa platform is engineered with a high-throughput, low-latency microservice architecture:

• API Gateway: Dot-notation routing (api.business.syncnexa.co, api.syncnexa.co), SSL termination, rate-limiting, and authentication proxying.
• Org Service (`syncid-org`): Manages business applications, environments, API keys, OAuth clients, and billing accounts.
• Verification Service (`syncid-verification`): Evaluates zero-knowledge proofs, cryptographic signatures, and generates verification tokens.
• Consent Service (`syncid-consent`): Manages granular, revocable permissions between students and requesting applications.
• Notification & Webhooks Engine (`syncid-notification`): Dispatches real-time HMAC-signed webhooks to business endpoints with automatic exponential backoff retries.

Cryptographic Security Guarantees