<u>Solution Overview</u>
A hub that doubles as a landing- and launchpad offering stakeholders (that are having a hard time with Catalyst and Ideascale) a personal and human centered on-boarding experience.
- Landing: personal and individual on-boarding into Catalyst
- Hub(ing): Mingling and ideating on proposals
- Launching: polished proposals
Facilitation via Discord (coordination), GitHub (documentation & tracking) and Twitter (outreach).
Collaborations with Hazelnetbot (automation, role and ID verification), ADAO (DAO tooling), SecretDecks (contribution tracking) and ADACafé with StakingDAO (Twitterspaces, outreach) are already ongoing and will deepen further within the hub.
see attached HFQ-Landing_v.01.jpg
see attached HFQ-Launching_v.01.jpg
ID/Role Solution
A separate ID/Role solution will be developed in the scope of this proposal:
DuckId will be a customizable Identification/Role solution. DAO's or other autonomous organizations will be able to request custom Identification for entire organization that are verifiable and unique by using a user provided 4-6 pin concatenated with the organization's name(or other chosen identifier).
- The DuckID can be used as an input in a script, releasing funds to specific users.
- The DuckID can be used to assign roles in a DAO/Server.
- The DuckID can be used to establish trusted users in a public space by requiring members to have a policy key minted with their unique identifier.
- The DuckID can be used as a voting tool, requiring each participant to possess a valid personalized ID with the policy number tied to a corresponding election.
<u>Who are the stakeholders we are talking about? </u>
Referencing IO article
- general ADA holders
- (previous) Catalyst participants
- SPO'S & MPO's
- exchanges (centralised and decentralised)
- IOG, CF, Emurgo
- proposers not comfortable with ideascale or long format town halls / after town halls
1) Delivering information to people who would not otherwise have the access
- pick up new members right at the gate, offering a personal onboarding experience (manually at first, via bot when scaling up)
- lowering cost of information acquisition by increasing signal to noise ratio
- synopsis of long format events
- helping with finding meaningful stake pools
2) Ensuring resilience and self-reliance within that community.
- identity, proposals and ideas are being tokenized, in order for members to be self sovereign
- Creating small, dynamic hubs around stakeholders, purposes and congruent ideas
3) Community Mapping and Identifying existing “community hubs / Stake Holders” to engage them in a meaningful and appropriate way
There are several areas of concern that we will be monitoring closely and providing additional resources to insure a successful delivery but here are the main points that we’ve identified:
1) User Engagement on all three platforms, github, discord, and twitter is the goal and we are aware that some participants will not engage on all three platforms.
Using the three platforms is one method of transferring some of the risk.
2) Redefining Community Hubs as digital centers of influence may be challenging for some to understand.
3) Properly connecting the three platforms for a seamless experience will require some trial and error.
4) Education and training on github, discord, and twitter could be a challenge if not addressed properly.