How srikanth200217/forensic-evidence-management works
Project type and purpose
• This is a domain-specific full-stack system for forensic evidence management, leveraging blockchain to guarantee data integrity and non-repudiation of evidence.
• Its primary goal is to secure, track, and manage digital and physical evidence across its entire lifecycle, from collection through analysis to presentation in court.
(minimal) file structure
• At present, we only see a README, but we can infer key components:
• A blockchain layer (smart contracts, ledger nodes)
• An off-chain storage layer for large evidence files
• A backend/API service to mediate between clients and the blockchain
• A frontend/user interface for investigators, lab technicians, auditors, and legal staff
• Authentication/authorization and audit‐logging subsystems
README for additional insights
• The README emphasizes immutability and decentralized trust via blockchain.
• We know the system will record evidence metadata (e.g., hash, timestamp, custody chain) on-chain and store bulk data off-chain.
a. Main Components
1. User Clients – Browser or mobile interface for different roles (Investigator, Lab Tech, Auditor)
2. API Gateway / Backend Service – REST or GraphQL endpoints, business logic
3. Blockchain Network – Smart contracts, consensus nodes, ledger
4. Off-Chain Storage – IPFS, S3, or other blob storage for actual evidence files
5. Identity & Access Management – OAuth2/OpenID Connect or custom IAM
6. Audit & Monitoring – Logging service, analytics dashboard
7. External Integrations – Court systems, law-enforcement databases
b. Relationships & Interactions
• Users authenticate via IAM → receive tokens → call API
• For new evidence: Frontend uploads file to Off-Chain Storage → computes hash → calls Backend
• Backend invokes Smart Contract → writes hash + metadata to Blockchain
• For verification: Frontend requests record → Backend reads from blockchain → retrieves metadata and compares stored hash with off-chain file hash
• Audit logs capture every transaction and API call for compliance
c. Architectural Patterns & Principles
• Layered Architecture (Presentation → API/Service → Blockchain/Storage)
• CQRS for read vs. write paths (writes go on-chain, reads can be served from a read-optimized cache)
• Use of smart contracts as “trust anchor”
• Separation of concerns: evidence data vs. metadata
d. Key Technologies & Frameworks
• Blockchain: Ethereum/Hyperledger Fabric, Solidity chaincode
• Backend: Node.js/Express or Python/Flask
• Frontend: React/Vue/Angular
• Storage: IPFS or AWS S3
• Auth: Keycloak/Auth0 or custom JWT service
• Logging: ELK stack or Prometheus/Grafana