Threshold
OG Tracker Rating 2/3
Clear display of deliverables✅
Clear display of a valid direct point of contact ✅
Clear display of proposal’s duration✅
OGT Rating aims to help voters make better informed decisions and direct proposers towards certain common-good practices. We are providing feedback based on 3 simple yet crucial criteria which we believe should be included in every OpenGov referenda.
Edited
PolkaWorld votes AYE
Most of our members recognize the necessity and importance of Pop CLI, as well as the growing trend of its adoption across the ecosystem.
Some members believe that based on previous deliveries, the project demonstrates a high level of completion. The proposed funding breakdown is relatively clear, and the upcoming feature roadmap is well-structured — therefore, they support the proposal.
A few members did express concern that the requested budget is on the higher side and that the breakdown could be more granular. They consulted developers to confirm whether the described scope justifies six months of work. The feedback confirmed the timeline is reasonable, and the hourly rates are in line with current standards.
Overall, this proposal has earned our support!
You can view the full discussion here.
Big Aye from the Dedot Team
POP CLI has long been a crucial tool for Polkadot builder, supporting both new and experienced developers with reliable, well-designed tooling that simplifies the development process. This proposal marks an important step forward in strengthening the developer experience and providing much-needed improvements across the ecosystem.
We're looking forward to the potential collaboration with the R0GUE team, especially around frontend template development. We fully support this proposal and look forward to seeing POP CLI continue to evolve as a core piece of Polkadot’s developer infrastructure.
Dear Proposer,
Thank you for your proposal. Our first vote on this proposal is ABSTAIN.
The Medium Spender track requires 50% quorum (at least 5 aye votes) and simple majority of non-abstain votes 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 zero aye and zero nay votes from ten available members, with six members abstaining. Below is a summary of our members' comments:
Several voters chose to abstain from the referendum, expressing a desire for greater clarity regarding the user base and the specific applications of the proposal. They acknowledged the valuable efforts of the R0gue team but raised concerns about the justification of the associated costs and the overall adoption of the initiative. Many voters echoed similar sentiments, emphasizing the need for further discussions before making a decision. Overall, there was a consensus on the importance of more information to inform their choices.
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
Santi from Parity here.
I just want to say that I truly believe in the work that the R0gue does, specially when it comes to POP-CLI. Personally I recently had the pleasure to work with them in integrating the Polkadot Deployment Portal (PDP) with the CLI and the entire project was managed professionally and with deep Polkadot knowledge by the R0gue team.
This team has proved time and again that their passion for Polkadot is real, and they back this with very useful contributions!
I've been a frequent CLI user, and I think this proposal will help improve the developer experience. As an added bonus, I should mention that the POP team does a great job providing support for questions or issues.
Truth DAO votes AYE
The team has a strong track record of delivery and is highly reliable.
Pop CLI is already a core tool within the Polkadot ecosystem and continues to see growing adoption.
The budget is well-structured, with reasonable cost-efficiency.
Recommendation:
While the budget is on the higher side, we suggest publishing quarterly progress reports to ensure transparency and accountability.
Read all feedback here.
📖Truth DAO Governance Statement
🗳️ Delegate
✅ Why Vote YES
• Critical developer tool: Pop CLI is an all-in-one tool that simplifies the full development lifecycle on Polkadot — from scaffolding to deployment, for both chains and smart contracts.
• Proven adoption & ecosystem recognition:
• Used by ~10% of the Polkadot dev community (Electric Capital est.)
• Officially recommended in Polkadot’s own documentation
• Featured in major events like Polkadot Decoded, Sub0, and Substrate seminars
• Experienced team: Built by former Parity engineers with deep experience in Substrate, ink!, testnets, Polkadot SDK, and enterprise chains.
• Clear and strategic roadmap:
• Live state forking for local networks
• AI integration via prompt and conversational mode (MCP server)
• Verified contract publishing (ink! → Etherscan/Blockscout)
• Full-stack starter kits (frontend + OmniNode runtime templates)
• State lookup, continuous maintenance, education & DevRel support
• Improves developer experience (DX):
• Less boilerplate, seamless tooling integration
• Secure signing via browser
• Support for multi-chain testing, runtime upgrades, and benchmarking
• End-to-end workflows in one tool
• Future-ready & aligned with JAM vision:
• Integrates with Polkadot Deployment Platform (PDP), supports ink! v6
• Sets the foundation for JAM-native, cloud-style workflows
⸻
❌ Why Vote NO
• High funding request: $577,500 USDC (~530,000 EUR) for a single proposal, covering around 4,800 engineering hours over 6–12 months.
• Single team control: R0GUE leads the entire proposal; over-reliance on one group may centralize influence over core developer tooling.
• Still growing adoption: While early traction is strong, day-to-day usage and community contribution on GitHub remain limited compared to long-term goals.
• Pending audit for templates: Contract/chain templates included in the CLI are not yet audited. Audits are planned but not part of this budget scope.
• AI integration still experimental: The AI functionality is early-stage and not guaranteed to deliver immediate utility — potential overinvestment in a speculative feature.
⸻
🎯 Verdict:
Pop CLI is a high-impact, high-quality project that has already delivered strong results and is positioned to become the default developer tool in the Polkadot ecosystem. If you believe in accelerating developer adoption and reducing friction in building on Polkadot, this is a strategic proposal worth supporting — with justified cost and clear milestones.
Past Performance
Delivered Tasks & PoW
✅ Unit and integration testing, documentation, and ink! examples. Augmented with the Pop CLI.
✅Support for DOT / PAS as native token on Pop.
✅A pallet to facilitate asynchronous smart contracts.
✅Pop API spec, with pallet implementation.
✅Integrate Pop API with specific pallets.
✅Pop API crate linking ink! contracts with the runtime pallets.
✅A UI that on/offboards relay chain token to Pop.
✅Pop API crate linking ink! contracts with the new runtime features.
✅Foreign assets with Asset Hub and querying with ISMP.
✅Pallet and relayer, integrated with Pop API.
✅Launch on Polkadot with parachain infrastructure in place.
Pending Tasks
Three tasks experienced delays due to third-party involvement and dependencies on external components that are currently under development.
⌛ Bulk Coretime Purchase
⌛Audits
⌛Subscan Integration
Remodelled Tasks
❗ Integrate cross-chain use-cases and programmable DAO with Pop API
❗ Implementation of an ink! programmable DAO pallet allowing quick creation of DAOs
The above deliverables related to the ProgrammableDAO task were replaced by the implementation of Revive Compatibility and is estimated to be fully completed during August.
OG Tracker Review
The proposal's duration was extended by 2 months.
It is clear that the team has dedicated significant time and effort to the proposal, with most of the expected tasks already delivered, and they actively working upon the remaining items until are fully completed.
Additionally, the team was highly responsive and transparent.
They answered all our questions in depth and provided extended updates and information related to the proposal.
Past Performance is our second experimental approach, after OGT Rating, to target pre-approval practices and help voters make better informed decisions.
We share our findings and further insights about the previous proposer's work and its overall status.
Edited
JAM Implementers DAO votes NAY on this proposal.
Key reasons:
🔻 Unclear current adoption
Despite the compelling vision around AI-integrated tooling, we couldn’t identify at least two real ecosystem teams currently relying on or planning to adopt this tool. Without a proven need, the $ 577,000 USDC request feels premature.
🔻 Uncertain impact on Polkadot’s core dev stack
Several JAM DAO devs have tested POP AI at hackathons — and while the concept is promising — there’s little evidence it significantly improves current developer workflows or ecosystem UX. Most of the core stack remains CLI-driven and tightly integrated with Substrate SDKs and tools like Bagpipes.
🔻 Better developer outcomes elsewhere
We believe Treasury funding for developer productivity should focus on accelerating usage and onboarding. Prioritizing direct CLI tooling improvements or integrations (like Bagpipes or substrate-indexer pipelines) would provide broader ecosystem value.
🔻 No battle testing or production adoption
While we acknowledge the Rogue team’s track record, this tool hasn’t yet been deployed in the trenches. If this is a critical tool for developer adoption, let’s see it in action before scaling Treasury funding.
We encourage the team to reapply in the future with:
Before Pop CLI was a thing, I usually thought to myself: "We need a CLI to scaffold parachains". Developers are extremely used to using CLIs for creating projects. Web developers use them all the time, especially for frontends with javascript but also for backends with tools such as rails or django. If we want to make Polkadot more appealing to developers outside of Web3, if we want to make it easy for developers to build on Polkadot, then a CLI is a great way of doing so. Pop CLI filled that need and it did so with impressive features like
pop callfor interacting with chains and signing via the browser and scaffolding smart contracts as well.The objectives mentioned in the proposal align with the vision of making Polkadot friendlier and more accessible to developers. Being able to spawn mock networks with the state from live chains already filled in will be a huge win for new developers wanting to test their project. Frontend templates make it very appealing as a "fullstack" CLI, pushing the adoption of the latest and greatest, like PAPI. I was initially intrigued by the usage of AI in the proposal but after reading it, I think it makes a lot of sense, as long as the user is prompted to accept the generated command before executing it :P
Pop CLI, PDP, chopsticks, zombie-byte, papi, polkavm, we really are witnessing a new generation of tools to build on Polkadot that make it easier than ever before.
Props to the team!