Integrate Dispute History Weighting into Cumulative Score
- Category: Smart Contract: Reputation & Badges
- Task ID: SC-REP-043
Description
This issue is dedicated to the technical design, implementation, and rigorous auditing of 'Integrate Dispute History Weighting into Cumulative Score' inside the Lance marketplace ecosystem, specifically focusing on the Smart Contract: Reputation & Badges component. As a Soroban smart contract task, the contributor must design robust instance or persistent storage allocations, ensure safe checked math operations, and write high-coverage unit tests within the Rust cargo test harness. The compiled WASM footprint must fit comfortably within standard block boundaries. Ensure that your implementation strictly adheres to the project's architectural guidelines, features self-documenting code with comprehensive inline annotations, and provides solid verification proofs. Any modifications to state variables must undergo strict validation before commits.
Requirements
- Implement the reputation storage and metrics inside
contracts/reputation/src/lib.rs for Integrate Dispute History Weighting into Cumulative Score.
- Design a custom
Profile struct that stores review aggregates, completed jobs count, and active badge levels.
- Implement safe fixed-point arithmetic for averaging ratings and applying mathematical decay factors.
- Secure the score adjustment routines to strictly check that the caller is an authorized contract address.
Acceptance Criteria
- Reputation profiles load and save correctly without panicking on empty accounts.
- Badge upgrades trigger and level changes reflect immediately in the public getters.
- Vulnerability tests prove that arbitrary direct reviews from unverified public keys are rejected.
Integrate Dispute History Weighting into Cumulative Score
Description
This issue is dedicated to the technical design, implementation, and rigorous auditing of 'Integrate Dispute History Weighting into Cumulative Score' inside the Lance marketplace ecosystem, specifically focusing on the Smart Contract: Reputation & Badges component. As a Soroban smart contract task, the contributor must design robust instance or persistent storage allocations, ensure safe checked math operations, and write high-coverage unit tests within the Rust cargo test harness. The compiled WASM footprint must fit comfortably within standard block boundaries. Ensure that your implementation strictly adheres to the project's architectural guidelines, features self-documenting code with comprehensive inline annotations, and provides solid verification proofs. Any modifications to state variables must undergo strict validation before commits.
Requirements
contracts/reputation/src/lib.rsfor Integrate Dispute History Weighting into Cumulative Score.Profilestruct that stores review aggregates, completed jobs count, and active badge levels.Acceptance Criteria