How cyscz/blockchain-based-data-sharing works
Main Components
a) Client-Server Architecture
• Two distinct server components (client_server_1 and main_server)
• Each server contains identical structure with web interface components
• Blockchain nodes for each server
b) Data Storage Layer
• Blockchain storage (Hyperledger Fabric)
• IPFS storage system
• Data balancing mechanism between on-chain and off-chain storage
c) Frontend Components
• Web interface (templates directory)
• Static assets (CSS, JS, images)
• User interaction flows
┌─ User Interface Layer ─────────────────────┐
• Web Frontend (React/Python) │
• Templates (HTML) │
• Static Assets (CSS/JS) │
• ┬───────────────────────┘
• ↓
┌─ Application Layer ──────────────────────┐
• ┌─ Client Server 1 ─┐ ┌─ Main Server ─┐ │
• Server.py │ │ - Server.py │ │
• Blockchain.py │ │ - Blockchain.py│ │
• ┘ └───────────────┘ │
• ┬───────────────────────┘
• ↓
┌─ Storage Layer ────────────────────────────┐
• ┌─ On-Chain ─────┐ ┌─ Off-Chain ─────┐ │
• Hyperledger │ │ IPFS Protocol │ │
• Fabric │←→│ Storage │ │
• ┘ └───────────────┘ │
• ┘
Key Elements to Highlight
a) Current Implementation:
• Basic blockchain file sharing system
• Web interface for file upload/download
• Server-side blockchain implementation
b) Planned Features:
• Data balancing mechanism (highlight as future component)
• AI-powered optimization (mark as future enhancement)
• IPFS integration (show as planned component)
Data Flow Indicators
• File upload path from UI → Server → Storage
• Blockchain transaction flow
• Data balancing decision points
• IPFS interaction paths
Implementation Notes
• Maintain consistent component sizing
• Version/status indicators for planned features
Remember to:
• Clearly distinguish between implemented and planned features
• Optimization points for data balancing
• Integration points for future AI components