NOTE &mdash; Due to some calculation errors and community feedback on the proposal, we have decided to withdraw the proposal in its current state and we plan to create a followup proposal incorporating the feedback and limited scope of development.&nbsp;
We thank everyone who supported this proposal and look forward to everyone's support on the updated proposal.&nbsp;
Regards,
Polkassembly Team

**NOTE** — _Due to some calculation errors and community feedback on the proposal, we have decided to withdraw the proposal in its current state and we plan to create a followup proposal incorporating the feedback and limited scope of development._ 

_We thank everyone who supported this proposal and look forward to everyone's support on the updated proposal._ 

_Regards,_

_Polkassembly Team_

Polkassembly serves as Polkadot and Kusama's primary governance hub, enabling participation in on-chain governance, delegation, proposal discussions, and community voting. As OpenGov evolves and JAM is introduced, we propose the following roadmap for 2025:
✅ Integration of JAM governance tools for extended cross-chain coordination
✅ New analytics and transparency tools for referenda, delegations, and fellowships
✅ Decentralized funding mechanisms to reduce reliance on the treasury
✅ Enhancements to mobile apps, social engagement, and bounties
Our iterative, agile development approach has allowed us to quickly deliver high-impact features while ensuring that user experience remains at the core of our platform.
This community-first mindset has driven significant enhancements across governance analytics, delegation transparency, and social engagement features. We have also focused on increasing accessibility for both new and experienced users, bridging gaps in OpenGov participation and governance tooling.
Key milestones and impactful developments from the past 12 months include:
Governance Analytics Enhancements
<ul>
<li>Added referendum, track, and governance-level insights.</li>
<li>Provided detailed voter participation analytics, delegation patterns, and key decision-making trends such as turnout and conviction splits.&nbsp;</li>
</ul>
Delegation Dashboard Upgrades
<ul>
<li>Introduced trending delegates and detailed delegation statistics.</li>
<li>Enabled badge-based recognition for high-performing delegates.</li>
<li>Improved tools for delegators to track and optimize their delegations.</li>
</ul>
Social Engagement Features
<ul>
<li>Launched a real-time social dashboard featuring live notifications, activity feeds, and user engagement tracking.</li>
<li>Improved follower-based updates to help users track governance developments.</li>
</ul>
Bounty Product Implementation
<ul>
<li>Developed a comprehensive bounty timeline, allowing users to track bounty status from initiation to completion.</li>
<li>Introduced a curator dashboard to enhance bounty management and accountability.</li>
<li>Implemented child and main bounties with advanced categorization for structured funding distribution.</li>
<li>Developed a User Created Bounties feature that allows bounties being funded by users beyond the treasury.</li>
</ul>
Checkout the <a href="https://x.com/polk_gov/status/1874341508716933141/video/1">Polkassembly 2024 roundup video&nbsp;</a>below -
<video controls="controls" width="500" height="250">
<source src="https://firebasestorage.googleapis.com/v0/b/polkassembly-backend.appspot.com/o/ssstwitter.com_1738241513795.mp4?alt=media&amp;token=d2f86d97-4c99-4e21-baf6-1a408714c552" /></video>
Implementation Gallery
&nbsp;
<img src="https://i.imgur.com/V5EO9za.png" alt="Implementation" width="617" height="451" />
<img src="https://i.ibb.co/fVDJx9XW/image.png" alt="image.png" width="617" height="350" />Upcoming Features 
Over the past year, Polkassembly has evolved in response to the growing complexity of Polkadot governance, offering tools that enhance accessibility, transparency, and efficiency. As governance frameworks expand and new participation models emerge, further improvements are necessary to strengthen user engagement .
The following enhancements are designed to:
<ul>
<li>Improve governance accessibility by integrating interactive analytics and proposal tracking.</li>
<li>Expand governance infrastructure by introducing JAM-based governance middleware, multichain support, and extended off-chain participation tools.</li>
<li>Enhance community collaboration with regional community dashboards, organization-based governance, and structured funding alternatives.</li>
<li>Refine the governance experience through mobile-first optimizations, and gamified learning elements.</li>
</ul>
These upgrades will ensure that Polkassembly continues to provide a dynamic and efficient governance coordination layer for Polkadot, Kusama, and parachains.
This submission covers costs for 2025. The full proposal is available <a href="https://docs.google.com/document/d/1D-0m8SYd0x6xm5hvsB2PR7jXegqHw15UoytrbL_owxg/edit?usp=sharing" target="_blank" rel="noopener">here</a>.

Polkassembly Social Contract 2025

Treasury

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.

- **Problem Statement:** Proposal withdrawal due to calculation errors and community feedback.
- **Significance:** Ensuring accuracy and community input in the proposal process.
- **Proposed Solution:** Create a follow-up proposal incorporating feedback and limited scope of development.
- **Expected Outcomes:** Improved proposal accuracy and community support.

#1434 Please vote Nay

No Active Proposals