Implement Soroban Contract Storage Key Namespace Collision Detection

[temma02]

Description

Build collision detection for Soroban contract storage keys to prevent template-generated contracts from accidentally using conflicting storage namespaces that could corrupt contract state.

Requirements and Context

• Correctness: Storage key collisions must be detected before deployment
• Testing: Test collision detection across template configurations
• Documentation: Document the storage key namespacing scheme

Suggested Execution

Branch: feat/issue-080-soroban-storage-key-collision-detection

Implement Changes

• Add storage key namespace analysis to the Soroban contract validator
• Detect when two generated storage keys would collide
• Reject configurations that produce colliding storage keys
• Surface a clear error indicating which keys collide

Test and Commit

• Test detection of colliding storage keys
• Test acceptance of non-colliding configurations
• Document the storage key namespacing scheme

Example Commit Message

feat(soroban): add storage key namespace collision detection

- Analyze generated storage keys for collisions
- Reject configurations with colliding keys
- Surface clear collision error messages

Guidelines

• Analyze keys statically before deployment
• Provide actionable errors indicating the colliding keys
• Align with Soroman storage key conventions

[Darkdante9]

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

Hi, can I work on this issue please??

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

[drips-wave]

Congratulations, @Darkdante9! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @Darkdante9: 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 @Darkdante9 as part of the Stellar Wave Program's 5th Wave 🥳

😎 @Darkdante9: 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.