get_creation_deposit uses raw Enum as Key

[hman38705]

Description
The function get_creation_deposit (Line 196) and its setter (Line 203) use ConfigKey::CreationDeposit directly as a storage key. In Soroban, enums used as keys in instance or persistent storage must be properly handled to avoid collisions with other instance variables or metadata. Using a raw enum variant as a top-level key without a formal wrapping structure is poor practice and risky.

Requirements and context

• Formalize the storage key structure for all configuration parameters.
• Ensure no collisions with other data types in the instance storage.

Suggested execution

• Fork the repo and create a branch: git checkout -b fix/issue-81-config-keys
• Refactor the configuration storage pattern.

Implementation changes

• Update markets.rs (Line 199 & 207) to use a consistent DataKey::Config(ConfigKey) pattern.

Test and commit

• Verify that setting the creation deposit does not overwrite other persistent counters like MarketCount.

Example commit message
fix: use structured DataKey for configuration storage to avoid collisions

Guidelines

• Storage safety.
• Timeframe: 12 hours.

[Uche44]

@Uche44 has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Good day.

Let me handle this for you.

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

[manuelusman73-png]

@manuelusman73-png has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hi Maintainer Can I work on this issue

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

[drips-wave]

Congratulations, @manuelusman73-png! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on March 30, 2026.

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

[drips-wave]

This issue has been completed by @manuelusman73-png as part of the Stellar Wave Program's 3rd Wave 🥳

😎 @manuelusman73-png: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.