With [Referendum #783](https://polkadot.polkassembly.io/referenda/783), LimeChain began the development of the devGround platform, focused on the implementation of new developer tools using the Polkadot-API (PAPI). It offers a suite of tools designed to help developers streamline development and debugging, enabling rapid prototyping and exploration of on-chain information seamlessly across the entire Polkadot ecosystem in a more intuitive way. Since then, we have delivered on the treasury proposal, gathered feedback, and published a detailed progress report, available [here](https://docs.google.com/document/d/1o4COqY5yQnOkC7kmR90Opjpoi0TZAze4DnnvXH7gXGk/edit?tab=t.0).

In Phase 2, we aim to enhance the developer experience on Polkadot further. The full proposal document for devGround Phase 2 can be found in the Google Docs document [here](https://docs.google.com/document/d/1hQ3M4tx7jiNyG3NdurW-IgUUmJJoLuB92GMb5eoWqcA/edit?tab=t.0#heading=h.v6is2ta0txr1).

**TL;DR**
In Phase 2 of devGround, we are turning the JavaScript IDE into a collaborative, shareable coding environment, improving the explorer with deeper on-chain insights, and adding utility pages tailored to real developer workflows. Our focus is on saving developer time, reducing context switching, and making devGround a daily-use tool across Substrate-based chains. These upgrades aim to streamline development, learning, and debugging in the Polkadot ecosystem.

**Ecosystem Benefits:**
By enhancing devGround into a unified, practical hub for runtime, dApp, and parachain developers, we reduce tool fragmentation and shorten the learning curve across parachains. This makes it easier for newcomers to onboard, for teams to collaborate, and for experienced builders to move faster; ultimately helping the entire Polkadot ecosystem scale more efficiently and attract more developers.

The total treasury request for this proposal is ***172,210 USDC****,* distributed across 4 milestones.

Any additional feedback or ideas for the enhancement of the devGround platform are greatly appreciated and welcome.&#x20;

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.

#1644 devGround Phase 2

No Active Proposals