Add Contract-Level Feature Flags

[Baskarayelu]

Description:

Introduce simple on-chain feature flags for gradual rollouts.

Requirements

• Define feature flag keys (e.g. "strict_goal_dates").
• Store flags via config contract or instance storage.
• Gate at least one non-critical behavior behind a flag.

Acceptance Criteria

• Feature flag mechanism implemented
• At least one feature behind a flag
• Docs explain usage

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[Henrichy]

@Henrichy has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hello 👋

I’d like to implement the contract-level feature flags for Remitwise-Contracts. I have experience designing configurable smart contract systems that support gradual rollouts while maintaining security and clarity.

For this task, I will:
• Define structured feature flag keys (e.g., strict_goal_dates) using a clear and extendable enum or key pattern.
• Store flags in instance storage or the config contract, ensuring minimal storage overhead and clean retrieval logic.
• Implement a reusable internal helper (e.g., is_feature_enabled(flag)) to centralize flag checks.
• Gate at least one non-critical behavior (such as goal date validation logic) behind the feature flag.
• Add thorough inline documentation and update the contract docs explaining how to set, toggle, and use feature flags safely.

The implementation will prioritize backward compatibility, audit clarity, and future extensibility for additional flags.

I can deliver a clean, well-documented, and secure feature flag mechanism ready for controlled production rollouts.

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

[drips-wave]

Congratulations, @Henrichy! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

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

[Henrichy]

@Baskarayelu please review this PR