#realy already does this for user profile data and follow and mute lists and deletes and whatnot i already built a "layer 2" interface for it and have some example implementations that use shitcoins and second databases for testing the space limiting garbage collecting feature i built into the event store, it would be simple to add a layer2 that forwards queries out to other relays and caches the answer for other users as well as returning the results to the client

Replies (1)

also, the question/problem of consistency on the nostr network is one that many minds are working on one really important thing to note about this is that the lack of a prescription for a consensus to create consistency is intentional, because every type of replication strategy has tradeoffs that are only suited to some use cases and not others