Thats the plan. We’re thinking of upgrading replaceable events to versioned events with a pruneable history. It shouldn’t be too disruptive in theory, it just changes replaceability with versions.
Login to reply
Replies (1)
nm i think i understand what you mean now. The issue of replacing contact lists with reduced checkpoints is another problem which is more disruptive and difficult, the one im talking about here is a simpler problem to tackle.
This came up because people were starting to use a-tags as zap and like targets which seemed very wrong. I wrote up why here:
GitHub
update nip-57 zap receipt spec to include 'a' tag by huumn · Pull Request #800 · nostr-protocol/nips
@verbiricha reached out letting us know SN's zapper wasn't including a tags in the zap receipt.
Figured it should be added to the spec for future z...