Join our community: https://t.me/+DOylgFv1jyJlNzM0
Why this matters
claimable.service.ts derives its cache key primarily from streamId; if two streams ever share the same numeric id across different token deployments the cache could serve a stale claimable amount for the wrong token, silently corrupting displayed balances.
Acceptance criteria
Files to touch
backend/src/services/claimable.service.ts
Out of scope
Does not change the underlying claimable calculation formula.
Why this matters
claimable.service.ts derives its cache key primarily from streamId; if two streams ever share the same numeric id across different token deployments the cache could serve a stale claimable amount for the wrong token, silently corrupting displayed balances.
Acceptance criteria
Files to touch
backend/src/services/claimable.service.tsOut of scope
Does not change the underlying claimable calculation formula.