Contributors—we’ve talked about them multiple times. It’s still a general term for now, but we’re in the process of breaking it down into more defined subroles. Currently, we have contributors at the product level, and now we’re adding contributors at the core community level (Core community: those actively engaging in our messaging channels like Discord and Telegram).
Recently, we onboarded a couple of new community contributors to the DAO.
What does that mean? They were hired by the DAO to complete specific tasks. Where did they come from? How were they chosen? We looked at previous ambassador programs, found the top performers, and sent them offers.
Okay, cool, who are they?
@rhizencrypt @sidneyakpaso @Berry
You probably know these guys from the community. Yes, they’ve done plenty for DappRadar back when the ambassador program was running, and now they’re directly hired.
So, what are we working on together?
While building the ambassador program, we realized that the community wasn’t standing together—things were scattered. So, we started with contributors. These guys will help us shape, structure, and strengthen our current community before moving outward and kickstarting outreach campaigns.
As a Web3 enthusiast, if you’re joining a community, you’d rather join one with active, smart, and innovative members rather than a small one. How do we reach that? We have to prepare the current community and strengthen it before expanding and bridging with other communities. Let’s say we did expand and reached out to other communities—can our community handle the inflow right now? If not, then we need to fix that with the new contributors.
This is similar to other aspects of the ecosystem. Imagine you open a hospital in a fresh city with 500 people—3 or 4 doctors are enough. But that doesn’t mean you should just sit there, as the city will grow. While you only have 500 people, you should strategize and structure your organization to adapt to growth. When you start hiring new people, your system won’t fail—you’ll have more doctors in preparation for what’s coming next. This same concept applies here.
Roles and Goals:
Now, we have two primary roles for our community contributors:
• Anchor (Community Support):The goal here is to improve community support by ensuring we cover different timezones. Our Anchors are learning more about DappRadar, which helps ensure that the community is well-supported by its own members. Eventually, the knowledge they acquire will be spread throughout the community, building a more informed and self-sufficient support system.
• Wordsmith (Content Creator):The second role focuses on increasing the amount of educational and informational content we put out on socials. More content means more impressions, which leads to greater reach. If the content is well-tailored to be educational, it benefits DAO members directly, ensuring they become more knowledgeable. We’re starting with one Wordsmith for now, but we’re building a framework to scale, which will create future opportunities for the community to contribute.
Right now, these contributors are onboarded and signed. They’re in practice mode, learning and preparing for a full push. We don’t expect anyone to be perfect from the start. DappRadar has been around for six years, and getting fully up to speed takes time. We’re also refining this initiative as we go because we need to adapt to the work.
Why Do We Need This?
The primary objective of the Community Contributor Initiative is to reward contributors within our ecosystem as we build a community-owned Dapp Store. We need to test various aspects with a controlled group before scaling, using insights gained from the Ambassador program. With the Progressive Decentralization workstream in place, this initiative will help transition some ambassadors to evaluate their effectiveness in operational and strategic tasks for scaling the World’s Dapp Store.
As I’ve mentioned before, it’s crucial to ensure our community is well-prepared, structured, and ready to handle an influx of new members before we start bringing them in. This initiative focuses on two key areas for community growth: user support and content creation. Both are essential as we refine our structure, build a solid framework, and prepare the community for the scale envisioned with the World’s Dapp Store—built by millions, used by billions. Just as the product needs to be prepared, so does our core community (those on Discord, Telegram, etc.). We’re setting them up for success to play a pivotal role in this growth.
Timeline:
The current community contributors are part of the progressive decentralization workstream. The next step is to extend this workstream for another 6 months, including a budget for the contributors. The first month, and part of the second, will focus on onboarding and training—getting the Anchors and Wordsmith comfortable in their roles. After that, they’ll move into full-on execution and expansion mode. In the long run, these contributors will be upgraded, and we’ll also have to increase their compensation to match their evolving roles.
There are no application forms or processes at this stage. We’re working with community members handpicked from the previous ambassador program. Once the structure and framework for community contributors are solid, we’ll assess the roles needed for further growth and then open it up to the wider community. Right now, we’re preparing the ingredients for a bigger dish that we’re about to cook.
Long-Term Impact:
We’re building a foundation that ensures a stronger, smarter community. It’s not about rushing into big campaigns without a plan. By focusing on key roles like Anchors and Wordsmiths, we’re setting up the community for long-term success. The stronger the foundation, the easier it will be to scale and bring in new members.
As we continue, we’re not just looking to grow our numbers. We’re focused on making the community more informed, better supported, and capable of growing together. Eventually, as the structure strengthens, we’ll have the capacity to open up more roles and invite broader participation, but for now, the focus is on building and refining.
Conclusion
I don’t want to sit down and type a lot, so here’s a quick diagram to show how contributors look in general. It’s not 100% final and is subject to change, but this is how things are aimed.
Look how beautifully this works—yes, it’s a loop! The product turns users into community members, and vice versa, while the community nurtures dapp managers and Web3 builders. That’s why it’s crucial to establish a strong foundation now with the Anchor and Wordsmith roles before expanding into other roles. By building the community’s educational content and leveraging the knowledge gained through support from these two contributor roles, expanding into other areas will become much easier.
If you want to learn more about the three contributors focused on the product (ones in grey in the diagram), check out pieces 20 to 24 here.
Please comment below with any questions you have, and we’ll keep you updated on all things regarding these contributors in this forum thread.