Add test coverage for Slashing mechanics

[meshackyaro]

Description

This issue aims to address the implementation of Add test coverage for Slashing mechanics.

The core objective is to: Simulate multiple dispute rounds where a juror votes maliciously and verify their balance decreases.

By completing this feature, we will ensure that the TrustFlow protocol maintains its high standards for security, usability, and decentralized logic. This issue requires careful attention to the Smart Contracts architecture and adherence to the existing project conventions.

When picking up this issue, please ensure you document any new dependencies or architectural decisions made during development.

Component

Smart Contracts

Difficulty

🟡 Medium

Tasks

• Review Soroban architecture and soroban-cli usage
• Implement Rust logic for: Add test coverage for Slashing mechanics
• Write comprehensive unit tests in Rust
• Ensure proper event emission for indexing
• Run cargo fmt and cargo clippy
• Verify soroban contract build successfully compiles to WASM without bloating size

Acceptance Criteria

• Feature accurately implements the objective: Simulate multiple dispute rounds where a juror votes maliciously and verify their balance decreases.
• Any PR that introduces TypeScript/Rust errors is automatically blocked
• CI pipeline runs in under 3 minutes per PR
• Code is properly reviewed and approved by codeowners

Estimated Time

4-8 hours

[YfengJ]

I would like to apply for this issue.

If assigned, my plan is to keep the change focused on test coverage for the existing slashing behavior: add Rust unit/integration tests that simulate repeated dispute rounds, drive a malicious juror vote path, assert the juror balance decreases across rounds, and verify any expected slashing event/state updates. I would avoid changing contract behavior unless the tests expose a real defect, and I would run cargo fmt, cargo clippy, the relevant Rust tests, and the contract build before opening a PR.

I will wait for maintainer or GrantFox assignment/confirmation before starting implementation or opening a PR.

[Godbrand0]

I would like to work on this issue.

I have experience building and testing Rust-based smart contracts and understand the importance of validating incentive and penalty mechanisms in decentralized systems. For this task, I will review the existing Soroban contract architecture and dispute resolution flow, then implement comprehensive Rust tests that simulate multiple dispute rounds where a juror repeatedly votes maliciously and verify that their balance is reduced correctly after each round.

My implementation will include:

Review of the current slashing and dispute logic.
Rust unit tests covering multiple malicious voting rounds.
Validation of balance reductions and cumulative slashing behavior.
Verification of relevant event emissions for indexing.
Running cargo fmt, cargo clippy, and all tests.
Ensuring successful Soroban WASM compilation without unnecessary size increases.
Documentation of any architectural decisions or new dependencies introduced.

The final solution will satisfy the acceptance criteria while maintaining code quality, protocol security, and CI performance requirements.

[grantfox-oss]

🦊 GrantFox — @Godbrand0 has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #20)
2. Your PR will be reviewed by the trustflow-protocol maintainers

Good luck! Track your progress on GrantFox.

[YfengJ]

Thanks for the update. I’ll step back here and leave this issue to @Godbrand0 since it has been assigned. Good luck with the implementation.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@Godbrand0's PR #31 was approved and merged by @meshackyaro.

🏆 @Godbrand0: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (48 total points). Track your full progress on GrantFox.

👏 Great work, @Godbrand0! Keep contributing to trustflow-protocol.