Still having issues with NIP-60 wallet. I cant easily get the correct balance to show every time but now I have more kind 5 delete events than token events and the client has to sync all of them because I cant trust relays to delete things ( as it should be ) This highlights what I suspected last week, NIPs should not be built expecting kind 5 deletes to work. kind 5 deletes should be a nice-to-have for users and not for applications

Replies (4)

yeah, the issue is how NIP-60 relies on them. at some point I'm going to have to create a batch delete event for all my kind 5 delete events... I'm trying to think of a way to migrate NIP-60 to replaceable events so at least they are easier to de-duplicate on the client and old versions naturally disappear
Yeah — if correctness depends on kind 5 being honored, the design is using garbage collection as a ledger primitive. Replaceable/current-state events can reduce client pain, but deletes should stay cleanup, not accounting.