over budget
🛫 On-Boarding ALL stakeholders
Current Project Status
Unfunded
Amount
Received
$0
Amount
Requested
$22,200
Percentage
Received
0.00%
Solution

On-boarding and launch protocols that make sense and engage in a meaningful & fun way

Problem

Cardano community sees Catalyst as a separate entity, thus many stakeholders are neither on-boarded nor engaged.

Addresses Challenge
Feasibility
Auditability

Team

2 members

🛫 On-Boarding ALL stakeholders

<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.

1 month - Prepare and launch the github, discord, and twitter thread and have on-boarded several additional participants to engage the stakeholders

3 months - Will have the three platforms providing data for the KPIs and should have on-boarded several groups of stakeholders, including SPOs and exchanges, or holders that used exchanges.

6 months - Will have entered into the scaling portion of the project and will have additional clones of these hubs for use by other community members.

12 months (with additional funding or already self sustaining!) - Expanded to additional social media platforms to engage additional stakeholders that are outside the main three platforms.

DuckID OpenSource solution: 9k USD

Community management (2 persons for 6 months): 12k USD

Administration & documentation: 1.2k USD

<u>Total: 22.2k USD</u>

[Community Management, Administration] Deryck Lance is an Entrepreneur with 18 years experience in the insurance and risk industry, Founder of Quasar Risk Advisors, an independent insurance brokerage and Gig Guard, an insurtech engineering studio specializing in the design of embedded insurance for platform businesses. His journey into blockchain began working with Etherisc, a parametric based smart contract risk protocol in 2017.

[LinkedIn]

[Community Management, Documentation] Dan Verowski is a business analyst and scrum master dedicated to pioneering distributed cooperatives (DisCo’s); in crypto full time since 2016; experienced in project and team management; funded in F6 and F7 with SecretDecks

[LinkedIn]

[Engineering] Dominick Garey-Owner Nehemiah Construction. Current Plutus Pioneer Student

[LinkedIn]

Tracking done in GitHub projects (ZenHub); Daily Check Ins (asynchronous Stand ups) of core contributors

Success for the project will be participation in Catalyst by stakeholders that were not actively engaged prior to this proposal, including new participants that were previously holding their ADA on exchanges and other stakeholders such as SPOs and exchanges, perhaps a Catalyst Native partner.

Another vision of success will be the duplication of this project in other languages.

Past proposals in relation to this were not funded

close

Playlist

  • EP2: epoch_length

    Authored by: Darlington Kofa

    3m 24s
    Darlington Kofa
  • EP1: 'd' parameter

    Authored by: Darlington Kofa

    4m 3s
    Darlington Kofa
  • EP3: key_deposit

    Authored by: Darlington Kofa

    3m 48s
    Darlington Kofa
  • EP4: epoch_no

    Authored by: Darlington Kofa

    2m 16s
    Darlington Kofa
  • EP5: max_block_size

    Authored by: Darlington Kofa

    3m 14s
    Darlington Kofa
  • EP6: pool_deposit

    Authored by: Darlington Kofa

    3m 19s
    Darlington Kofa
  • EP7: max_tx_size

    Authored by: Darlington Kofa

    4m 59s
    Darlington Kofa
0:00
/
~0:00