Polkassembly is an integral part of polkadot and kusama governance. This submission proposes a recurring payment (quarterly) to cover maintenance, operations and human resource costs for Polkassembly, including general maintenance, runtime upgrades changes and could/infrastructure cost. 
Since Polkassembly supports both Kusama and Polkadot Networks, this maintenance proposal will alternate networks for submission every three months. This submission covers costs for October, November and December of 2022. We are requesting the Polkadot treasury to provide funds this time.

The proposal details the work done in past from our previous proposal and the things we plan to implement in this quarter. 

The full proposal is available [here](https://docs.google.com/document/d/1-cm0QQDljqIGu7tFXI3wQz8-PsrKXb6QN3lSMElV9lk/edit?usp=sharing). 

Social Contract between Polkassembly and Polkadot Treasury

Polkassembly is an integral part of polkadot and kusama governance. This submission proposes a recurring payment (quarterly) to cover maintenance, operations and human resource costs for Polkassembly, including general maintenance, runtime upgrades changes and could/infrastructure cost. Since Polkassembly supports both Kusama and Polkadot Networks. This submission covers costs for January, February, March of 2023. We are requesting the Polkadot treasury to provide funds this time.

The full proposal is available [here](https://docs.google.com/document/d/1q3Byq4BN-OJAA0l4v51H3ye71SiorweoYPabB-jF41I/edit#). 

Social Contract between Polkassembly and Polkadot Treasury Q1'23

Polkassembly has been migrated to new backend. Polkassembly link sharing now allow title description to be shown in social graph. Please let us know if you face any errors.

Thanks

New API is available at https://documenter.getpostman.com/view/764953/2s93JxqLoH#181400b9-281a-44d2-91ff-93f9f6bf079e

New backend for polkassembly

We're excited to announce that we'll be giving away a free "Polkadot for beginners by [Gbaci](https://twitter.com/gbaciX)"  book at our booth in the Polkadot Now event in Bangalore! To enter, all you have to do is leave a comment on this post. We'll be selecting commenters to receive a copy of our featured book.

Don't miss out on this opportunity to add a new read to your collection! Make sure to comment on this post before the deadline to be considered. Winners will be announced at the event and must be present to claim their prize. Good luck! (edited) 


Claim a Free Book at Polkadot now India Event - Comment to Enter!

Polkassembly is an integral part of Polkadot and Kusama governance. It is dedicated to fostering transparent governance and active participation within the Kusama and Polkadot ecosystems. The team is excited to announce its application to become a registrar.

- On-chain identities in the Polkadot ecosystem are crucial for trust, accountability, and interoperability. By establishing unique digital fingerprints, participants can securely interact within the network. An on-chain identity fosters a reliable and verifiable framework for participants within the Polkadot ecosystem, which is governed by a defined set of rules. It enables seamless integration and collaboration between different projects and stakeholders.
- It also builds accountability as the participants are vetted and there are multiple points of contact for an individual/team. Hence, when requesting funds or proposing changes, the network and its resources have an additional layer of protection via the verification process. 

The goal of setting an on-chain identity is to enhance transparency, security, and the overall ease of interaction between the participants of the Polkadot and Kusama ecosystems.

Problems in current on chain identity system

- The current process for verifying the identity is extremely fragmented
- The process requires a heavy reliance on navigating through PolkadotJS, which can be overwhelming to those who are new to the ecosystem
- Twitter, Element and email verification is done manually and the process is very complicated for any user. The verification process also relies on availability of the registrar, creating further friction in the process. 
- The process is also broken away from the governance and proposal creation interface, which makes it difficult for a lot of the community as they need to adapt to multiple tools for serving different use cases. 

**Objective for Registrar Application**

- The primary objective of creating the registrar application is to build an easy and integrated governance experience for all users within Polkassembly. 
- This involves building for automation of proposal creation, addition of education nudges on proposal evaluation, verification of on chain identities and comprehensive user level profiling with leaderboards and gamification for governance participants
- Taking the onus for ensuring verification of users and building security for funds requested from treasury
- All teams requesting funds should be able to create an onchain identity, verify themselves and use our product suite to create a multisig (via Polkasafe or any other publicly available multisig SDK) when requesting for funds
- The time required for identity registration and verification will be reduced by more than 75%, enhancing the adoption of the feature and enabling a more robust and secure treasury management. 
- The number 75% was deduced by using the average time difference between the two methods for 3 unique users
- The time required by the earlier method was 20-25 mins, and via Polkassembly will be approximately 5 mins

**How will Polkassemby enable users to apply for on chain identity verification?**

Attached below is a step wise explanation of how Polkassembly plans to receive and process on chain delegations 

Step 1 - 

- Discovery on on chain identity setup
- Users will be provided with contextual nudges on Polkassembly for setting up on chain identity

![image](https://i.ibb.co/5Y7H1GM/2-premiurly-1686255544576.png)

Step 2 - 

- Educating users on what is on-chain identity and why is it important
- Explaining the process of setting up and on chain identity and how verification works
- Helping users understand how to identify users with a valid on chain identity
- Clear communication on the total amount required (Please note the amount mentioned is representative and may vary based on market conditions)
- The breakdown of the feed will also be provided
 
![image](https://i.ibb.co/SrPRbYt/2-premiurly-1686255581602.png)

Step 3 - 

- Providing the user with an interface to share all their social and contact information
- The user will be allowed to choose any one of their address which they want to verify
- They can choose their legal and display name
- They can identify their social handles for further communication with the community
- They are informed about the bond, which is mandatory while setting up an on chain identity 
- They are also informed about the fees charged for setting up or changing the social handles, which will be the fee per handle * # of handles being verified 

![image](https://i.ibb.co/Nt9Z606/2-premiurly-1686255656060.png)

Step 4 -

- Confirming the fees and initiating the step by step identity verification process
- Each social handle will need to be independently verified after the input is provided 
- Once all verifications are completed the success states will be provided

 ![image](https://i.ibb.co/54T72HK/2-premiurly-1686255690524.png)

![image](https://i.ibb.co/MpmzBRY/2-premiurly-1686255723505.png)

Other detailed steps and complete proposal can be found [here](https://docs.google.com/document/d/1wYkC09wMjC6KstW2E9VtHLgoRd1bV_GLhYoTOQ8gv8U/edit). 
We look forward to feedback from the community, suggestions to improve the product flow and support on our efforts to challenge the complex UX challenges of the Polkadot ecosystem. 

Regards,
Polkassembly Team

Polkassembly's Registrar Application

Polkassembly is an integral part of Polkadot and Kusama governance. We have been actively working on making the smoothest governance experience at Polkassembly for OpenGov. 

In our endeavor to do so, we completed our first milestone with the theme of migrating and adapting Polkassembly to all OpenGov related changes and successfully delivered on the same by Feb end. 

The theme of the previous proposal was Technical & Product Based Migration, Education regarding OpenGov & Creation of an appropriate user experience for the large transition governance went through.  

The upcoming milestone aims to build Delegation as a simple, intuitive and exciting experience. We have developed our dashboard, with a user first mindset aimed at promoting agile governance.
The core goal is to be ecosystem thought leaders and innovators, working with other teams including Nova. We will bring forth a list of delegation candidates, along with their voting experience and activity statistics, in order to enable maximum adoption of delegation. 

Details of milestone 1 updates can be found [here](https://docs.google.com/document/d/14hg1lAfeAgrR4YimqxPp-6XGW3gsvGzYAQnowpNGxoE/edit?usp=sharing).

**New Product Development & Milestone 2**

## Theme: Delegation

#### Feature: [User Dashboard(Live)](https://kusama.polkassembly.io/delegation)

**Goal:** To allow users to access their wallet level delegation and profile details

**Tasks:**

- A Web3 wallet based personalized login experience which is linked to your Polkassembly login experience 

- Users can edit their bio to allow more users to delegate

- The dashboards shows User’s current available, locked and transferable balance

- Their profile details (sourced and linked to the Polkassembly or on chain profile)

- Tracks for which they have delegated, not yet delegated or received delegations

- A quick overview of track level information

#### Feature: [Delegation experience (Live)](https://kusama.polkassembly.io/delegation/root)

**Goal:** To allow users to delegate with ease and in an informed manner

**Tasks:**

- Users can select a particular track they want to delegate for

- Based on the track selected, users will be able to see the list of available delegates

- They can make a decision based on bio of the delegate, delegations they have received, proposals they have voted upon and total voting power

- In addition to choosing delegates, Users can see active proposals on the track

- If they have delegated, they can also see if the delegated user has casted a vote yet or not

#### Feature: Expanding available Delegates List (In Progress)

**Goal:** To allow users to have a wider variety of choice while delegating

**Tasks:**

- Tie up with those working on delegations across the industry to bring more candidates forward

- Create a native interface for users to submit themselves as delegates across tracks

- Work closely with ecosystem partners like Nova to develop an ecosystem wide product to accept nominations for delegation

- Importing the list of delegates available on the official polkadot delegation website


## Theme: Platform Growth & Development

#### Feature: Registrar Application Design (Done)

**Goal:** To allow users to have a supercharged and easy to use on chain verification experience

**Tasks:**

- Outlined in the following discussion posts
-  Kusama - [https://kusama.polkassembly.io/post/2585](https://kusama.polkassembly.io/post/2585)
- Polkadot - [https://polkadot.polkassembly.io/post/1815](https://polkadot.polkassembly.io/post/1815)
- The development for the same will be charged in our maintenance proposal as it is a larger public good effort


#### Feature: OpenGov Proposal Creation (In Progress)

**Goal:** To allow users to create OpenGov proposals via Polkassembly

**Tasks:**
- Creating proposals via PolkadotJs apps could be overwhelming for users and has scope for lot of errors

- Polkassembly will simplify this experience and make proposal creation simpler by linking the steps of preimage and proposal creation

- The Phase1 of this process is to enable the proposal and preimage creation process from within Polkassembly for treasury proposal. Phase2 will be creation of all proposals which will be a part of the later proposals.

**Goal:** Proposal creation from Polkassembly (Process)

**Tasks:**

- Users will be nudged to create a discussion post regarding their proposal

- After this, the preimage creation process will start. Leveraging the amount of the proposal, beneficiary and creator address, Polkassembly will recommend the track for creation of the proposal

- The preimage will be automatically linked if the user proceeds to the proposal where they can pay the submission deposit and the proposal will be generated on chain. The off chain description will be populated based on whether the discussion is linked or not. 

- The users can then pay the decision deposit at any point of time during the voting phase

## Theme: Accessibility & Experience

#### Feature: Proposal Listing view changes (In Progress)

**Goal:** To allow users to have a seamless UI while accessing proposal

**Tasks:**

- A new and upgraded listing view which enables a better platform experience 
- Treasury amounts shown upfront for all treasury related proposals
- Tags for Gov1 & OpenGov Proposals (Done)

- Easy filtering of proposals into four parts - All Proposals, Submitted, Voting and Closed(Done)

#### Feature: Search (In Progress)

**Goal:** To allow users to experience a top notch unified search experience 

**Tasks:**

Search will be broken into two parts - Search - Chain level search
- Super Search - Site wide search, a very powerful search across all Governance Proposals in Polkadot Ecosystem
- Search Features: 
- Discussion and Off chain search 
- Users will have the option to search keywords in titles and description of proposals 
- Referendum Level and On chain search
- Users will have the option to search keywords in titles and descriptions of discussions
- User level search where users can search by keywords to receive on chain usernames and off chain usernames

## Theme: User Interface Upgrades

#### Feature: New account settings page (In Progress)
**Goal:** To enable easy interactions for various account settings

**Tasks:**

- Easy interface for password, username or email change
- Upgraded interface for linking addresses, multisig and proxies in Polkassembly. 

#### Feature: Dark mode (In Progress)

**Goal:** To allow users to set their user interface as per their preference

**Tasks:**

- Sitewide deployment of dark mode to support users who prefer leveraging a dark mode interface

- Modifying all elements across flows including user profiles, on chain governance activity (Gov1 & OpenGov), off chain activity, delegation and overview pages 

 - Combining the effort of zooming out the interface to make a more comfortable default experience for users

#### Feature: Voting interface upgrades(Live)

**Goal:** To allow users to vote on proposals with more options and have a better voting experience

**Tasks:**

- Clear indication of the last vote casted by the user on the UI
- The ability to vote using split and abstain as options in OpenGov(Live)
- A new and improved voting interface(Live)

## Theme: Polkadot OpenGov Deployment

#### Feature: Deploying all core features for OpenGov to Polkadot (Live)

**Goal:** To upgrade Polkassembly’s Polkadot interface to OpenGov

**Tasks:**
- The list of feature deployed for Polkadot are similar to Kusama as mentioned in the Kusama Proposal: [OpenGov Treasury proposal](https://docs.google.com/document/d/1vWOiKBG_lARiy0EXDATxvt0htJ_N_LmtOnzirutAvns/edit). 
- The remaining tech effort spent on the migration for Polkadot has been billed in this proposal
- Marketing and promotional efforts including the setup of the OpenGov Proposal timer. 
- Announcement: https://twitter.com/polk_gov/status/1667146568258969601

#### Feature: Deploying delegation dashboard for Polkadot (Live)

**Goal:** To allow users to vote on proposals with more options and have a better voting experience

**Tasks:**

Links for reference
- [Dashboard](https://polkadot.polkassembly.io/delegation)
- [Track Level Delegation experience](https://polkadot.polkassembly.io/delegation/root)

## Theme: Security

#### Feature: 2 Factor Authentication (Live)

**Goal:** To allow users to secure Polkassembly accounts

**Tasks:**

 - 2FA authentication integration to provide seamless security upgrade
- New API provided to all partners in the ecosystem to deliver a more robust and improved performance.
- This also includes the process of migration of existing Polkassembly APIs to Opengov 

**Implementation Gallery**

![image](https://i.ibb.co/r45mWXH/2-premiurly-1687437748485.png)

*The user dashboard interface for delegation dashboard*

![image](https://i.ibb.co/8Kqmy0Y/2-premiurly-1687437809680.png)

*Track level delegation experience*

![image](https://i.ibb.co/y0jXgwh/2-premiurly-1687437843020.png)

*Two Factor Authentication Setup*

Other details about implementation, detailed cost calculations and milestone 3 are available in the detailed proposal [here](https://docs.google.com/document/d/14hg1lAfeAgrR4YimqxPp-6XGW3gsvGzYAQnowpNGxoE/edit?usp=sharing). 

Treasury proposal for New Product Development & OpenGov Deployment

Polkassembly is an integral part of Polkadot and Kusama governance. This submission proposes a recurring payment (half yearly) to cover maintenance, operations and human resource costs for Polkassembly, including general maintenance, runtime upgrades changes and could/infrastructure cost. We have transitioned to a half yearly method to improve on the scope of our deliverability and execute larger changes to our platform. This submission covers costs for Q3 &amp; Q4 of 2023. The maintenance proposal alternates between Polkadot &amp; Kusama treasury and we are requesting the Polkadot treasury to provide funds. This recurring proposal aims to secure the continuous operation and sustainability of Polkassembly, a vital component of Polkadot and Kusama governance. To ensure the smooth functioning of Polkassembly, we request a payments to cover essential expenses such as maintenance, operations, and human resources. The funds are allocated towards general maintenance, runtime upgrades, and infrastructure costs, guaranteeing the reliability and efficiency of Polkassembly. Attached below are key highlights of our proposal: 
Voting &amp; Transparency Upgrades:
<ul>
<li>Voting Details on Referendum (Live): Enhance the proposal page to show users' self vs. delegation vote split, detailed breakdown of delegators, and more.</li>
<li>Vote History in Profile (Live): Display voting history in user profiles, including self vs. delegated votes.</li>
<li>Reason for Voting (Live): Enable users to add voting reasons immediately after casting their votes.</li>
<li>Vote Anonymously: Allow users to hide their identity while voting.</li>
<li>Share reason for voting: Enable users to share voting reasons on social media.</li>
<li>Unlocking token locks: Simplify unlocking locked tokens.</li>
</ul>
New Features:
<ul>
<li>AI Summary (Live): Provide a quick summary of proposals.</li>
<li>Tooltip &amp; Tipping: Allow users to tip others and view tipping history.</li>
<li>Statistics: Display on-chain balances and user activity details.</li>
<li>Microfeatures: Enhancements to existing features.</li>
<li>Markdown &lt;&gt; Rich Text Editor Support: Toggle between markdown and rich text editors.</li>
<li>See more proposals: Recommend and display related proposals on detail pages.</li>
</ul>
Partnerships:
<ul>
<li>Moderation (Live): Enable Polkadot &amp; Kusama forum moderators to moderate on Polkassembly.</li>
<li>Polkasafe Integration: Utilize multisigs and proxies for governance interactions.</li>
</ul>
Maintenance &amp; Site-wide Migrations:
<ul>
<li>Husky Setup: Implement Git pre-commit hooks for code quality.</li>
<li>Redux setup &amp; remove contexts: Optimize state management for performance and debugging.</li>
<li>Remove Styled Components; implemented CSS modules: Refactor components to improve performance and eliminate hydration errors.</li>
</ul>
Additional Upgrades:
<ul>
<li>Optimistic Updates: Improve user experience and speed for actions like reactions and comments.</li>
<li>V2 DS &amp; Routed APIs: Simplify and optimize APIs.</li>
<li>Timeline UI upgrade: Enhance the timeline for on/off-chain events and proposal progress.</li>
<li>Navigation bar: Improve visibility and accessibility.</li>
<li>Open any profile: Allow viewing of any on-chain account.</li>
<li>JSDoc: Provide documentation for functions to facilitate open-source contributions and development.</li>
</ul>
These upgrades aim to enhance user engagement, transparency, and the overall experience on Polkassembly while streamlining development and maintenance processes. Please <a href="https://docs.google.com/document/d/1tFFRSIvtsa0fuzpzeESyrippWT3emkjIkiVAUMnh2kU/edit?usp=sharing">click here</a> to view the full proposal

Polkassembly Maintenance proposal Q3 & Q4’23

When Polkadot discussions start to happens? I guess after sudo removal. 

Too silent here.

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

Polkassembly serves as Polkadot and Kusama's primary governance hub, enabling participation in on-chain governance, delegation, proposal discussions, and community voting.
This proposal seeks funding from the Polkadot Treasury to support Polkassembly's 2025 maintenance and key improvements in stability, user experience, and core features. It focuses on essential upgrades such as better UX/navigation, enhanced identity management, technical stability, and spam prevention &ndash; that will strengthen the platform&rsquo;s reliability and usability for the community
What&rsquo;s our focus with this proposal?
The primary focus for improvement is summarized as below:
<ol>
<li>Identity -
<ol>
<li>Increase stability in core flow.</li>
<li>Simplify things for multisig account identity setup and fix issues.</li>
<li>Add support for proxy-identity setup.</li>
<li>RPC connectivity issues to be resolved on priority.</li>
</ol>
</li>
<li>Comments AI summary &amp; load speed improvement.</li>
<li>Comments for Proxy and Multisig accounts revamp.</li>
<li>Proposal creation
<ol>
<li>Improve support for multi-asset proposals.</li>
<li>Improve the proposal creation process for different tracks and scenarios.</li>
<li>Add support for proposal creation through proxy and add support for multisig proposal creation.</li>
</ol>
</li>
<li>Add support for more wallets including Nova, Mimir, Polkagate Snap, Signet.</li>
<li>Improve hardware wallet connectivity and functionality across all features.</li>
<li>Redo the landing page to improve discovery and site navigation.</li>
<li>Improve the proposal&rsquo;s detailed view layout to make information more accessible</li>
<li>Site-idle connectivity issues and data loading.</li>
<li>Reduce steps in proposal creation &amp; bundle decision deposit.</li>
<li>Create a proxy management dashboard and explorer Improve UX and platform navigation.</li>
<li>Add product walkthroughs for new user onboarding.</li>
<li>Add support for OpenGov Nomination Pool wallet voting for all wallet types.</li>
<li>Add comment filtering (DV, Proposer, Verified Accounts, Wallet linked).</li>
<li>Improved Preimage management and add option to convert pre-image into proposal directly through all wallet types.</li>
</ol>
Technical Improvements
<ol>
<li>Upgraded to Next.js 15 with Turbopack support for improved development experience</li>
<li>Node 20 support (compared to Node 18 in v1)</li>
<li>Revamped Editor</li>
<li>Better organized component architecture. Overhauled state management with Jotai Atoms.</li>
<li>New design system Integration along with shadcn/ui component system.</li>
<li>Overhauled project configuration with focus on security for easier open-source contribution.</li>
<li>The API architecture has been overhauled to improve data organization and facilitate easier integration for community members.</li>
<li>The API now offers expanded content delivery capabilities, enabling the return of data in markdown, block and HTML formats.</li>
<li>The authentication mechanism has been updated to utilize HTTP cookies for session management, replacing the previous implementation that relied on local storage and JWT.</li>
</ol>
Other technical improvements and details can be found within the <a href="https://docs.google.com/document/d/17ueaWqQcWpYmskJhrg3s3PPsFGEyzc4qea4XI4aBerw/edit?usp=sharing">proposal document</a>.&nbsp;
Proposal 2024
Here&rsquo;s the <a href="https://app.ogtracker.io/bigSpender/483">OG tracker ref link</a> for our 2024 proposal and a <a href="https://docs.google.com/document/d/1iKgCOzIAMwFvIiYHl3PrBIQkxv5_pCdhdmRMIhFSvaA/edit?usp=sharing">detailed self report</a> with features and product updates from last year&rsquo;s proposal. We worked with some amazing video designers to create a Polkassembly 2024 roundup. Users can watch the video <a href="https://x.com/polk_gov/status/1874341508716933141/video/1">here</a>.
<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;
Several UI/UX enhancements are actively being developed to refine navigation, improve usability, and ensure a better governance experience.
<img src="https://i.ibb.co/Zz98ssJH/1.png" alt="Revamped Proposal Listing View" width="640" height="588" />
Revamped Proposal Listing View
<img src="https://i.ibb.co/whBV3c05/2.png" alt="Revamped Proposal Detail view" width="640" height="881" />
Revamped Proposal Detail view
<img src="https://i.ibb.co/G4dNzHpk/3.png" alt="Revamped Profile Page" width="640" height="1169" />
Revamped Profile Page
<img src="https://i.ibb.co/Pz3y70hb/4.png" alt="Spam Proposal Detailed View" width="639" height="542" />
Spam Proposal Detailed View
<img src="https://i.ibb.co/hJ5ZH6JR/5.png" alt="Spam comments" width="640" height="385" />
Spam Comments
<img src="https://i.ibb.co/wZdw3wYF/6.png" alt="Delegation Dashboard &amp; Chat with delegates" width="639" height="405" />
Delegation Dashboard &amp; Chat with delegates
<img src="https://i.ibb.co/dsMbsKH0/7.png" alt="Bounty Dashboard" width="640" height="391" />
Bounty Dashboard
<img src="https://i.ibb.co/kgzCVJyb/8.png" alt="Batch Voting" width="640" height="403" />
Batch Voting
<img src="https://i.ibb.co/tTbt7pMS/9.png" alt="Proxy Dashboard" width="640" height="519" />
Proxy Dashboard
<img src="https://i.ibb.co/V0MspcgC/10.png" alt="Analytics Dashboard" width="640" height="716" />
Analytics Dashboard
&nbsp;
Our stats reflect our continued dominance in the ecosystem
Theme Product Metric Engagement on Polkassembly
Number of users
<ul>
<li>Last 30 days visits - 145K&nbsp;</li>
<li>Total API Requests - 92M/month (Source: Cloudflare)</li>
<li>MAU - 97k (Source: Google analytics)</li>
</ul>
Number of comments
<ul>
<li>Total Number of Comments on Polkassembly - 13695</li>
<li>Total Percentage of comments in governance on Polkadot - 82.66% (6288/7607)</li>
<li>Total Percentage of comments in governance on Kusama - 68.2% (502/736)</li>
</ul>
Number of disucussions
<ul>
<li>Total Number of Discussions on Polkassembly &mdash; 2206</li>
<li>Total Percentage of discussions in governance on Polkadot - 93.69% (698/745)</li>
<li>Total Percentage of discussions in governance on Kusama - 76.19% (32/42)</li>
</ul>
Number of Proposals
<ul>
<li>Total Percentage of proposals in governance on Polkadot - 39%+</li>
<li>Total Percentage of proposals in governance on Kusama - 20%</li>
</ul>
Source: Polkassembly Firebase
Views
Total Views last 4 months: 750K+ (Polkadot + Kusama)
Source: Polkassembly Firebase
Identity Verification
Number of Judgements provided
Total Percentage of judgements Polkadot - 52.22% (1216/2327)
<table style="border-collapse:collapse; width:52.9907%; height:30px;" border="0.5" cellspacing="0.1">
<tbody>
<tr>
<td style="width:50.085%; height:84px;">
Category&nbsp;
</td>
<td style="width:49.9163%; height:84px;">
Amount (US$)&nbsp;
</td>
</tr>
<tr>
<td style="width:50.085%; height:49px;">
Infrastructure &amp; Maintenance (12 months)
</td>
<td style="width:49.9163%; height:49px;">
$203,659
</td>
</tr>
<tr>
<td style="width:50.085%; height:49px;">
Development Budget
</td>
<td style="width:49.9163%; height:49px;">
$327,012
</td>
</tr>
<tr>
<td style="width:50.085%; height:10px;">
Total
</td>
<td style="width:49.9163%; height:10px;">
$530,671
</td>
</tr>
</tbody>
</table>
The budget calculations can be found <a href="https://docs.google.com/spreadsheets/d/1gQeTVOccQofkIcxJDqafQ657P_cSMmTiFK6Gck3xfeA/edit?usp=sharing">here</a>.&nbsp;
Refer to the full proposal document <a href="https://docs.google.com/document/d/17ueaWqQcWpYmskJhrg3s3PPsFGEyzc4qea4XI4aBerw/edit?usp=sharing">here</a>.&nbsp;

Multi Option Polls feature is added to polkassembly. Post author can add any number of polls with multiple options using create poll button. Users can vote offchain on the polls. You can click on options to vote on options



Polkassembly update: Multi Option Polls are here

[Polkassembly](https://polkadot.polkassembly.io/) is an integral part of polkadot and kusama governance. This submission proposes a recurring payment (quarterly) to cover maintenance, operations and human resource costs for Polkassembly, including general maintenance, runtime upgrades changes and could/infrastructure cost. Since Polkassembly supports both Kusama and Polkadot Networks, this maintenance proposal will alternate networks for submission every three months. This submission covers costs for July, August, September of 2021. We are requesting the Polkadot treasury to provide funds this time.

The full proposal is available [here](https://docs.google.com/document/d/1iyV_F6L9FjGx6gAf8EdTDFsENGqWhpfqYYFYTRZNXHo/edit?usp=sharing)

We have added a page for [council](https://polkadot.polkassembly.io/council). Council Members can edit the page to provide more info about them. 


New Polkassembly Feature: Council page

Polkassembly is an integral part of polkadot and kusama governance. This submission proposes a recurring payment (quarterly) to cover maintenance, operations and human resource costs for Polkassembly, including general maintenance, runtime upgrades changes and could/infrastructure cost. Since Polkassembly supports both Kusama and Polkadot Networks, this maintenance proposal will alternate networks for submission every three months. This submission covers costs for January, February, March of 2022. We are requesting the Polkadot treasury to provide funds this time.

The full proposal is available [here](https://docs.google.com/document/d/1hb3d_wItFmijFTG_hbQEtCoLaeiLfaNlc0iY5GCS-LQ/edit?usp=sharing)

This submission proposes new features on the Polkassembly platform. The product roadmap outlines the transition and development of Polkassembly platform to improve UX, enhance UI and add some features which will bring a lot of value to the users of the platform.

### Product philosophy + Milestones/Features
Please find our Pitch deck here - [Link](https://docsend.com/view/yzq59fr3zzquvkns)

**Note** - The product roadmap is flexible when it comes to prioritizing feature development and timelines are subject to change based on community requirements for features but consistent efforts will be made to ensure that every quarter there are more tasks done than mentioned in the milestones.

**Product plan**

The product roadmap primarily focuses on 3 things-

- Improve UI & UX of existing platform to ease governance discussions
- Add new features like treasury analytics, parachains info, events calendar, etc..
- Educate the community on Polkadot and substrate ecosystem and simplify the learning process for people moving from web2 -> web3(Tentative pipeline - [Link](https://docs.google.com/spreadsheets/d/1esbMkfIfZSYoLHor-y5v97pLHrDF8GnnoSrYg60INiU/edit?usp=sharing))

**Milestones**

[![](https://i.ibb.co/tm5CyPZ/pitchdeck.png)](https://ibb.co/r7Jynfb)


**Additional features that are in development in this quarter include**
- Create treasury proposal from Polkassembly platform(enhanced UX)
- Other features as requested by Council members, community and partner chains - Flexibility for adding more features beyond our defined roadmap will help Polkassembly become user’s go-to place for Governance and information on Polkadot ecosystem.
- Merge sign-in/sign-up process
- Improve website performance and load speed
- Introduce an option to select network when signing in
- Merge the treasury proposal creation process to provide a simplified UX to complete entire process on Polkassembly platform
- Treasury analytics page - Detailed treasury spend and inflow with latest events
- Personalized Notifications to stay updated on latest activity for a custom list of protocols
- Introduce rewards & NFTs for contributing voters and participants
- Make polkassembly live for multiple chains
- Addition of child bounty support: Feb W3
- Aggregation of data across multiple parachains: March W3
- Increased focus on educational content and ecosystem updates: Feb W3 
- Experience Overhaul & Upgrade for the Product (Polkassembly)
- Launch of updated Product Home: March W1
- Launch of update for all Product pages: April W1
- Enhanced landing page for each protocol. The protocol page will have the following information
- Description of protocol
- All relevant links - discord, twitter, github, reddit, youtube, etc
- An option for protocol owners to add custom links would be created later
- All relevant links - discord, twitter, github, reddit, youtube, etc
- News & Events and activity feed for that protocol
- Custom Calendar view for each protocol
- Enhanced view for various tabs - Treasury, Bounty, Tips, etc. 

Please find the mock design below along with the link to figma design file

![](https://i.ibb.co/h9PYtmg/homepage.png)
![](https://i.ibb.co/sH6w0jQ/calender.png)

Figma Design files for 

- [Home page](https://www.figma.com/proto/42APiTcMqSnnqT2zttgf9M/Polkassembly-Final?node-id=136145%3A256226&scaling=scale-down-width&page-id=136145%3A256110&starting-point-node-id=136145%3A256226&hide-ui=1)
- [Calendar](https://www.figma.com/proto/42APiTcMqSnnqT2zttgf9M/Polkassembly-Final?node-id=136155%3A230768&scaling=scale-down-width&page-id=136145%3A257324&starting-point-node-id=136155%3A230768&hide-ui=1)
- [Link Multisig](https://www.figma.com/file/ko3Sks2oLSnW7ogk7UoMQO/Link-Multisig?node-id=0%3A1)
- [Child bounty](https://www.figma.com/file/u6eNe9N0G1257aEyDpNFfK/Untitled?node-id=0%3A1)

**Features Completed**

**Polkassembly Website & Social**: Dec’21 to Present

- Creation of a homepage for Polkassembly to build towards the vision of educating users about governance in the Polkadot ecosystem
- Creation and development of social channels to increase the audience for governance discussions and build awareness

**Multi-Sig & Proxy**: Jan’22

- Integration of the ability to add multi-sig and proxy on Polkassembly, adapting the platform based on community feedback

**Moonbase Integration**: Jan’22 to Feb’22

- Launch and integration of feedback from the Moonbase team to bring the community to Polkassembly for Governance

**Design & Experience changes**: Jan’22

- Improving experience on login, settings and navigation
- Addition of error messaging

**Dashboard view for independent parachains**: Jan’22 to Present

- Improving the experience for users by allowing them to view all on-chain activities in a dashboard view for each parachain
- Viewing news, upcoming events, and much more as a part of the dashboard

**Calendar Integration**: Feb’22 to Present
- Integration of an on-chain + off-chain calendar for events in the polkadot ecosystem in a parachain agnostic form
- Allowing users to create events for greater visibility along with the option of adding events to their google/social calendar

**Improving integration of Treasury functions**: Jan’22 to Present
- Visibility on treasury proposals along with stats from the treasury
- Creation of treasury proposal from Polkassembly | The PRD and design is for Tips but the same would be used to develop it for Treasury Proposal
- [Design](https://www.figma.com/file/vLHdo4BJMDl0sliebC20MU/Create-treasury%2FTip-proposal?node-id=0%3A1)
- [Short PRD](https://www.notion.so/Create-Treasury-Proposal-20f975684aff48a088db8aff52ce8527)
- Linking discussion post to treasury
- Integration of treasury analytics

**Tip calculation and threshold data**: 
- Improved tips calculations and started showing proposer’s tip, expected tip and list of council members along with a status against each Jan’22


Total Proposal amount: 4690 DOT

Link to Proposal: [https://docs.google.com/document/d/1TRgHh5DJoVxlUUhCaaxV95ACcwCiErJ73ES6uAhji6o/edit?usp=sharing](https://docs.google.com/document/d/1TRgHh5DJoVxlUUhCaaxV95ACcwCiErJ73ES6uAhji6o/edit?usp=sharing)

Polkassembly Product Improvement Proposal

Polkassembly Social Contract 2024

Context of the proposal
Polkassembly has become an integral part of Polkadot and Kusama governance. Proposers use it to describe the details of the proposals. Council members are using it to discuss and coordinate voting on motions. Links of proposals and discussion of Polkassembly are used in various newsletters and apps.
The team has followed guidelines provided by Dr. Gavin Wood as well as recommendations from various fellows to make an engaging platform for fellows. You can find details of the in the note shared by Dr. Gavin Wood <a href="https://hackmd.io/33pI3HvlSkycp-1dQjRLZA#Induction">here</a>
Platform Details - <a href="https://collectives.polkassembly.io/?page=1">collectives.polkassembly.io</a>
Github - <a href="https://github.com/polkassembly/fellowship">https://github.com/polkassembly/fellowship</a>
The Polkadot Technical Fellowship, vital to Polkadot&rsquo;s governance and development, necessitated a specialized platform on Polkassembly for a couple of reasons,
First, the Fellowship's intricate role in overseeing and guiding Polkadot&rsquo;s protocol development required a dedicated space for in-depth technical discussions. A separate platform within Polkassembly ensures these complex conversations remain focused and clear, essential for high-level decision-making.
Second, a distinct platform will enhance the visibility and understanding of the Fellowship&rsquo;s contributions. In the vast ecosystem of Polkadot, where myriad discussions occur on Polkassembly, the Fellowship&rsquo;s work can easily be overshadowed. A dedicated space ensures their critical inputs and activities are prominent and accessible for other fellows, bolstering transparency and accountability in the network&rsquo;s governance. This will help account for their promotion / demotion cycles and ensures that fellows are contributing as per the rank and being rewarded for the same.
Lastly, this platform will act as a bridge between the Fellowship&rsquo;s technical expertise and the broader community. It will serve as an educational resource, demystifying complex decisions and fostering an informed, engaged community. This engagement is crucial for the health and success of Polkadot&rsquo;s decentralized governance model and fellowship.
Polkassembly&rsquo;s Fellowship product is thus a specialized platform for the Fellowship on Polkassembly enhancing decision-making, transparency, and community involvement in Polkadot&rsquo;s governance ecosystem.
Dashboard - <img src="https://i.ibb.co/CPbTGWN/2-Polkassembly-1703152462143.png" alt="image" />
Members - <img src="https://i.ibb.co/r29bNLQ/2-Polkassembly-1703152512513.png" alt="image" />
We are requesting the Polkadot Treasury to provide funds retroactively for the development of Fellowship product V1.
Please find the details of the proposal, budget, tasks and milestones <a href="https://docs.google.com/document/d/1lZGlBugwFcP_P5rfLpMyCFW49C_xqEkiFDA0zZETK3Y/edit?usp=sharing">here</a>.

 Proposal for retroactive funding of Fellowship product development.

Polkassembly is an integral part of Polkadot and Kusama governance. This submission proposes a recurring payment (half yearly) as part of our social contract with the Polkadot &amp; Kusama treasury to cover maintenance, operations and human resource costs for Polkassembly, including general maintenance, runtime upgrades changes and could/infrastructure cost. We have transitioned to a half yearly method to improve on the scope of our deliverability and execute larger changes to our platform. This submission covers costs for Q3 &amp; Q4 of 2023. The maintenance proposal alternates between Polkadot &amp; Kusama treasury and we are requesting the Polkadot treasury to provide funds. This recurring proposal aims to secure the continuous operation and sustainability of Polkassembly, a vital component of Polkadot and Kusama governance. To ensure the smooth functioning of Polkassembly, we request a payments to cover essential expenses such as maintenance, operations, and human resources. The funds are allocated towards general maintenance, runtime upgrades, and infrastructure costs, guaranteeing the reliability and efficiency of Polkassembly. Attached below are key highlights of our proposal: 
Voting &amp; Transparency Upgrades:
<ul>
<li>Voting Details on Referendum (Live): Enhance the proposal page to show users' self vs. delegation vote split, detailed breakdown of delegators, and more.</li>
<li>Vote History in Profile (Live): Display voting history in user profiles, including self vs. delegated votes.</li>
<li>Reason for Voting (Live): Enable users to add voting reasons immediately after casting their votes.</li>
<li>Vote Anonymously: Allow users to hide their identity while voting.</li>
<li>Share reason for voting: Enable users to share voting reasons on social media.</li>
<li>Unlocking token locks: Simplify unlocking locked tokens.</li>
</ul>
New Features:
<ul>
<li>AI Summary (Live): Provide a quick summary of proposals.</li>
<li>Tooltip &amp; Tipping: Allow users to tip others and view tipping history.</li>
<li>Statistics: Display on-chain balances and user activity details.</li>
<li>Microfeatures: Enhancements to existing features.</li>
<li>Markdown &lt;&gt; Rich Text Editor Support: Toggle between markdown and rich text editors.</li>
<li>See more proposals: Recommend and display related proposals on detail pages.</li>
</ul>
Partnerships:
<ul>
<li>Moderation (Live): Enable Polkadot &amp; Kusama forum moderators to moderate on Polkassembly.</li>
<li>Polkasafe Integration: Utilize multisigs and proxies for governance interactions.</li>
</ul>
Maintenance &amp; Site-wide Migrations:
<ul>
<li>Husky Setup: Implement Git pre-commit hooks for code quality.</li>
<li>Redux setup &amp; remove contexts: Optimize state management for performance and debugging.</li>
<li>Remove Styled Components; implemented CSS modules: Refactor components to improve performance and eliminate hydration errors.</li>
</ul>
Additional Upgrades:
<ul>
<li>Optimistic Updates: Improve user experience and speed for actions like reactions and comments.</li>
<li>V2 DS &amp; Routed APIs: Simplify and optimize APIs.</li>
<li>Timeline UI upgrade: Enhance the timeline for on/off-chain events and proposal progress.</li>
<li>Navigation bar: Improve visibility and accessibility.</li>
<li>Open any profile: Allow viewing of any on-chain account.</li>
<li>JSDoc: Provide documentation for functions to facilitate open-source contributions and development.</li>
</ul>
These upgrades aim to enhance user engagement, transparency, and the overall experience on Polkassembly while streamlining development and maintenance processes. Please <a href="https://docs.google.com/document/d/1tFFRSIvtsa0fuzpzeESyrippWT3emkjIkiVAUMnh2kU/edit?usp=sharing">click here</a> to view the full proposal.

Polkassembly Social Contract | Maintenance proposal Q3 & Q4’23

Polkassembly is an integral part of Polkadot and Kusama governance. We have been actively working on making the smoothest governance experience at Polkassembly for OpenGov
In our endeavor to do so, we completed our first milestone with the theme of migrating and adapting Polkassembly to all OpenGov related changes and successfully delivered on the same by Feb end.
The theme of the previous proposal was Technical &amp; Product Based Migration, Education regarding OpenGov &amp; Creation of an appropriate user experience for the large transition governance went through.
The upcoming milestone aims to build Delegation as a simple, intuitive and exciting experience. We have developed our dashboard, with a user first mindset aimed at promoting agile governance. The core goal is to be ecosystem thought leaders and innovators, working with other teams including Nova. We will bring forth a list of delegation candidates, along with their voting experience and activity statistics, in order to enable maximum adoption of delegation.
Details of milestone 1 updates can be found <a href="https://docs.google.com/document/d/14hg1lAfeAgrR4YimqxPp-6XGW3gsvGzYAQnowpNGxoE/edit?usp=sharing">here</a>.
New Product Development &amp; Milestone 2
<h2 id="themedelegation">Theme: Delegation</h2>
<h4 id="featureuserdashboardlivehttpskusamapolkassemblyiodelegation">Feature: <a href="https://kusama.polkassembly.io/delegation">User Dashboard(Live)</a></h4>
Goal: To allow users to access their wallet level delegation and profile details
Tasks:
<ul>
<li>
A Web3 wallet based personalized login experience which is linked to your Polkassembly login experience
</li>
<li>
Users can edit their bio to allow more users to delegate
</li>
<li>
The dashboards shows User&rsquo;s current available, locked and transferable balance
</li>
<li>
Their profile details (sourced and linked to the Polkassembly or on chain profile)
</li>
<li>
Tracks for which they have delegated, not yet delegated or received delegations
</li>
<li>
A quick overview of track level information
</li>
</ul>
<h4 id="featuredelegationexperiencelivehttpskusamapolkassemblyiodelegationroot">Feature: <a href="https://kusama.polkassembly.io/delegation/root">Delegation experience (Live)</a></h4>
Goal: To allow users to delegate with ease and in an informed manner
Tasks:
<ul>
<li>
Users can select a particular track they want to delegate for
</li>
<li>
Based on the track selected, users will be able to see the list of available delegates
</li>
<li>
They can make a decision based on bio of the delegate, delegations they have received, proposals they have voted upon and total voting power
</li>
<li>
In addition to choosing delegates, Users can see active proposals on the track
</li>
<li>
If they have delegated, they can also see if the delegated user has casted a vote yet or not
</li>
</ul>
<h4 id="featureexpandingavailabledelegateslistinprogress">Feature: Expanding available Delegates List (In Progress)</h4>
Goal: To allow users to have a wider variety of choice while delegating
Tasks:
<ul>
<li>
Tie up with those working on delegations across the industry to bring more candidates forward
</li>
<li>
Create a native interface for users to submit themselves as delegates across tracks
</li>
<li>
Work closely with ecosystem partners like Nova to develop an ecosystem wide product to accept nominations for delegation
</li>
<li>
Importing the list of delegates available on the official polkadot delegation website
</li>
</ul>
<h2 id="themeplatformgrowthdevelopment">Theme: Platform Growth &amp; Development</h2>
<h4 id="featureregistrarapplicationdesigndone">Feature: Registrar Application Design (Done)</h4>
Goal: To allow users to have a supercharged and easy to use on chain verification experience
Tasks:
<ul>
<li>Outlined in the following discussion posts</li>
<li>Kusama - <a href="https://kusama.polkassembly.io/post/2585">https://kusama.polkassembly.io/post/2585</a></li>
<li>Polkadot - <a href="../post/1815">https://polkadot.polkassembly.io/post/1815</a></li>
<li>The development for the same will be charged in our maintenance proposal as it is a larger public good effort</li>
</ul>
<h4 id="featureopengovproposalcreationinprogress">Feature: OpenGov Proposal Creation (In Progress)</h4>
Goal: To allow users to create OpenGov proposals via Polkassembly
Tasks:
<ul>
<li>
Creating proposals via PolkadotJs apps could be overwhelming for users and has scope for lot of errors
</li>
<li>
Polkassembly will simplify this experience and make proposal creation simpler by linking the steps of preimage and proposal creation
</li>
<li>
The Phase1 of this process is to enable the proposal and preimage creation process from within Polkassembly for treasury proposal. Phase2 will be creation of all proposals which will be a part of the later proposals.
</li>
</ul>
Goal: Proposal creation from Polkassembly (Process)
Tasks:
<ul>
<li>
Users will be nudged to create a discussion post regarding their proposal
</li>
<li>
After this, the preimage creation process will start. Leveraging the amount of the proposal, beneficiary and creator address, Polkassembly will recommend the track for creation of the proposal
</li>
<li>
The preimage will be automatically linked if the user proceeds to the proposal where they can pay the submission deposit and the proposal will be generated on chain. The off chain description will be populated based on whether the discussion is linked or not.
</li>
<li>
The users can then pay the decision deposit at any point of time during the voting phase
</li>
</ul>
<h2 id="themeaccessibilityexperience">Theme: Accessibility &amp; Experience</h2>
<h4 id="featureproposallistingviewchangesinprogress">Feature: Proposal Listing view changes (In Progress)</h4>
Goal: To allow users to have a seamless UI while accessing proposal
Tasks:
<ul>
<li>
A new and upgraded listing view which enables a better platform experience
</li>
<li>
Treasury amounts shown upfront for all treasury related proposals
</li>
<li>
Tags for Gov1 &amp; OpenGov Proposals (Done)
</li>
<li>
Easy filtering of proposals into four parts - All Proposals, Submitted, Voting and Closed(Done)
</li>
</ul>
<h4 id="featuresearchinprogress">Feature: Search (In Progress)</h4>
Goal: To allow users to experience a top notch unified search experience
Tasks:
Search will be broken into two parts - Search - Chain level search
<ul>
<li>Super Search - Site wide search, a very powerful search across all Governance Proposals in Polkadot Ecosystem</li>
<li>Search Features:</li>
<li>Discussion and Off chain search</li>
<li>Users will have the option to search keywords in titles and description of proposals</li>
<li>Referendum Level and On chain search</li>
<li>Users will have the option to search keywords in titles and descriptions of discussions</li>
<li>User level search where users can search by keywords to receive on chain usernames and off chain usernames</li>
</ul>
<h2 id="themeuserinterfaceupgrades">Theme: User Interface Upgrades</h2>
<h4 id="featurenewaccountsettingspageinprogress">Feature: New account settings page (In Progress)</h4>
Goal: To enable easy interactions for various account settings
Tasks:
<ul>
<li>Easy interface for password, username or email change</li>
<li>Upgraded interface for linking addresses, multisig and proxies in Polkassembly.</li>
</ul>
<h4 id="featuredarkmodeinprogress">Feature: Dark mode (In Progress)</h4>
Goal: To allow users to set their user interface as per their preference
Tasks:
<ul>
<li>
Sitewide deployment of dark mode to support users who prefer leveraging a dark mode interface
</li>
<li>
Modifying all elements across flows including user profiles, on chain governance activity (Gov1 &amp; OpenGov), off chain activity, delegation and overview pages
</li>
<li>
Combining the effort of zooming out the interface to make a more comfortable default experience for users
</li>
</ul>
<h4 id="featurevotinginterfaceupgradeslive">Feature: Voting interface upgrades(Live)</h4>
Goal: To allow users to vote on proposals with more options and have a better voting experience
Tasks:
<ul>
<li>Clear indication of the last vote casted by the user on the UI</li>
<li>The ability to vote using split and abstain as options in OpenGov(Live)</li>
<li>A new and improved voting interface(Live)</li>
</ul>
<h2 id="themepolkadotopengovdeployment">Theme: Polkadot OpenGov Deployment</h2>
<h4 id="featuredeployingallcorefeaturesforopengovtopolkadotlive">Feature: Deploying all core features for OpenGov to Polkadot (Live)</h4>
Goal: To upgrade Polkassembly&rsquo;s Polkadot interface to OpenGov
Tasks:
<ul>
<li>The list of feature deployed for Polkadot are similar to Kusama as mentioned in the Kusama Proposal: <a href="https://docs.google.com/document/d/1vWOiKBG_lARiy0EXDATxvt0htJ_N_LmtOnzirutAvns/edit">OpenGov Treasury proposal</a>.</li>
<li>The remaining tech effort spent on the migration for Polkadot has been billed in this proposal</li>
<li>Marketing and promotional efforts including the setup of the OpenGov Proposal timer.</li>
<li>Announcement: <a href="https://twitter.com/polk_gov/status/1667146568258969601">https://twitter.com/polk_gov/status/1667146568258969601</a></li>
</ul>
<h4 id="featuredeployingdelegationdashboardforpolkadotlive">Feature: Deploying delegation dashboard for Polkadot (Live)</h4>
Goal: To allow users to vote on proposals with more options and have a better voting experience
Tasks:
Links for reference
<ul>
<li><a href="../delegation">Dashboard</a></li>
<li><a href="../delegation/root">Track Level Delegation experience</a></li>
</ul>
<h2 id="themesecurity">Theme: Security</h2>
<h4 id="feature2factorauthenticationlive">Feature: 2 Factor Authentication (Live)</h4>
Goal: To allow users to secure Polkassembly accounts
Tasks:
<ul>
<li>2FA authentication integration to provide seamless security upgrade</li>
<li>New API provided to all partners in the ecosystem to deliver a more robust and improved performance.</li>
<li>This also includes the process of migration of existing Polkassembly APIs to Opengov</li>
</ul>
Implementation Gallery
<img src="https://i.ibb.co/r45mWXH/2-premiurly-1687437748485.png" alt="image" />
The user dashboard interface for delegation dashboard
<img src="https://i.ibb.co/8Kqmy0Y/2-premiurly-1687437809680.png" alt="image" />
Track level delegation experience
<img src="https://i.ibb.co/y0jXgwh/2-premiurly-1687437843020.png" alt="image" />
Two Factor Authentication Setup
Other details about implementation, detailed cost calculations and milestone 3 are available in the detailed proposal <a href="https://docs.google.com/document/d/14hg1lAfeAgrR4YimqxPp-6XGW3gsvGzYAQnowpNGxoE/edit?usp=sharing">here</a>.

Polkassembly is an integral part of polkadot and kusama governance. This submission proposes a recurring payment (quarterly) to cover maintenance, operations and human resource costs for Polkassembly, including general maintenance, runtime upgrades changes and could/infrastructure cost. Since Polkassembly supports both Kusama and Polkadot Networks, this maintenance proposal will alternate networks for submission every three months. This submission covers costs for January, February, March of 2023. We are requesting the Polkadot treasury to provide funds this time.

The full proposal is available [here](https://docs.google.com/document/d/1q3Byq4BN-OJAA0l4v51H3ye71SiorweoYPabB-jF41I/edit#). 

Discussion is [here](https://polkadot.polkassembly.io/post/1641)...

Polkassembly is an integral part of polkadot and kusama governance. This submission proposes a recurring payment (quarterly) to cover maintenance, operations and human resource costs for Polkassembly, including general maintenance, runtime upgrades changes and could/infrastructure cost. 
Since Polkassembly supports both Kusama and Polkadot Networks, this maintenance proposal will alternate networks for submission every three months. This submission covers costs for October, November and December of 2022. We are requesting the Polkadot treasury to provide funds this time.

The proposal details the work done in past from our previous proposal and the things we plan to implement in this quarter. 

The full proposal is available [here](https://docs.google.com/document/d/1-cm0QQDljqIGu7tFXI3wQz8-PsrKXb6QN3lSMElV9lk/edit?usp=sharing).  Discussion can be found [here](https://polkadot.polkassembly.io/post/1377)

[Polkassembly](https://polkadot.polkassembly.io/) is an integral part of polkadot and kusama governance. This submission proposes a recurring payment (quarterly) to cover maintenance, operations and human resource costs for Polkassembly, including general maintenance, runtime upgrades changes and could/infrastructure cost. Since Polkassembly supports both Kusama and Polkadot Networks, this maintenance proposal will alternate networks for submission every three months. This submission covers costs for January, February, March of 2022. We are requesting the Polkadot treasury to provide funds this time.

The full proposal is available [here](https://docs.google.com/document/d/1hb3d_wItFmijFTG_hbQEtCoLaeiLfaNlc0iY5GCS-LQ/edit?usp=sharing). Disussion can be found [here](https://polkadot.polkassembly.io/post/803)

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