Pop CLI was initiated in late 2023 by R0GUE, a team of ex-Parity engineers deeply experienced with the Polkadot ecosystem. Recognizing the complexity and fragmentation faced by developers, the team identified a critical need for an all in one tool for Polkadot Development. In mid-2024, Pop CLI received a Decentralized Futures grant from the Web3 Foundation, evolving into a production-grade tool with strong ecosystem adoption (read the [full story](https://medium.com/@r0gue/pop-cli-reimagining-the-polkadot-developer-journey-4c38fe21483b)).

*“Collaborating with the R0GUE team was highly positive—the robust documentation, user-friendly Pop CLI, and excellent support to deploying teams were consistently impressive.” —* **Web3 Foundation**

The Pop CLI supports the full development lifecycle for both Polkadot chains and smart contracts. It features secure transaction signing, integration and [partnership](https://x.com/PolkadotDeploy/status/1906643927911792654) with the Polkadot Deployment Portal (PDP), integration with OpenZeppelin and includes advanced features for testing, benchmarking and much more. More recently it has been [recognised in Polkadot's documentation](https://docs.polkadot.com/develop/toolkit/parachains/quickstart/pop-cli/). 

This proposal seeks funding to further enhance Pop CLI's functionality, usability, and infrastructure. Specifically, funding will support local network bootstrapping with live state, full-stack starter kits and OmniNode integration, state query functionality, AI integration, contract verification, continuous maintenance and UX improvements, and focused developer education, distribution and community collaboration.

You can review all the details of the proposal in the following Google Doc: [https://docs.google.com/document/d/1jdfnwWAW4EIBu2UFiXmFry1NXTu3QO20lkjjVpF\_4q4](https://docs.google.com/document/d/1jdfnwWAW4EIBu2UFiXmFry1NXTu3QO20lkjjVpF_4q4/edit?tab=t.0)

\---

## Change Log

**Section:** AI integration

**Date:** 30-06-25

In response to feedback from 0xTaylor (at KusDAO), we’ve made updates to clarify and strengthen our approach to AI integration in the Pop CLI. While our original proposal emphasised a single-prompt interface, we agree that this alone doesn’t reflect how developers actually want to work. We had already been exploring more flexible options, including conversational interaction and the use of an MCP server. These changes clarify our intent to support both modes of interaction and to lay the foundation for more powerful, agentic AI workflows.

**IMPORTANT**: Nothing has changed in terms of the total amount of time needed and thus the costs.

\---

Go R0GUE

Propose and approve a spend of treasury funds.

## Dispatch Origin

Must be [`Config::SpendOrigin`] with the `Success` value being at least
`amount` of `asset_kind` in the native asset. The amount of `asset_kind` is converted
for assertion using the [`Config::BalanceConverter`].

## Details

Create an approved spend for transferring a specific `amount` of `asset_kind` to a
designated beneficiary. The spend must be claimed using the `payout` dispatchable within
the [`Config::PayoutPeriod`].

### Parameters
- `asset_kind`: An indicator of the specific asset class to be spent.
- `amount`: The amount to be transferred from the treasury to the `beneficiary`.
- `beneficiary`: The beneficiary of the spend.
- `valid_from`: The block number from which the spend can be claimed. It can refer to
  the past if the resulting spend has not yet expired according to the
  [`Config::PayoutPeriod`]. If `None`, the spend can be claimed immediately after
  approval.

## Events

Emits [`Event::AssetSpendApproved`] if successful.

#1619 Pop CLI: An All-in-one Tool for Polkadot Development

No Active Proposals