feat(wot): add web of trust graph service for NIP-02 follow distance - #745
Open
Priyanshubhartistm wants to merge 2 commits into
Open
feat(wot): add web of trust graph service for NIP-02 follow distance#745Priyanshubhartistm wants to merge 2 commits into
Priyanshubhartistm wants to merge 2 commits into
Conversation
Signed-off-by: Priyanshubhartistm <bhartipriyanshustm@gmail.com>
Signed-off-by: Priyanshubhartistm <bhartipriyanshustm@gmail.com>
🦋 Changeset detectedLatest commit: edece5a The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Collaborator
|
Coverage is 71.632% — Priyanshubhartistm:feat/wot-graph-service into cameri:main. No base build found for |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds a WotService that builds a trust graph rooted at an operator-configured seed pubkey, ingesting NIP-02 contact lists (kind 3). The graph is updated in real time as kind-3 events come in, exposes
getDistance(pubkey)isTrusted(pubkey)for other parts of the relay to query, and supports a configurable trust depth plus a minimum-followers threshold for anything past direct (1-hop) follows.Storage is Redis-backed (per-pubkey follow sets), with the in-memory graph rebuilt from Redis on demand and lazily primed from already-stored contact-list events in Postgres when a pubkey's follow set isn't cached
yet. Pure logic only, matching the issue's scope no background refresh worker is wired up in this PR.
Related Issue
Closes #626
Motivation and Context
Nostream has no way to filter or weight events by social trust today any pubkey can publish regardless of whether the relay owner actually knows them. This is the foundation piece: a queryable trust graph that later anti-spam work (adaptive PoW reductions, WoT-gated content reporting) can build on top of.