No credit rate change count getter in FarmingPool

[ritaifeoluwa]

Description

The FarmingPool contract does not have a way to query the total number of credit rate changes performed. While individual changes are trackable via events, there is no aggregate count.

Current behavior

No credit rate change count.

Expected behavior

Maintain a running count:

fn credit_rate_change_count(env: &Env) -> u32 {
    env.storage().instance().get(&DataKey::CreditRateChangeCount).unwrap_or(0)
}

Increment during set_credit_rate.

Why this matters

Protocol analytics need credit rate change counts for governance monitoring.

Labels

enhancement, farming-pool, good first issue

[anifast-123]

@anifast-123 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

• Goal: Write a 1-2 sentence application to work on a specific GitHub issue. * Repository: SmartDropLabs/smartdrop-contracts * Issue Title: No credit rate change count getter in FarmingPool * Issue Description: Add a way to query the total number of credit rate changes. Implement a getter and increment it during set_credit_rate. * Constraints: * Natural tone. * 1-2 sentences. * Mention a concrete implementation/testing detail. * No markdown. * No greetings to a

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

[payfoxX]

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

I love to fix this issue, kindly assign it to me. Thanks

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

[axeroofficialtournament-del]

@axeroofficialtournament-del has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello Maintainer, I have gone through this issue documentation and i am interesting and would love to be assigned this particular issue.

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

[Muyideen-js]

@Muyideen-js has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi, I can fix this

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

[ExcelDsigN-tech]

@ExcelDsigN-tech has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I'm a full-stack developer with hands-on experience across Next.js, Node.js, NestJS, React, and TypeScript, and I also specialize in smart contract development using Rust and Soroban. I build end-to-end, from polished frontends to robust backends to on-chain logic, with a strong focus on clean, maintainable code that works in production, not just in isolation. I communicate progress consistently and keep things fully transparent throughout. I'm confident I can deliver within 12 hours.

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

[drips-wave]

Congratulations, @ExcelDsigN-tech! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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