How tum-i4/kovacs works
Main System Components
a) Network Layer:
• Bootnode (entry point for network discovery)
• Node instances (distributed nodes in the network)
• MDNS for peer discovery (visible in node/p2p/mdns.go)
b) Core Services:
• Revolori Service (external identity management system)
• Ethereum Network (indicated by geth directory and blockchain storage)
• Nginx Proxy (for network access management)
c) Functional Components:
• Listener Service
• Requester Service
• Verifier Service
• User Management System
• Storage System (both Blockchain and SQLite)
Component Relationships
a) Data Flow:
• User Management → Revolori (authentication flow)
• Nodes ↔ Bootnode (network discovery)
• Nodes ↔ Nodes (P2P communication)
• Nodes → Storage (both blockchain and SQLite)
• Requester → Nodes (data requests)
• Listener → Storage (data persistence)
b) Security Layer:
• Encryption flows (based on node/encryption)
• Non-repudiation system (from node/nonRepudiation)
• Password management (from node/password)
Architectural Patterns to Highlight
• P2P Network Components (hexagons)
• Security Services (shields)
• External Services (clouds)
• Internal Services (rectangles)
Technical Details
Annotations for:
• Docker containerization
• Ethereum smart contract integration
• Authentication mechanisms
• Encryption standards (AES-GCM)
• Non-repudiation protocols
Service Layer (middle)
• Node Network
• Security Services
• Management Services
Storage Layer (bottom)
• Blockchain
• SQLite
External Services (side)
• Revolori
• Bootnode
Critical Aspects to Emphasize
• Security mechanisms (encryption, non-repudiation)
• Distributed nature of the system
• Data flow paths
• Storage redundancy
• Error handling paths
• Authentication flows