I might agree on this if Passport broadened its scope to being a protocol or primitive applicable to projects & programs as well as donors/voters. See my comment here:
Passport is a protocol for using DIDs to:
- Scoring reputation for gating access in a transparent and auditable way
- Scoring behavioral interactions for retroactively discounting unwanted behavior in a transparent and auditable way.
If it was a comprehensive solution needed for all of our components, I would agree it is the third most important.
If not, then I think βempowering the community to participate in building alongside usβ is #3.
This would include:
- Improving documentation to empower developers to build on our protocols
- Improving open data access to empower data scientists to conduct research and guide a community driven R&D cycle
- Development of educational materials and runbooks for Program Managers - maybe even training classes
- Defining ENGAGEMENT LOOP metrics for each of these constituencies to not only acquire their interest, but to make their participation βstickyβ (The old 10 friends on facebook thing)
How might we have more of the community weigh in to see if we donβt change our minds before EthDenver in person sessions?