Build key rating submission function with running average update

[Chucks1093]

Summary

Implement the on-chain key rating function that accepts holder ratings, maintains a running average, and prevents non-holders from submitting ratings.

Scope

• rate_key() accepts score 1-5 from authenticated holder
• Minimum holding balance required to submit
• Running average updated using incremental formula on each submission
• One rating per wallet — re-submission updates average correctly
• KeyRated event emitted with new score, wallet, and updated average

Acceptance Criteria

• Ratings rejected from wallets below minimum holding
• Running average updated correctly on first and subsequent submissions
• Re-submission from same wallet recalculates average without double-counting
• KeyRated event emitted with correct fields
• Unit tests cover first rating, re-rating, and non-holder rejection

ETA

24 hours

[guptakumarranjeet150]

Hello team,

I would like to resolve this issue. Here is my proposed execution plan:

• Implementation: Implement Build key rating submission function with running average update with explicit require_auth checks, secure state storage, and gas optimization.
• Testing: Add Soroban test cases checking unauthorized invocations, edge values, and state updates.

I am ready to start immediately—please feel free to assign this to me!

[Salome-Agu]

@Salome-Agu has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hello Maintainer, i can fix this issue

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

[Israel-light]

@Israel-light has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

I'd like to work on this issue because the rating function combines authorization, state management, and incremental aggregation, so correctness matters both for preventing unauthorized ratings and for keeping the on-chain average accurate as ratings change.

I am confident I can implement rate_key() by first tracing the existing key ownership, holding-balance checks, storage model, and event conventions in the contract. I'll enforce the 1–5 score range and minimum holding requirement before modifying state, then maintain the running average incrementally. For re-submissions, I'll account for the wallet's previous score and adjust the aggregate rather than treating the new submission as an additional rating, preventing the same wallet from being double-counted.

I'll also emit KeyRated with the wallet, submitted score, and resulting average using the contract's established event pattern. Unit tests will cover the first rating, multiple ratings, re-rating an existing submission, invalid scores, and rejection of wallets below the minimum holding threshold, including assertions that the aggregate remains correct after each state transition.

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

[Luchi5544]

@Luchi5544 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Good day maintainer i would love to work on this issue please assign me

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

[iexwr]

@iexwr has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hello Maintainer, i can fix this issue

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

[BaseDev-Eth]

@BaseDev-Eth has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

hello maintainer, can i work on this issue

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

[CHKM001]

@CHKM001 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

let me get this for you please

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

[ONEONUORA]

@ONEONUORA has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hi
I am a smart contract developer with 5 years of experience
I believe i can handle this issue

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

[drips-wave]

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

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

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@ONEONUORA's PR #1010 was approved and merged by @Chucks1093.

🏆 @ONEONUORA: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,105 total points). Track your full progress on GrantFox.

👏 Great work, @ONEONUORA! Keep contributing to accesslayerorg.

[drips-wave]

This issue has been completed by @ONEONUORA as part of the Stellar Wave Program's 9th Wave 🥳

😎 @ONEONUORA: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.