Performance: Redis caching layer for hot reads (dashboard, leaderboard, campaign metadata)

[joelpeace48-cell]

Context

Hot read endpoints recompute on every request. A cache with correct invalidation is needed to scale
reads without hammering the DB/chain.

Scope

• Cache hot reads in Redis with TTL + event-driven invalidation on writes/indexer updates.
• Stampede protection (single-flight / lock) on cache miss.
• Cache hit-rate metrics.

Acceptance criteria

• Hot endpoints serve from cache with correct invalidation; measurable DB load reduction.

Verification

• Load test shows high hit rate and that writes invalidate stale entries.

[jesutobaadedejidev]

I would like to work on this. Do assign it to me.

[gloskull]

Hello, I have 4 years of experience delivering solutions for projects like this, covering backend, frontend, and smart contract development. After carefully reviewing your requirements, I have a clear understanding of the task and am confident in my ability to deliver a clean, efficient, and thoroughly tested solution on time. I prioritize code quality, maintainability, and industry best practices throughout the development process. My PR will be submitted in under 10hours.

[oscar2004JT]

I have experience building backend applications with Laravel, PHP, PostgreSQL, Redis, Docker, and REST APIs. I have worked on performance optimization, caching, database design, and scalable application architecture. For this issue, I would review the current implementation, identify the hot read endpoints, implement Redis caching with TTL and event-based invalidation, add cache stampede protection, and expose cache hit-rate metrics. I can submit a pull request after reviewing the codebase.