Other people may want to use nadabot protocol to create their own defintion of a human and not trust us. They may want to add their own stamp
User Story(s):
As a application, I want to have my own definition of human or meeting a score, so that I can not rely on nada bot providers
As an application, I want to leverage existing stamps for nadabot but add my own custom rules so I dont have to
As a person configuring my own score, i need to have any easy dashboard for toggling this, so that I can easily set the settings.
As a user of this custom score, I want to see a version with different config (pass config id in props) so that I can interact and optimize for this type of score.
Acceptance Criteria
UX
view all stamps and sets weights and statuses
ability for users to see wieghts and rules with the associated config and see their relevant score
ability to have their own config file and id
that config file has their own rules, own weights and own statuses
view meetsThreshold(config): book
getConfig(config): config
ability to add existing stamps
set their own weights and rol,
setIsHumanRules
make front ends configure with different nadabot contracts
should have restriction on flagged vs rejected ones for safety to help nada bot people better
deploy under v2
Maybe
can be factory account models
but factory modal doesnt keep state of current stamps
config files enables them to adjust current state and set their own state and rules
Problem
Other people may want to use nadabot protocol to create their own defintion of a human and not trust us. They may want to add their own stamp
User Story(s):
As a application, I want to have my own definition of human or meeting a score, so that I can not rely on nada bot providers As an application, I want to leverage existing stamps for nadabot but add my own custom rules so I dont have to As a person configuring my own score, i need to have any easy dashboard for toggling this, so that I can easily set the settings. As a user of this custom score, I want to see a version with different config (pass config id in props) so that I can interact and optimize for this type of score.
Acceptance Criteria
UX
view all stamps and sets weights and statuses
ability for users to see wieghts and rules with the associated config and see their relevant score
ability to have their own config file and id
that config file has their own rules, own weights and own statuses
view meetsThreshold(config): book
getConfig(config): config
ability to add existing stamps
set their own weights and rol,
setIsHumanRules
make front ends configure with different nadabot contracts
should have restriction on flagged vs rejected ones for safety to help nada bot people better
deploy under v2 Maybe
can be factory account models
but factory modal doesnt keep state of current stamps
config files enables them to adjust current state and set their own state and rules