feat: implement resolution delay and dispute window before final payout

[greatest0fallt1me]

Description:

Implement a configurable resolution delay (dispute window) after event end during which disputes can be raised; payouts occur only after the window closes or dispute is resolved.

Requirements and Context:

• Must be secure, tested, and documented
• Should allow admin to set dispute window duration per event (or global)
• Should allow resolution to be proposed but not final until window ends (or dispute resolved)
• Should allow users/admins to raise disputes during the window
• Should trigger payout only when window closed and no unresolved dispute
• Should emit events for dispute window and finalization
• Must integrate with existing dispute and payout logic

Suggested Execution:

1. Fork the repo and create a branch

   git checkout -b feature/resolution-delay-dispute-window

2. Implement changes

   • Write contract: src/lib.rs (dispute window, finalize_after_window)
   • Update disputes and resolution modules
   • Update types, storage, events
   • Add documentation and NatSpec-style comments

3. Test and commit

   • Run tests; cover window open/close, dispute during window, payout after
   • Include test output and security notes

Example Commit Message:

feat: implement resolution delay and dispute window before final payout

Guidelines:

• Minimum 95 percent test coverage
• Clear documentation
• Timeframe: 96 hours

[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

[Georgechisom]

@Georgechisom has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hi, I love to work on this issue and deliver an excellent result, please help assign it to me.

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

[soma-enyi]

@soma-enyi has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Gm Gm Maintainer!!
I would like to work on this issue!!!

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

[Villarley]

@Villarley has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hey team! i have great experience with this repo, would love to contribute on this one!

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

[drips-wave]

Congratulations, @Villarley! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on January 31, 2026.

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