How wizicer/maskmeta works
High-Level Architecture Components
The system should be represented as a full-stack application with the following main components:
a. Frontend Layer (Quasar/Vue.js):
• Main application container
• Views (Explore, Graph, Mask, Meta, ProofRequest pages)
• Component structure for dialogs and UI elements
b. Backend Layer (Node.js/Express):
• API endpoints
• Integration services for Web5, Arcblock, and Pinata
• Storage management
c. External Services:
• TBD (Web5)
• Arcblock
• Pinata IPFS
• Blockchain networks
Key Architectural Elements
a. Core Concepts (represented as distinct modules):
• Mask Management System
• Meta (VC) Management System
• ZKP Processing Module
• DID Integration Hub
b. Data Flow Paths:
• User Authentication Flow
• VC Issuance Flow
• ZKP Generation/Verification Flow
• Storage Operations (Online/Offline)
Detailed Component Breakdown
Frontend Components (from src/):
• Pages Layer
• Explore
• Graph
• Mask
• Meta
• ProofRequest
• Components Layer
• Dialogs (Detail/QR/ZKP)
• Core Components
• Stores Layer
• Vault Management
Backend Services (from server/):
• API Services
• Integration Services
• TBD Connector
• Arcblock Connector
• Pinata Connector
• Storage Management
Integration Points
Clearly mark:
• API endpoints
• External service connections
• Storage interfaces
• Blockchain interactions
Key Workflows
Four main scenarios: