No, because I still want wot numbers if the server goes down

Yes, that'd work for Community Apps. As the communities' job and effect is that they do most of the spam prevention + user validation. Page rank is more rarely needed for the individual user and it's fine if servers go down sometimes. I can fall back on a light local "user network" calculation by using the Communities and Contacts and going max two level deep (ideally just one even, which'd be fine).

I'm not too worried about the server lying, since ideally users could choose their provider or maybe run their own. The way I see it there are two uses for pagerank or "WoT" 1. The client wants to hide content that is outside of the users social network (subjective distance or score) I'm not sure how this could work without the server sending the whole graph (probably Mb of data) or the client making API requests to check each pubkey (not great for privacy) For this case I think the simple kind:3 WoT is good enough, at least for now 2. The client wants to sort events or pubkeys by "reputation" or score Vertex already does this well for user search ( query -> pubkey[] ) but it may be useful to have some kind of generic sorting method for events to allow a client to sort replies ( again probably bad for privacy ) I tend to agree with @hodlbod. I want my client to work without a dependency on a server. but I'd also like to integrate with some kind of server to improve performance or to get better sorting / filtering results