Verify Content Hash Integrity

[dDevAhmed]

📚 Overview

Ensure uploaded evidence matches stored content hashes to prevent tampering.

---

🎯 Objectives

• Compute hash locally
• Compare with returned CID
• Validate integrity before DB write

---

🧠 Scope

• Hash utilities
• Middleware validation
• Evidence verification step

---

✅ Acceptance Criteria

• Hash mismatch rejected
• Logs produced
• Tests included

---

⏳ Complexity

High

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[Obiajulu-gif]

@Obiajulu-gif has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

GM maintainer, this looks familiar and I’d love to work on it because it’s a clean security hardening: we’ll make evidence tamper-evident by verifying the content hash before anything is persisted. I’ll add hash utilities to compute a deterministic digest from the uploaded file buffer, introduce middleware that validates the computed hash against the expected hash/CID returned by storage (rejecting on any mismatch), and wire an explicit “evidence verification” step in the upload flow so the DB write only happens after integrity passes.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Obiajulu-gif to this issue.

[ummarig]

@ummarig has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Let me promptly implement this task as soon as possible with an ETA of 2 to 4 hours

ℹ️ Repo Maintainers: To accept this application, review their application or assign @ummarig to this issue.

[Babigdk]

@Babigdk has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Kindly assigned me to this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Babigdk to this issue.

[drips-wave]

Congratulations, @Babigdk! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

🧑‍💻 @Babigdk: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are issued when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊