Add helper for generating a stable cache key from a creator ID and query param set

[Chucks1093]

Summary

Creator list and detail responses are cached, but the cache key must be stable regardless of the order query params appear in the URL. A shared helper that normalizes and hashes the param set into a deterministic cache key should replace any inline key construction.

Scope

• Add buildCacheKey(base: string, params: Record<string, unknown>): string helper
• Sorts param keys alphabetically before hashing so order does not matter
• Returns a fixed-length string suitable for use as a cache key
• Add unit tests confirming identical params in different order produce the same key and different params produce different keys

Acceptance Criteria

• Same params in different order produce identical cache key
• Different params produce different cache keys
• Output is a fixed-length string

ETA: 12 hours

---

Coordinate on Telegram

[abioye-emma]

Hi, I’m a full-stack Web2 & Web3 developer with open-source contribution experience, and I’d be glad to work on this issue.

[Empire050]

Hi boss,
​I'd love to work on this issue. It seems like a great fit, and I'm ready to dive into the codebase to get it resolved. Could you please assign it to me?
​Thanks.

[Killerjunior]

I’ve reviewed the issue details and documentation, and I understand the problem statement and expected outcome. Please assign this task to me — I’m ready to start working on it.

[grantfox-oss]

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

Next steps:

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

Good luck! Track your progress on GrantFox.