Store Review CID for IPFS Reference

[Naomi-Gift]

Description:

All review text should be stored off-chain, with only the IPFS CID stored on-chain. This allows the contract to reference review content efficiently while keeping on-chain storage minimal.

Expected Behavior:

CID is stored on-chain and associated with the project ID and reviewer address.

Any fetch function returns the CID to enable frontend retrieval from IPFS.

Implementation Notes:

Ensure CID format validation.

Consider gas efficiency when storing multiple reviews per project.

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 100 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

[iammrjude]

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

Hi @HubDApp.
I'd like to work on this issue.

My plan:

1. Add a submit_review(env, reviewer, project_id, cid) function that stores the IPFS CID on-chain keyed by project ID and reviewer address
2. Add CID format validation before storing
3. Add get_review_cid(env, project_id, reviewer) and get_project_reviews(env, project_id) fetch functions that return CIDs for frontend IPFS retrieval
4. Use efficient storage structure to handle multiple reviews per project without excessive gas cost
5. Write tests for successful CID storage, invalid CID format, and CID retrieval

My background: Rust, Solidity, Python, JavaScript, and Next.js. I can deliver this in 4 hours.
Can you assign this to me?

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

[drips-wave]

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

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

[Austinaminu2]

Gm maintainer,

I’d like to work on this issue.

I have experience working with Rust and Soroban smart contracts, as well as integrating IPFS-based off-chain storage. I will implement logic to store review IPFS CIDs on-chain, associate them with the project ID and reviewer address, and ensure retrieval functions return the CID for frontend IPFS access. I will also add CID format validation and design the storage structure to remain gas-efficient when handling multiple reviews per project.

ETA: 2–3 hours.

Please assign this issue to me.