Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feat: Spot check miners against twitter api false/true #237

Closed
2 tasks
Tracked by #2
Luka-Loncar opened this issue Sep 4, 2024 · 0 comments · Fixed by #265
Closed
2 tasks
Tracked by #2

Feat: Spot check miners against twitter api false/true #237

Luka-Loncar opened this issue Sep 4, 2024 · 0 comments · Fixed by #265
Assignees
Labels
feature New feature or task

Comments

@Luka-Loncar
Copy link
Collaborator

Luka-Loncar commented Sep 4, 2024

Problem

The network currently does not validate the result of the data scraping. This is especially problematic with X/Twitter data, which seems possible to fake quite easily.

Proposed solution

We can spot-check miners periodically. Data could be validated by validators which can double-check if the content of the tweet is equal to the one that can be fetched with the same ID via twitter. Essentially, validators should check time to time if some of the requests are correct - that is if the tweet returned exist, is valid, and the content reported by the worker is the content that can be fetched using the Twitter API.

Validators should then flag and be able to blacklist miners which are abusing the service.

acceptance criteria

  • Validators do not need to provide a twitter account credentials
  • Checking twitter content should happen on the public channel
@Luka-Loncar Luka-Loncar added the feature New feature or task label Sep 4, 2024
@grantdfoster grantdfoster self-assigned this Oct 8, 2024
@grantdfoster grantdfoster linked a pull request Oct 10, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or task
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants