Client-Side Encrypted Evidence Vault for the Dispute Courtroom

[meshackyaro]

Description

This issue aims to address the implementation of Client-Side Encrypted Evidence Vault for the Dispute Courtroom.

The core objective is to: Encrypt dispute evidence in-browser to juror public keys before pinning to IPFS, and decrypt it on the juror side so raw files are never exposed to the gateway or backend.

By completing this feature, we will ensure that the TrustFlow protocol maintains its high standards for security, usability, and decentralized logic. This issue requires careful attention to the Frontend architecture and adherence to the existing project conventions.

When picking up this issue, please ensure you document any new dependencies or architectural decisions made during development.

Component

Frontend

Difficulty

🔴 Hard

Tasks

• Review Next.js App Router structure
• Implement the UI components for: Client-Side Encrypted Evidence Vault for the Dispute Courtroom
• Ensure responsive design using Tailwind CSS or standard modules
• Add caching for npm dependencies in CI
• Run npm run lint and npm run typecheck
• Run npm run build to verify production bundling

Acceptance Criteria

• Feature accurately implements the objective: Encrypt dispute evidence in-browser to juror public keys before pinning to IPFS, and decrypt it on the juror side so raw files are never exposed to the gateway or backend.
• Any PR that introduces TypeScript errors is automatically blocked
• CI pipeline runs in under 3 minutes per PR
• Code is properly reviewed and approved by codeowners

Estimated Time

3-5 days