feat(pow): apply WoT-distance-based PoW reductions - #779
Open
Priyanshubhartistm wants to merge 2 commits into
Open
Priyanshubhartistm 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: acc6622 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: 72.494% (+0.09%) from 72.408% — Priyanshubhartistm:feat/wot-aware-pow-policy into cameri:main |
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
nostream now has a Web of Trust graph exposing a distance-lookup API, and a relay-load-aware adaptive PoW pipeline that scales the required eventId difficulty with observed event rate. The two didn't talk to each other every pubkey faced the same computed difficulty regardless of how trusted it is.
This wires the WoT graph into the adaptive PoW pipeline via
limits.event.pow.wotThresholds: an ordered list of{ maxDistance, difficultyFactor }entries. The eligible threshold with the smallestmaxDistanceapplies, scaling the computed difficulty bydifficultyFactor(0 bypasses eventId PoW entirely, 1 requires the full computed difficulty, fractional values in between). A pubkey outside the trust graph, or beyond every configured threshold, always pays the fullcomputed difficulty. Disabled by default (no thresholds configured), and only ever consults the WoT graph when at least one threshold is configured, so relays not using this stay unaffected.
EventMessageHandler.canAcceptEvent()is nowasyncto support the distance lookup every other check inhandleMessage's chain was already async, so this keeps the same style rather than special-casing one synchronous check.Related Issue
Closes #778
Motivation and Context
A fixed adaptive difficulty treats a well-connected community member the same as a completely unknown pubkey under load. Reducing (or waiving) the PoW requirement for pubkeys inside the operator's trust circle means a trusted author can keep posting instantly during a spam flood, while an unknown pubkey still has to prove it isn't a bot.