Fix prefix-based cache invalidation

[Lakes41]

Difficulty: Hard

Type: Bug

Summary

Fix cache invalidation so guild-scoped and wallet-scoped entries are actually removed when invalidation helpers are called.

Current Behaviour

invalidateGuildCache builds prefix-like cache keys such as access:checkAccess:${guildId}:, then calls cache.delete(key). The cache adapter only deletes exact keys, so entries like access:checkAccess:prime-guild:premium-docs:0x... are not removed.

Expected Behaviour

Invalidation helpers should remove all matching cache entries for the target guild or wallet without requiring a full cache clear unless the adapter cannot support targeted deletion.

Suggested Implementation

Extend the cache adapter contract with an optional deleteByPrefix(prefix: string) method. Implement prefix deletion in InMemoryCacheAdapter. Update invalidateGuildCache to use prefix deletion when available and document fallback behaviour for custom adapters.

Files or Areas Likely Affected

• src/client/GuildPassClient.ts
• src/cache/cache.types.ts
• tests/
• docs/sdk-guide.md

Acceptance Criteria

• invalidateGuildCache removes all access, membership, role, and guild entries for the target guild
• InMemoryCacheAdapter supports prefix deletion
• Custom adapters can opt into targeted prefix deletion
• Fallback behaviour is documented for adapters without prefix support
• Tests prove stale guild cache entries are not returned after invalidation
• Existing clearCache behaviour remains unchanged

Additional Notes

This issue is separate from adding pluggable caching. It focuses on correctness of the cache invalidation helpers that already exist.

[MoscowDev]

I’d love to take this issue on. I’ve worked on production-ready applications and collaborated extensively through GitHub workflows. I’ll dig into the current setup, implement a solid and reliable fix, and deliver a well-tested PR. My focus is on clean, maintainable code and fast, dependable delivery.

[Yasir-TechGuy]

Hi Maintainer,

I'd like to work on this issue. I have experience designing caching layers and invalidation strategies, and I understand how stale cache entries can lead to inconsistent authorization results. I'm confident I can implement targeted prefix-based invalidation, add support in the in-memory adapter, document the fallback behavior for custom adapters, and provide thorough test coverage to ensure correctness.

ETA: 3–5 hours

Please assign this issue to 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.

[GBOYEE]

I'd like to work on this issue. I'll implement it with proper types and tests.

[GBOYEE]

I can fix the prefix-based cache invalidation. TypeScript SDK experience. Please assign me.

[grantfox-oss]

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

@GBOYEE's PR #101 was approved and merged by @Lakes41.

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

👏 Great work, @GBOYEE! Keep contributing to Adamantine-guild.