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

[Ryjen1]

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

Kindly assign

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

[BigJohn-dev]

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

This issue appeals to me because it combines the challenge of solving complex frontend performance problems with the opportunity to deliver a smoother, more reliable user experience, while also sharpening my skills with emerging design and resolution patterns.

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