You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create a service that checks the latest DeVouch attestation data and updates the project’s verification points depending on which attester orgs issued each vouch.
Giveth Verifiers = 1 point
TRAINED Giveth Verifiers = 3 points
Core Reviewer = 30 points
Verification levels
Projects must have a certain amount of points
Verification level 1
For the purposes of staging/testing the vouching threshold will be 2. So if a project has receive 2 eligible vouches its project status should be changed to Verified level 1.
e.g If a project receives 2 vouches from a Giveth Verifier it is automatically verified within 24 hours
Ideally we can handle checking this data real-time as the DeVouch indexer processes on-chain events. If we are not able to handle real-time events then a delay of up to 12 hours is acceptable.
Verification level 2
For the purposes of staging/testing the vouching threshold will be 2. So if a project has received 2 eligible vouches its project status should be changed to Verified level 1.
e.g If a project receives 2 vouches from a Giveth Verified it is automatically verified within 24 hours
Ideally we can handle checking this data real-time as the DeVouch indexer processes on-chain events. If we are not able to handle real-time events then a delay of up to 12 hours is acceptable.
Notes
on every event that happens we can make a hook in the impact-graph that can be called - we should protect this by some password so only 1 BE can call it to push information to impact-graph
create list of updated statuses, create API in DeVouch BE, fetch projects that are updated by impact-graph
Otherwise we check data at least every 12 hours and update projects’ status
Requirements
The number of points required to become automatically verified can be easily changed by a developer
The number of points each type of Verifier is worth can be easily changed by a developer
changing the “points threshold” does not retroactively affect projects’ verified status
we can remove the status, keep track of time of project has been updated, fetched project has been updated until 1 hour ago, only fetch projects from after that. If we change the threshold
If a Giveth Verifier changes their vouch or revokes it, and the project then becomes under the threshold then we unverify the project.
when the amount of vouches a project receives attains the set threshold the project's status changes to "Verified" within a maximum delay of 12 hours
If a project's vouches are revoked and it falls under the threshold then the project loses it verified status within a maximum delay of 12 hours.
The text was updated successfully, but these errors were encountered:
divine-comedian
changed the title
Check project vouching data and update project's status
Check project vouching data and update project's verification points
Aug 20, 2024
Create a service that checks the latest DeVouch attestation data and updates the project’s verification points depending on which attester orgs issued each vouch.
Verification levels
Projects must have a certain amount of points
Verification level 1
For the purposes of staging/testing the vouching threshold will be 2. So if a project has receive 2 eligible vouches its project status should be changed to Verified level 1.
Ideally we can handle checking this data real-time as the DeVouch indexer processes on-chain events. If we are not able to handle real-time events then a delay of up to 12 hours is acceptable.
Verification level 2
For the purposes of staging/testing the vouching threshold will be 2. So if a project has received 2 eligible vouches its project status should be changed to Verified level 1.
Ideally we can handle checking this data real-time as the DeVouch indexer processes on-chain events. If we are not able to handle real-time events then a delay of up to 12 hours is acceptable.
Notes
Requirements
The text was updated successfully, but these errors were encountered: