Not hard with what I’ve built. My original Nostr goal was literally how do we model the Nostr network and events to keep a mostly accurate database or state of the universe. There are so many ways the data can go wrong… been slowly protecting against them.

Examples like newer event seen before older, deletions, double counting, all aggregation, replacing events, missing data, invalid data, spam, and I use an event stream based architecture.. so some consumers have to happen earlier - depend on upstream processes (only one actually :p).

But what I’ve been working on recently is the stats roll up and aggregation consistency side. Pretty tough to tackle, but I’ve got a solid approach now. And means dashboards can be fast. But means more processing and data to store too.

Old now and pretty different.. but this is how it started. https://github.com/blakejakopovic/NostrEventPlayground