Kudos: Unlocking the Full Potential of Polkadot's Developer Community


Kudos is a platform designed to streamline the process of onboarding new developers to the Polkadot ecosystem. We make it simple to browse, search and filter open GitHub contributions across the entire ecosystem, allowing aspiring contributors to find projects and tasks, which match their skill level and interests. In addition, we provide project maintainers the ability to tag open contributions with custom incentives, ranging from native tokens, NFTs, POAPs and many more. Lastly, we are working with ecosystem teams to actively curate sets of high quality, context-rich issues which aspiring contributors can begin working on immediately.

Who we are

A team of three technical co-founders who all successfully graduated from Wave 3 of the Polkadot Blockchain Academy at UC Berkeley.


The motivation for Kudos stemmed from a shared challenge encountered as successful graduates of the Polkadot Blockchain Academy. Despite being equipped with specialised skills in Polkadot technologies, we, along with many fellow alumni, found it difficult to immediately secure roles within the ecosystem, mainly due to the global tech hiring slowdown. Unfortunately, the lack of open roles in the Polkadot space at the time led to many skilled individuals accepting roles in other blockchain ecosystems or Web2 industries. One potential path to getting hired into the ecosystem is via contributing to the open source repositories with the hope of providing value and getting noticed. However, the difficulty with this method came into sharp focus during an alumni catch up at the sub0 Polkadot Developer Conference. Here we discussed the daunting task of navigating the Polkadot ecosystem to find suitable projects that aligned with our interests and skill levels. With over 25 000 repositories in the Polkadot ecosystem, efficiently locating and contributing to relevant open issues seemed nearly impossible.

Another motivating factor was the proliferation of low effort, low quality issues across the ecosystem. Issues lacking context and clear explanation simply serve as friction for potential contributors and generally end up accumulating as stale issues in the repository. In a previous post about his ecosystem wishlist, the Polkadot Fellowship’s Shawn Tabrizi further mentions that the current distribution of open ecosystem issues most likely follows a bell curve, with the majority of the issues requiring an intermediate core developer experience, while the majority of contributors are most likely interested in completing “good first issues” or “easy tasks”. This disconnect acts as a barrier to entry for less experienced developers and hinders developer growth.

Finally, we were inspired by the various decentralisation initiatives taking place firstly within the ecosystem itself but also in the wider world. As witnesses to the rise of flexible remote work and the normalisation of distributed asynchronous teams, we have all seen the power of decentralisation in action. Inefficiencies born of archaic processes begin to melt away as new methods of collaboration and value exchange emerge. We believe we can best contribute to a more decentralised future by providing tools and infrastructure which enable win-win situations for both projects and contributors.

From our motivations two questions arose:

  1. How do you best engage developers who are keen to contribute but lack a straightforward way to connect with appropriate opportunities?
  2. How do you create a positive feedback loop between project teams, contributors and the wider community, in a way that accelerates the growth of the Polkadot ecosystem?

Introducing the Kudos Portal

We are thrilled to reveal the Kudos Portal - https://www.morekudos.com

  1. Unified Repository Access: The portal consolidates repositories from the entire ecosystem into a single platform, providing a comprehensive view without the need to navigate through each individual repository on GitHub.
  2. Project Categorisation: The portal allows for refined searches based on specific interests and programming languages, enabling users to easily find projects that align with their skills and passions.
  3. Issue Curation: Kudos is already in collaboration talks with projects to curate sets of high quality issues which provide all of the necessary context to allow a contributor to begin work.
  4. Custom Incentives: We offer project maintainers the chance to utilise our smart contract templates along with customisable GitHub Workflows, allowing issues to be tagged with incentives which can later be automatically claimed by the contributor once the contribution has been accepted.

The actual alpha version was developed during the recent Encode x Polkadot accelerator program - (https://www.youtube.com/watch?v=pdDhO5SFuFA&t=306s ).

Ecosystem Fit

There are various initiatives within the Polkadot ecosystem aimed at developer engagement and upskilling.

  1. The Polkadot Blockchain Academy which aims to seed the Polkadot ecosystem with skilled developers.
  2. The Polkadot Developer Heroes program which aims to create a developer community, with a focus on mentoring and knowledge sharing.
  3. The Polkadot Fellowship is composed of core protocol developers with a focus on retaining technical expertise over the Polkadot meta-protocol.
  4. The Polkadot Dev channel on Twitch which aims to produce engaging video content for new and experienced developers alike.

We aim to complement these initiatives by providing a way for aspiring contributors to gain experience through solving meaningful tasks while potentially earning rewards while doing so.

Our core target audience is split across the following categories

  1. Developers & Contributors
  2. Projects & Teams
  3. Community

For contributors we want to help you:

  1. Find interesting tasks to work on
  2. Find great-fit contributions which match your skill level
  3. Find issues which are well documented and clearly explained
  4. Gain production experience and hone your skills
  5. Get hired and build a professional reputation
  6. Build relationships and network with other developers in the ecosystem
  7. Earn monetary and social rewards

For teams we want to help them:

  1. Ship faster
  2. Engage and upskill their developer/contributor community
  3. Gain greater visibility and actively promote their project

For the community we will:

  1. Provide a unified location for a browseable community wishlist
  2. Provide the means to aggregate and deliver feedback to ecosystem teams
  3. Allow the community to pre-emptively fund and upvote wishlist ideas and feature requests


Agile Devtime

We want to provide projects with the ability to rapidly and flexibly increase their workforce on demand. Whether it’s to take advantage of a new grant, or to polish up existing features allowing the core team to focus on more fruitful endeavours, we want to provide the infrastructural and organisational layer to make this possibility a reality.

Kudos Issues - Kudos Milestones

Kudos already streamlines the discovery of GitHub issues for contributors, aligning tasks with their skills and interests, but we plan to supercharge the value we provide by partnering with ecosystem teams to introduce two minimal mechanics:

  • Kudos Issues - high-quality, context-rich problems that are ready for immediate action by contributors
  • Kudos Milestones - “tracking issues” for larger achievements that encompass an incremental list of individual sub-tasks

Both Kudos Issues & Milestones will be taggable with incentives. Kudos Issues provide a one off reward for a well defined task, while Kudos Milestones will have an incentive pool claimable by contributors upon completion (e.g. bounty).

It’s important to note that the motivation behind open source contributions often stems from the contributors’ interests and experiences, not from financial incentives. Consequently, monetary rewards do not form the central pillar of our platform. We envision optional predefined rewards as simply a useful tool in the hands of maintainers, who always have the final say on which contributions are accepted, thereby ensuring that only high quality work is incentivised.

Latent community potential waiting to be tapped

Each project in the ecosystem has a core team, whose focus will be on the project’s main value proposition, and who will be engaged in delivering features related to their planned roadmap objectives, typically by executing on a set of clearly defined tasks. However, every project also usually has another set of more fuzzy tasks, often not fully scoped out due to time constraints and lack of personnel. These types of tasks vary in their nature, ranging from revamping documentation to developing better testing tools. Kudos will offer a way for teams to leverage the developer community by regularly working with projects to draw out these tasks into a set of actionable open contributions which can be worked on by members of the Kudos community.

Next Steps

We have already begun planning out our immediate next steps to extend the platform

  • Enhance contribution navigation by extending our search mechanism functionality

    • By trend: See trending collaborations, explore new projects, perfect for finding new challenges in your area of interest.
    • By project: View in-progress roadmaps, find similar projects, identify active collaborators to engage with.
    • Exploring teams/contributors relationships: Navigate back and forth between teams, projects, and contributors, uncovering a network of key players in your niche.
    • Using favourites: Access metrics, identify active teams, and spot the latest collaborations.
  • Develop collaboration workflows that are easy to integrate with existing projects

    • Develop a special Kudos GitHub label set for both issues and longer term milestones, for use by maintainers who wish to participate in the Kudos initiative.
    • Kudos Issues: Integrate our hackathon-winning incentive tagging mechanism directly on the Kudos platform. Tag individual issues with customised incentives and explore the development of an ecosystem wide Kudos version of the Substrate tip bot.
    • Kudos Milestones: Adopt a project-level bounty approach for short-term, potentially grant-funded roadmaps by leveraging “tracking issues” or GitHub projects. This approach is designed to share a larger vision with external contributors and release incentives upon overall completion.

Future Ideas

  • Kudos reputation system and contribution metrics

  • Notifications: stay updated with alerts on your interests and engagements

  • Community engagement tools (e.g. upvoting community wishlist)

  • Open job boards


We are going to be presenting our ideas at the upcoming sub0 developer conference in Bangkok on March 12th, where we hope to present a full picture of our project. We want the development of the Kudos platform to be driven by the community’s needs and welcome your feedback and suggestions!


This is something that is needed in the Polkadot ecosystem. We need a streamlined process to onboard more developers.

This is a great idea. It provides a very good source of data.

Yes, this is indeed challenging.

This is interesting. This makes the live of a contributor much more enjoyable.

Overall, I support this initiative.

1 Like

This is a great idea and knowing all three members of the team from my time at the PBA UC Berkeley makes me certain that the team is more than capable of its delivery. This will provide a showcase for developer talent as well as focus for developers at any level to deliver value to projects within the Polkadot Ecosystem. I also see a potential partnership with another great project dAppForge: AI-powered plugin for Polkadot developers that reduces development time which is providing enhanced AI driven developer tooling for Substrate & Ink builders. I fully support this initiative. Cheers Richard


I have just completed the fourth wave of the PBA developer track in Hong Kong, and both myself and other students have encountered the same challenges.

Polkadot is an extremely interesting and powerful technological ecosystem. However, it can be challenging for newcomers to gain experience, build relationships, fully integrate into the ecosystem and choose what to work on, especially if have already a full time job in a different sector.

I believe that initiatives like this are extremely useful for the development of the ecosystem.
They allow developers to gain experience at their own pace, choose the right tasks to work on, facilitating a gradual transition from other professional areas and enabling them to switch to a full-time job in the ecosystem when they are ready.

This flexibility is essential for developers to enter or switch to this ecosystem, and it can contribute positively to its growth.


I really like the idea. I don’t think it’s easy for new developers coming into the poladkot ecosystem to gain experience. This is something where this project will definitely help to be a place for new developers to gain experience and make new connections.

It also seems like it will be a fun way for contributors to find tasks that fit their skill set and earn rewards. I looking forward to see how this project will develop in the furture and I’m sure the ecosystem will benefit from this.

1 Like

I’m genuinely excited about Kudos and its potential to streamline the onboarding of new developers into the Polkadot ecosystem. As someone who’s faced challenges in finding open-source projects aligned with my interests and skills, Kudos feels like a much-needed solution.

A suggestion to further enhance the platform would be the addition of a leaderboard. It could spotlight top contributors weekly or monthly, providing recognition and potentially attracting more developers.

Looking forward to diving into Kudos and discovering the opportunities it offers!

1 Like

This is a fantastic idea! I think it’s very important to shorten the gap between new contributors and existing codebases while enabling project maintainers to incentivise them, and providing and a way of filtering suitable repositories and issues.

As you mentioned, contributing to open source projects is one of the best ways of getting noticed in the ecosystem and I believe having a reputation and skillset metrics can help recruiters pick the right developers for their needs.

1 Like

This is a great initiative for contributors and new developers. I am pretty sure this will bring more developer engagement to the Polkadot ecosystem.

1 Like

Hii Everyone This is vishal jr dev being a part of Polkadot heroes programme ,i’m gain some sort of experience in rust trait and genrics till now about syntax i just want to do a contribution in open source plz can u help me how can i start?

1 Like

Hey, it’s Diego from 3rd Cohort Berkeley (the coolest :rugby_football:!). I see a valuable proposal over here!

Focusing the onboarding experience of an entire ecosystem and digesting them up to specific tasks of known time frame of completion is powerful to implement, when the tasks are of high added value for the ecosystem. If done with UX/UI in mind, engaging with new tasks and earning batches should be fun, and together with the possibility of engaging with hackathon events and challenges would be an excellent start point for the productivity streamline that gots us gathered around these projects in the first place and will continue giving us good reasons to stay doing business together, which should always attract new investors from around the world. I see a clear and interesting value proposition behind this project, considering its tentative overall cost of implementation.

The possibility of aggregating all the contribution and being able to visualize it could be powerful too, as a way of taking insights on the development of the technology in its different aspects. In this sense, I see the issue categorization as a critical aspect for the overall experience of the tool, as for example with up and downstream dependency relationship, expected time of completion, vulnerability level and priority.

Keep the good work guys! Hope to see you soon.


First of all, Kudos for this awesome initiative!

It’s not just the process to help to onboard new people in the ecosystem, but also the unified access, the incentives, and the feeling of challenging us.

This proposal can help many people to get started with real-world experience right after educational processes (like Polkadot Blockchain Academy, or PBA-X), closing the circle for introducing them to the ecosystem and making the efforts to educate developers on Substrate/FRAME/Polkadot, and related technologies way more useful.

1 Like

I can not wait to try it in action!

If marketed correctly, I think it will definitely increase the developer activity.

1 Like

I am a PBA Hong Kong alumni, and this is an excellent proposal; we need substrate developers to find a place to contribute to the Polkadot ecosystem, find a job, etc.

I have a question: what is the marketing plan to engage with the developers?

1 Like

Kudos sounds like a valuable initiative for the Polkadot ecosystem! I appreciate you sharing your detailed explanation and vision for the platform. Can’t wait to see it go live.

1 Like

Nice! I wonder if we could incorporate some voting mechanism to get input on how important an issue is.
Let’s imagine there are stakeholders that want some issues solved but have no way of expressing their priority. Do you think there could be some simple :+1: / :-1: voting on issues?


Yes, I agree with you. A simple voting mechanism with the right user interface will be effective in decision making.

1 Like

Yes for sure, the creation a voting mechanism is definitely part of the Kudos roadmap!

We’re currently considering a few different implementation methods for such a system. In the early stages we may look to just leverage GitHub reactions to create a preference indicator, however since we will also create a community wishlist, we will probably need something custom to allow a bit more expressivity as well as cater to those who might not have GitHub accounts.

If you have any ideas around voting mechanisms you would like to see, or about any other topics we mentioned please let us know!

Hola :wave:

I like the team a lot and the team is capable.
I can easily give me best support.


Cheers :sun_behind_small_cloud:

1 Like

While seemingly simple as a solution, is actually quite crucial to fostering our circle of OSS contributors. it’s also a sound way to gather more metrics on contributors in the space in general

During ETH Denver, I was asked a few times about how one could start contributing to the Polkadot SDK - currently, for a newcomer to the ecosystem (or new to blockchain in general) it can be intimidating, friction is often a massive turnaway for many.

Also, hightlighting ecosystem teams is great, you’d be surprised at how many don’t make the connection between some of them and the fact that they are built on Polkadot.