#088: Time-Locked Milestone Vesting Vaults

[bakarezainab]

#88: Time-Locked Milestone Vesting Vaults

Overview

Create time-locked vesting vaults for approved milestone payouts, allowing a holding period during which payouts can be disputed.

Objectives

• Hold payout amounts in a vesting state for a safety window.
• Let admins/creators open disputes during the vesting period.
• Complete release if no dispute is opened within the window.

Acceptance Criteria

• Vesting vault mappings and time checks.
• Claim blocks and dispute handlers during vesting.
• Unit tests validating delayed payouts.

[praisesokoyebomfrancis]

Hi team,

I would like to apply to work on #88 #79: Time-Locked Milestone Vesting Vaults for LatterFix-Smart-contract.

Motivation & Experience
Implementing secure time-locked mechanics and dispute safety windows is critical for robust DeFi protocol architecture. I have experience developing and testing smart contracts with delay locks, access control, and dispute/freeze mechanisms.

Proposed Implementation Plan
Vesting Vault Architecture: Implement state mappings and timestamp verification logic to safely hold milestone payouts for the duration of the vesting window.

Dispute & Claim Handlers: Create admin/creator hooks to flag disputes during vesting and ensure claim executions are strictly blocked while under dispute or prior to lock expiry.

Automated Release: Build the release logic to automatically finalize and release funds once the safety window passes without active disputes.

Testing Suite: Write unit and integration tests validating edge cases around timestamp boundaries, unauthorized claims, and dispute triggers.

I am ready to start working on this immediately upon assignment!

[Securify001]

Hi. I am a web3 fullstack developer. Kindly assign this issue to me. I have 5+ years of Rust and smart contract development experience with deep expertise in Soroban, time-locked escrow mechanisms, vesting vault patterns, and implementing dispute resolution windows for milestone-based payouts.

My approach to this implementation:
Design a vesting vault contract with mappings that store for each vault: beneficiary, amount, token, release_ledger, status (Pending, Released, Disputed), and dispute_resolution fields to track the dispute lifecycle

Implement create_vault to lock payout amounts in the contract with a configurable safety window, storing the release_ledger = current_ledger + safety_window and setting status to Pending

Implement claim requiring beneficiary authorization, checking that current_ledger >= release_ledger and the status is Pending, then releasing the full amount and updating status to Released

Implement open_dispute(vault_id) callable by admin/creator during the vesting period (before release_ledger), pausing the release timer, setting status to Disputed, and emitting DisputeOpened with a resolution deadline

Implement resolve_dispute(vault_id, outcome) with admin authorization, setting status to Released (if outcome favors beneficiary) or allowing funds to be returned to the original depositor (if outcome favors admin), with clear event emissions for transparency

Write comprehensive unit tests validating: delayed payouts release correctly after the safety window, disputes can be opened during vesting, payout is blocked when disputed, resolution paths work correctly, and unauthorized claim/dispute attempts panic

Ensure all arithmetic uses checked methods (checked_add, checked_sub) for overflow protection, and achieve comprehensive test coverage on boundary conditions. I am ready to deliver this time-locked vesting vault contract within 4-5 hours with full test coverage and thorough documentation

[Mainnet-ops]

Hi, I’d like to work on #79: Time-Locked Milestone Vesting Vaults.

I’ll implement the vesting vault mappings and time checks, prevent claims during the vesting period, add dispute handling for admins/creators, and ensure undisputed payouts are released after the safety window.

I’ll also add unit tests covering delayed claims, disputes, and successful releases after vesting.

I’m happy to take this up and keep the implementation focused and consistent with the existing codebase.

[grantfox-oss]

🦊 GrantFox — @Mainnet-ops has been assigned to this issue as part of the Third Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #88)
2. Your PR will be reviewed by the LatterFixxx maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Third Campaign campaign!

@Mainnet-ops's PR #99 was approved and merged by @bakarezainab.

🏆 @Mainnet-ops: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (376 total points). Track your full progress on GrantFox.

👏 Great work, @Mainnet-ops! Keep contributing to LatterFixxx.