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
Their needs to be a way to prevent spam of a projects and easily query all projects associated with potlock.
User Story:
As an admin, I want to be able to edit the status of a project, to prevent from people spamming us.
As a an dev, I want their to be an official potlock registry, so I can easily query all projects that signed up throuhg our platform.
As a refi council member, I want to vote on adding an additional admin, so
Description
Registry contract can add projects with different statuses updated by admin
Acceptance Criteria
registry.potlock.near contract for all projects that go through onboarding flow. Requirement / prereq for applying to round
ability for owner (refi.sputnik-dao.near) in this case to add and remove admin based on accountID
add project by accountID
flag projects
put projects in a whitelist to displaylist
projects in pending status
Getters
query all projects
query status by projectID
query if project is on registry by accountID
get all projects in graylist, blacklist, and whtielist (get all projects by status)
ability to get owner
ability to query admin
Limitations
on the front end still need to hit multiple data sources
Problem
Their needs to be a way to prevent spam of a projects and easily query all projects associated with potlock.
User Story:
As an admin, I want to be able to edit the status of a project, to prevent from people spamming us.
As a an dev, I want their to be an official potlock registry, so I can easily query all projects that signed up throuhg our platform.
As a refi council member, I want to vote on adding an additional admin, so
Description
Registry contract can add projects with different statuses updated by admin
Acceptance Criteria
registry.potlock.near contract for all projects that go through onboarding flow. Requirement / prereq for applying to round
Getters
Limitations
Resources
The text was updated successfully, but these errors were encountered: