Cache problem in Primal client

Unable to update my profile, after many attempts I conclude this is a cache problem in Primal client - here is my bug report
Cache problem in Primal client

If you use primal.net, beware as you may see an old profile for this account and it won’t update.

On primal.net, @9x4u…rsw7 looks like “MrMeeseeks” with a profile from 2025!

On jumble.social and ditto.pub the same account shows “m22seeks” with its current profile. So the account is fine — except Primal app is showing old data.

Why? because of Primal’s caching server: that caching server is still holding an old copy of the profile from October 2025. That old copy doesn’t exist on any relay anymore (I checked relay.primal.net, nos.lol, ditto and nostr.mom — none of them have it).

The current profile is on Primal’s own relay and on nos.lol.
I even signed a brand new profile update and published it to primal, nos, damus and snort. Primal’s cache never picked it up — I watched it for about 25 minutes and nothing changed.

Nothing on from the user side can fix this. That cache only answers read requests, there’s no refresh button, no way to clear an entry.
It looks like this account’s profile got stuck in the cache, so it needs a fix from Primal (drop the old entry and re-read the profile from their own relay).

Not a Nostr problem — just a cache problem in Primal client.


Write a comment