About me
I’m Ankan. I was part of the first PBA cohort (July 2022), then joined Parity as a runtime developer (my first Web3 job), and have worked extensively on staking since then. I’ve also been an instructor and TA at PBA Hong Kong (2024) and PBA Bali (2025).
The Problem
PBA is an excellent academy. It turns motivated engineers into capable substrate runtime developers. But:
- After graduation, some join Parity or ecosystem teams, a few receive OpenGov funding, but many drift back to Web2 or other ecosystems.
- Parity cannot absorb everyone. It has its own roadmap and priorities.
- The Polkadot community has treasury funds and open bounties but not enough active developers.
- External contributors who try to submit PRs to polkadot-sdk often get blocked and discouraged trying to get meaningful feedback and reviews.
As a result, we have hundreds of developers who want to help and an ecosystem that needs help, but no clear bridge between the two.
The gap and vision
What we are missing after PBA is continuity. Developers graduate with strong technical skills but often lose momentum because there is no structure guiding them toward real work in the ecosystem.
New developers need help with context, feedback, and access to people who can connect them with problems worth solving and help them get their first few PRs through review and merge. After that, most can stand on their own and mentor others.
PBA itself has raised this point several times in its opengov proposals: support after graduation is missing. If we can build that layer through a growing network of mentors, we can turn PBA from a one-time bootcamp into a continuous developer pipeline for Polkadot.
With OpenGov bounties, it is now possible to make a real living by building for Polkadot as a freelance developer. Working as part of a group with shared identity and learning, like the PBA community, is much more effective than doing it alone.
Many graduates also bring experience from other blockchain ecosystems. They can help Polkadot collaborate better with the wider blockchain world, something we have not done well so far. These people can quietly become the bridges and ambassadors that Polkadot needs.
The long-term goal is to create an open, self-run system organised by PBA alumni, sustainable and not dependent on any one person or company. If it works, it becomes the missing middle layer that connects training with real, ongoing impact in the ecosystem.
Pilot
Together with Alexander Popiak and six recent graduates from PBA Bali - Eman, Jeff, Johanan, Lucas Grasso, Veronika, Yash, and with blessings from the PBA team, we are starting a small pilot.
We’ll take on around three tasks as bounties (OG Rust) and help deliver them end-to-end. We have already submitted a bounty proposal for one issue, and almost ready with two others:
- Time based scheduler: A time based scheduler · Issue #3672 · paritytech/polkadot-sdk · GitHub
- Session rotation benchmark: Properly benchmark on_initize hook weight · Issue #184 · paritytech/polkadot-sdk · GitHub
- Governance Precompile: Add Governance pre-compile · Issue #8366 · paritytech/polkadot-sdk · GitHub
We are starting small, but if this works, we will gradually bring in more mentors and more PBA developers to work on tasks that the community cares about.
Both developers and mentors will be paid through the bounties.
I am still exploring whether we should find a different way to compensate mentors, perhaps through OpenGov funding, a fellowship mechanism, or something else. I would appreciate any opinions or experience others can share.
Contribution Portal
We want to work in public and keep everything transparent. To know whether we are succeeding, we also need to measure our impact.
We plan to build a public Contribution Portal, developed by PBA alumni, that tracks:
- Contributions from PBA developers to
polkadot-sdk
and the broader ecosystem:- PRs merged
- Issues closed
- Active contributors
- Review and audit times, from ready for review to first feedback, audit, and merge
- Ongoing bounties and mentors
The goal is to make contributions visible and feedback cycles shorter - for both pba devs and core protocol devs.
I already vibe-coded a POC that you can checkout here: Contribution Portal.
Closing Note
Similar efforts have been tried before and have sometimes lost momentum. We want to learn from those experiences and keep this one practical and open. If we succeed, we could drive a step change in how quickly Polkadot evolves, whilst guiding PBA graduate developers to the right issues, building their experience and profile within the ecosystem and driving efficient utilisation of the developers we have invested in through PBA Campus.
Coordination is our superpower. If you believe you can help, or have thoughts or experiences to share, we would love to hear from you.