This pages summarises data collection procedures for OpenGov HR.
Disclaimer: OpenGov HR provides a structured overview of Polkadot ecosystem teams and contributors that are or have been funded by OpenGov.
OpenGov HR does not constitute an endorsement of the teams and contributors listed.
OpenGov HR does not aim nor claim to establish a “single source of truth” for off-chain data. Viewers are strongly encouraged to click through the links presented in OpenGov HR databases to obtain more details on the information presented.
Where does the data indexed in OpenGov HR databases come from?
| On-chain data | Off-chain data | |
|---|---|---|
| Bounties HR | Polkassembly, Subsquare (API), DoTreasury, Subscan | Bounty/curator candidacy proposal documents, Bounties webpages, Polkadot Forum |
| Bounties Staff | Polkassembly, Subsquare, DoTreasury, Subscan | Bounty/curator candidacy documents, Bounties webpages, Polkadot Forum |
| **DevRel HR & BD HR** | Polkassembly, Subsquare, DoTreasury, Subscan | Treasury/Bounty/Phragmén Initiative Fund proposal documents, Bounties webpages, Project web/social pages, Polkadot Forum |
| UX HR (TBC) | TBC | TBC |
How is the data indexed in OpenGov HR databases selected?
| Selection criteria | Rejection criteria | Notes | |
|---|---|---|---|
| Bounties HR | • Bounty is funded | ||
| • Bounty is active | |||
| • Bounty has issued payouts for bounty roles or bounty admin duties | • Bounty was claimed | ||
| • Bounty was rejected | |||
| • Bounty was cancelled | |||
| Bounties Staff | • Staff has been paid for bounty roles or admin duties | ||
| • Staff is an individual, the representatives of an organisation, a registered business | • Staff has been paid for other roles/duties unrelated to bounty admin | The field ‘Professional experience’ highlights some of the official roles/positions held by Bounties staff in the past and present. This is not an exhaustive list. | |
| **DevRel HR & BD HR** | • Team is a group, an association, a DAO, a registered business | ||
| • Team has received funding from OpenGov | • Team is part of W3F, Parity, or an ecosystem project (i.e. parachains & tokens issuers) | The dropdown menu highlights some of the efforts/successes achieved by teams throughout their history. This is not an exhaustive list. | |
| UX HR (TBC) | TBC | TBC | TBC |
How is the data indexed in OpenGov HR databases filtered and sorted?
| Filtering criteria (fields) | Sorting criteria (charts) | |
|---|---|---|
| Bounties HR | Inception: | |
| • The date on which the initial bounty proposal was submitted | ||
| Chain: | ||
| • Bounties that are submitted on Polkadot and Kusama | ||
| ID & Address: | ||
| • Active bounty IDs and their on-chain accounts | ||
| Balance: | ||
| • Current balance (in DOT/KSM) linked to active bounty IDs | ||
| Child bounties count: | ||
| • Child bounties that are linked to active bounty IDs | ||
| Child bounties sum: | ||
| • Total amount of DOT/KSM disbursed by active bounty IDs | ||
| Top-ups: | ||
| • Top-up proposals that are linked to active bounty IDs | • List of bounties submitted on each chain | |
| • Number of bounties created per month (historical) | ||
| • Total number of bounties in which each staff participate | ||
| • Total amount of DOT/KSM available in each bounty | ||
| • Total number of child bounties awarded by each bounty | ||
| • Total number of top-ups proposals awarded to each bounty | ||
| Bounties Staff | Roles: | |
| • Bounty roles that are listed in the initial bounty proposal or in top-up proposal(s) | ||
| • Bounty admin duties that are listed in child bounties | ||
| Professional experience: | ||
| • Bounties staff’s past and current official roles/positions (non-exhaustive) | ||
| Professional organisations: | ||
| • Bounties staff that are linked to an organisation operating within or outside the ecosystem | • Number of distinct bounty roles assigned to each staff | |
| • Total number of staff assigned to each bounty role | ||
| • The most represented organisations | ||
| • Total number of staff affiliated to the Polkadot Ambassador Fellowship | ||
| • Total number of staff affiliated to Parity Technologies | ||
| **DevRel HR & BD HR** | Start date: | |
| • The date on which the team was launched on socials OR the team’s first treasury proposal was submitted | ||
| Teams/Contributors: | ||
| • Teams/Contributors that are listed in Treasury proposals | ||
| Regions: | ||
| • Teams/Contributors that have participated to key industry events of the region | ||
| Programs: | ||
| • Teams that have run standalone DevRel-related programs | ||
| Services: | ||
| • Teams/Contributors that have delivered BD-related services | ||
| Status: | ||
| • ACTIVE: Teams that have submitted a Treasury proposal OR made Polkadot-related publications on their web/social pages in the past 3 months | ||
| • ?: Teams that have not submitted a Treasury proposal in the past 6 months | ||
| • INACTIVE: Teams that have not made Polkadot-related publications on their web/social pages in the past 9 months | ||
| Treasury proposals: | ||
| • Treasury proposals that are not funded by native bounty programs (i.e. Event bounty’s Polkadot Roots/Meetup; Meetup bounty’s Meetups, Marketing bounty’s Community Management) | • Number of teams onboarded per month (historical) | |
| • Total number of teams and their current status | ||
| • The most represented programs or services | ||
| • The most active regions | ||
| • Total number of programs/services delivered by each team | ||
| • Total number of treasury proposals funded for each team | ||
| • Teams that deliver the most for less (comparative) | ||
| UX HR (TBC) | TBC | TBC |
Created: 6th September 2025