[P1] Implement Soroban repayment tracking contract logic

[Obiajulu-gif]

Priority

P1

Difficulty

Advanced

Task

Add repayment tracking logic to the ChainMove Soroban contract workspace.

Expected behavior

The contract should support:

• assigning a driver to a pool or vehicle
• recording repayment amount
• tracking total repaid
• tracking outstanding balance
• defining overpayment behavior
• querying repayment summary

Acceptance criteria

• Repayment can be recorded for an active driver contract.
• Outstanding balance updates correctly.
• Overpayment behavior is defined and tested.
• Unauthorized updates are rejected.
• Query function returns repayment summary.

Test requirement

Add tests for first repayment, multiple repayments, full repayment completion, overpayment behavior, and unauthorized caller rejection.

Evidence required

• Screenshot of cargo test passing.
• Screenshot of repayment summary output from tests.

Commands

cargo test
npm run lint
npm run build

[Yourbigmike]

i would like to work on this issue as a web 3 analysis and i solve complex smart contract issues

[IdokoMarcelina]

Hello, please assign me this issue. i have experience with frontend blockchain integration and smart-contract

[Emmyt24]

Hi team, I'd like to work on this issue.
I'm a full-stack developer experienced in TypeScript, Rust, and smart contract development across EVM and Soroban/Stellar ecosystems. I've built and shipped production systems covering backend APIs, frontend interfaces (Next.js, React), CI/CD pipelines, and onchain protocols — so I'm comfortable working across whatever layer this issue touches.
My approach
I'll start by reproducing the issue locally and reading the surrounding code to understand context and constraints. I'll scope the fix tightly to avoid unnecessary churn, write or update tests to cover the change, and make sure linting, formatting, and existing CI checks all pass before opening a PR. If anything in the issue is ambiguous, I'll flag it early rather than guess.
What you can expect
A single clean PR with a clear description linking back to this issue. Minimal, well-tested changes that follow the project's existing conventions. Fast turnaround — I'm available to start immediately and responsive to review feedback.
Happy to discuss the approach further if needed. Looking forward to contributing.

[ryzen-xp]

Hi maintainers 👋
I’m a blockchain developer with strong expertise in Stellar, Rust,TS and Stellar SDK integrations. I’ve worked on multiple Stellar-based smart contract and backend systems.

I understand the scope of this issue and can deliver a reliable, production-quality solution with proper tests and documentation.
Plz assign me !!

ETA: 24 hours

[Marodrumz]

Hi ChainMove team,

I would like to work on this issue because repayment tracking is a core part of the ChainMove contract logic. If drivers are assigned to pools or vehicles, the contract needs to accurately track repayment progress, outstanding balance, completion status, and overpayment behavior in a way that is secure, testable, and predictable.

My plan is to study the existing Soroban contract workspace first, identify the current driver, pool, vehicle, authorization, and storage patterns, then implement repayment tracking in the same style as the existing codebase.

I will focus on:

• Assigning a driver to a pool or vehicle using the existing contract structure
• Recording repayment amounts for an active driver contract
• Tracking cumulative amount repaid
• Updating outstanding balance correctly after each repayment
• Defining clear overpayment behavior
• Rejecting unauthorized repayment updates
• Adding a query function that returns repayment summary
• Adding tests for first repayment, multiple repayments, full repayment completion, overpayment behavior, and unauthorized caller rejection
• Running cargo test, npm run lint, and npm run build
• Providing screenshots of passing tests and repayment summary output as requested

I have experience with backend systems, financial-style state tracking, Rust/Soroban-style smart contract workflows, and correctness-focused validation. I understand that repayment logic must be handled carefully because mistakes in totals, balances, authorization, or overpayment rules can create financial and contract-state inconsistencies.

If assigned, I will submit a focused PR with clean contract changes, complete repayment tests, evidence screenshots, and no unrelated changes.

[Jess52487]

GM boss, I would love to work on this issue please assign me.

[grantfox-oss]

🦊 GrantFox — @Jess52487 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 #12)
2. Your PR will be reviewed by the Chainmove maintainers

Good luck! Track your progress on GrantFox.