Add helper for reading the current protocol fee bps without duplicating storage key logic

[Chucks1093]

Summary

The protocol fee bps value is read from persistent storage in multiple contract functions, each constructing the storage key inline. A shared read helper should centralise this to eliminate duplication and make fee config reads consistent.

Scope

• Add read_protocol_fee_bps(env: &Env) -> u32 helper
• Helper should panic with a descriptive message if the value is absent (contract not initialized)
• Replace all inline protocol fee bps reads with the helper
• Add unit tests: initialized contract returns configured bps, uninitialized contract panics with correct message

Acceptance Criteria

• Helper returns correct bps from storage
• Helper panics with descriptive message when uninitialized
• All inline reads replaced with helper
• Unit tests for initialized and uninitialized states

ETA: 12 hours

---

Coordinate on Telegram

[MoscowDev]

I’d love to take this issue on. I’ve worked on production-ready applications and collaborated extensively through GitHub workflows. I’ll dig into the current setup, implement a solid and reliable fix, and deliver a well-tested PR. My focus is on clean, maintainable code and fast, dependable delivery.

[MoscowDev]

I’d love to take this issue on. I’ve worked on production-ready applications and collaborated extensively through GitHub workflows. I’ll dig into the current setup, implement a solid and reliable fix, and deliver a well-tested PR. My focus is on clean, maintainable code and fast, dependable delivery.

[olaayoade91-byte]

hello i would like to work on this please assign me

[Damilorlar]

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

I would love to work on this projects.

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

[mariamfehintola95-lgtm]

@mariamfehintola95-lgtm has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi, I’ve carefully reviewed the issue and understand what’s required. I’m confident I can implement a high-quality solution that meets the acceptance criteria. I’d appreciate being assigned this issue.

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

[Power70]

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

Hi Maintainer,
I can work on this issue.
Kindly assign it to me.
Thank you.

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

[Johnsmichael150]

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

I would love to work on this projects.

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

[drips-wave]

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

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