Issue 5: Optimistic State Mutators and Rollback Controllers for Contract Adjustments

[elizabetheonoja-art]

Scope

File: src/hooks/useEscrow.ts

Problem

When users submit tariff updates or fund deposits to Soroban contracts, the 3-5 second block confirmation window leaves the UI in a loading state. If the transaction fails or is dropped, there is no automatic rollback mechanism, leaving the UI in a permanently incorrect state.

Requirements

1. Implement an optimistic mutation queue where each mutation has states: idle → pending → confirmed | failed.
2. On submit(data): immediately apply optimistically, call onChainSubmit(data), mark confirmed on success or failed on failure with onRollback(data) to revert.
3. Expose rollback(mutationId) that manually reverts a pending mutation.
4. Expose retry(mutationId) that re-submits a failed mutation.
5. Track pendingCount for UI badge display.

Resolution Strategy

• useRef<Set> to track active mutations and prevent duplicate rollbacks.
• Store mutation history in state with max 50 entries.
• Each mutation carries submittedAt and confirmedAt timestamps.

Tags

hooks, optimism, rollback, contract

[Jess52487]

Hello boss, I would love to work on this issue please assign me.

[grantfox-oss]

🦊 GrantFox — @Jess52487 has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

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

Good luck! Track your progress on GrantFox.

[grantfox-oss]

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

@Jess52487's PR #34 was approved and merged by @elizabetheonoja-art.

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

👏 Great work, @Jess52487! Keep contributing to Utility-Protocol.