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
Outside of project sign up, projects need a way to apply for a pot directly.
User Story:
As a project, I want to be able to apply to a Pot, so that I can be eligible for a quadratic funding round.
As a project, I want to know whether I am able to apply to a quadratic funding round, so that I can get those criterion or i know that im not ellgible
Description
Create an easy application page that is navigable from a pot page for proejcts to apply. Also keep in mind that there will be popup for eligibility requirements and indicators for projects to sign up if not already part of proejct registry.
Acceptance Criteria
Contract
calls the pot contract at {potname}.pot.potlock.near in the apply round
check if not already applied (need to keep track of acceptance applications, but all applications)
Eligibility
show what eligibility requirements are and show error if not with link to sbt
show a checkmark you are ellgible
Limitations
making application flexible so that it is not a friction potinf or projects to apply
separating project registry from application may hinder people from applying directly to round and may need to be considered within the same flow
"Outside of project sign up, projects need a way to apply for a pot directly." - @codingshot are you saying that projects should be able to apply without being on the registry? bc currently that's not how it's set up
Problem
Outside of project sign up, projects need a way to apply for a pot directly.
User Story:
Description
Create an easy application page that is navigable from a pot page for proejcts to apply. Also keep in mind that there will be popup for eligibility requirements and indicators for projects to sign up if not already part of proejct registry.
Acceptance Criteria
Contract
Eligibility
Limitations
Resources
The text was updated successfully, but these errors were encountered: