- Referenda/
- Big Spender/
- #1549/
KAGOME – the C++ implementation of Polkadot Host milestone 4
- 0.0%
- 0.0%
Threshold
- 0.0%
PolkaWorld votes AYE.
From the 38 JAM implementation teams, it’s clear that Polkadot places great importance on client diversity. However, the Polkadot network itself currently relies solely on the client developed by Parity. While the relay chain will eventually be replaced by JAM, it still needs to run in the meantime—and of course, we hope JAM can be implemented as soon as possible.
Our main concern initially was the lack of transparency around compensation. The proposal used a flat hourly rate, but as we all know, teams consist of different roles with different responsibilities. We believe it’s important to encourage more budget transparency, as this helps any community member assess whether the funding amount is reasonable. It also allows OpenGov to better understand regional salary standards and compensation structures—ultimately helping establish more transparent funding norms across the ecosystem.
Thanks to the team’s recent clarification, we now have a much clearer understanding of the cost breakdown. Referring to data from web3.career, we can also see that the team’s compensation levels fall within a reasonable market range:
• Engineering Manager: $10,000 / month
• Senior C++ Engineer: $4,000 – $9,000 / month
• DevOps Engineer: $50 / hour
• QA Engineer: $50 / hour
We appreciate the team’s openness and responsiveness in helping the community make a more informed decision.
Dear Proposer,
Thank you for your proposal. Our first vote on this proposal is AYE.
The Big Spender track requires 60% quorum according to our voting policy v0.2, and any referendum in which the majority of members vote abstain receives an abstain vote. This proposal has received six aye and one nay votes from ten available members, with two members abstaining. Below is a summary of our members' comments:
The voters expressed varying opinions on the importance of client diversity in the context of an upcoming transition to JAM. Most supported the proposal, acknowledging the necessity of alternatives like KAGOME for enhancing network resilience and performance, especially given its successful implementation on other platforms. Some voters raised concerns about the practicality and timing of investing in client diversity, suggesting that user adoption should precede funding. A few chose to abstain, reflecting uncertainty about the benefits of client diversity amid ongoing developments with JAM.
The full discussion can be found in our internal voting.
Please feel free to contact us through the links below for further discussion.
Kind regards,
Permanence DAO
Decentralized Voices Cohort IV Delegate
📅 Book Office Hours
💬 Public Telegram
🌐️ Web
🐦 Twitter
🗳️ Delegate
At this stage, it’s difficult for us to assess whether the overall costs are reasonable. Would you be able to provide a more detailed breakdown of the following?
It would also be helpful to see the hourly rate differences across roles, such as:
• 1 Engineering Manager
• 4.5 Senior C++ Developers
• 0.5 DevOps Engineer
• 0.5 QA Engineer
Additionally, under each ETA (hours) entry, would it be possible to indicate which roles are involved in delivering that specific feature?
This level of detail would help us better evaluate the proposal and would also bring greater transparency to the broader community. Thank you!