Skip to navigation

System Architecture

View as Markdown

Used in: §1.2 Why Decentralized Identity, §1.5 Platform Architecture at a Glance Audience: all personas IA ID: D1

Clients Edge IDA API (Go / Chi) Stores ADI blockchain (chain 8400 /testnet 99999) Externals Portal SPA (React + Vite) Wallet (Expo / React Native) SDK (@infinia/ida-sdk) Agent runtime (MCP-I / A2A) Load balancer / Ingress Auth handler DID handler VC + Schema handler ZKP handler Agent handler DIDComm handler Verifier + Trust handler Dashboard + Analytics PostgreSQL Redis (sessions, OTP, ratelimit, challenges) DIDRegistry SchemaRegistry RevocationRegistry AgentTrustRegistry ZKProofVerifier OAuth IdP (Google / GitHub) DIDComm mediators

Reading guide: Clients always reach the API through the ingress; the API is the only component that owns Postgres, Redis, and chain-write authority. The five registries on ADI are write-only from the API and read-only from anyone (including verifiers’ own infra), which is what makes verifications trust-minimised.