Add exponential backoff and configurable max retries to useOptimisticData

[Jagadeeshftw]

📌 Description

useOptimisticData (src/shared/hooks/useOptimisticData.ts) retries failed fetches up to a hardcoded max of 5 at full speed with no backoff, and never exposes the retry count to callers. This can hammer a failing backend.

💡 Why it matters: Immediate full-speed retries can amplify outages and exhaust the API.

🧩 Requirements and context

• Add exponential backoff (with jitter) between retries.
• Make max retries and base delay configurable via options.
• Expose retryCount/isRetrying from the hook.
• Ensure aborts cancel scheduled backoff timers.

Non-functional requirements

• Must be secure, tested, and documented.
• Should be efficient and easy to review.

🛠️ Suggested execution

1. Fork the repo and create a branch

git checkout -b feat/useoptimistic-backoff

2. Implement changes

• Write/modify the relevant source: src/shared/hooks/useOptimisticData.ts
• Write comprehensive tests: src/shared/hooks/useOptimisticData.test.ts
• Add documentation: TSDoc @example
• Include TSDoc doc comments
• Validate security assumptions: timers cleared on unmount/abort

3. Test and commit

• Run tests:

npm run test

• Cover edge cases: backoff timing (fake timers), abort during backoff, custom max
• Include test output and security notes in the PR description.

Example commit message

feat(hooks): exponential backoff + configurable retries in useOptimisticData

✅ Acceptance criteria

• Retries use exponential backoff with jitter
• Max retries/base delay configurable
• retryCount exposed
• Timers cleared on abort/unmount; tests assert timing

🔒 Security notes

Avoid retry storms; ensure backoff timers are always cleaned up.

📋 Guidelines

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

[YfengJ]

Hi maintainers, I would like to apply for this issue.

If assigned, I can add configurable retry limits and exponential backoff with jitter to useOptimisticData, expose retryCount/isRetrying, ensure aborts clear scheduled timers, and add focused hook tests around retry timing and cancellation.

I will wait for assignment or explicit maintainer/GrantFox confirmation before cloning, implementing, or opening a PR.

[leocagli]

I've studied the codebase and I'm ready to tackle this. Please assign me.

[clintjeff2]

Hello, I have 6 years of experience working on tasks like this and handling similar challenges across backend, frontend, and smart-contract development. I have carefully read and fully understood the task requirements, and I am confident I can deliver a clean, efficient, and well-tested solution promptly. I always ensure high-quality implementation, maintainability, and adherence to best practices.

Pull request in 5 hours.