Add Merkle-proof-based reputation verification

[dDevAhmed]

📚 Overview

Contracts currently trust backend/oracle reputation values without verification.

---

🌊 Drips Context

This violates a core Web3 principle: trust minimization.

Reputation must be cryptographically verifiable.

---

❗ Problem

• Direct oracle reads
• No proof validation

---

✅ Expected Behavior

• Backend submits Merkle root
• Users provide proof when voting
• Contract verifies inclusion

---

🧠 Implementation Guidelines

• Add root storage
• Add proof verification function
• Modify vote function to require proof

---

✅ Acceptance Criteria

• Valid proofs pass
• Invalid proofs revert
• Root updates handled safely

---

⏳ Complexity

High

---

🏷 Labels

audit, protocol, high-priority, drips-wave

[Dayz-tech-co]

@Dayz-tech-co has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

I’d like to work on issue #60 in the truthbounty-contract repository.

I’ll implement Merkle-proof-based reputation verification to replace direct oracle reads, adding storage for the root, a proof verification function, and updating the vote function to require valid proofs. Invalid proofs will revert, and root updates will be handled safely. This ensures trust-minimized, cryptographically verifiable reputation for the protocol.

Experienced with Rust smart contracts and Merkle-tree verification—happy to deliver a secure, well-tested implementation.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Dayz-tech-co to this issue.

[olawale880]

@olawale880 has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Please I'll like to be assigned this issue

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

[walterthesmart]

@walterthesmart has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hi @dDevAhmed, I would like to work on this issue

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

[drips-wave]

Congratulations, @walterthesmart! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on March 30, 2026.

🧑‍💻 @walterthesmart: 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 awarded 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 🌊