- Referenda/
- Big Spender/
- #483/
Referendum #483
Polkassembly Social Contract 2024
Executed
Content
AI Summary
Translations
Polkassembly is an integral part of Polkadot and Kusama governance.
This submission proposes an annual payment as part of our social contract with the Polkadot & Kusama treasury to cover maintenance, operations and human resource costs for Polkassembly, including general maintenance, runtime upgrades changes, new feature development and could/infrastructure cost.
Why has Polkassembly moved to an annual social contract?
Polkassembly is transitioning from a quarterly proposal model to an annual one to streamline our operations and enhance the value we deliver to the Polkadot community. This strategic shift is driven by several key factors:
1. Sustained Support and Development:
Moving to an annual proposal model allows us to secure more stable and long-term support for our team. This stability is crucial for maintaining a dedicated group of developers and contributors who can focus on continuous development without the interruptions that come with frequent funding cycles.
2. Enhanced Focus on Quality and Innovation:
With a yearly cycle, our team can dedicate more time to developing high-quality features and undertaking innovative experiments that require longer gestation periods. Planned pipelines and milestones with research will help deliver high quality features beyond the quarterly milestones
3. Comprehensive Reporting and Transparency:
Annual proposals enable us to provide more detailed and impactful reports on our progress and achievements. These comprehensive reports will offer clear insights into our contributions, backed by proof of work statistics, showcasing our commitment and the tangible benefits we bring to the ecosystem.
All these metrics are attached below in the Product Statistics and social statistics where our contribution and its significance can be seen
4. Strategic Marketing and Community Engagement:
A yearly cycle affords us the opportunity to plan and execute more strategic marketing initiatives. By aligning our marketing efforts with our development milestones, we can ensure that our achievements are effectively communicated and a long term strategy to promote OpenGov and its novel developments can be highlighted within and outside the community.
5. Maximizing Common Good and Addressing Opportunity Costs:
This model allows us to align our resources more closely with the common good of the Polkadot ecosystem. By considering the opportunity costs, we can prioritize projects and features that offer the highest value and impact, ensuring that our contributions are both meaningful and timely.
So essentially, transitioning to an annual proposal model reflects our commitment to continuous contribution, high-quality development, and strategic growth. With 95%+ of our milestones already achieved in the past year and over 50 new features rolled out, we are confident that this new approach will enable us to serve the Polkadot community even more effectively.
Our story is one of unwavering commitment and proven results, and we are excited to embark on this next phase of our journey with the support of the community.
So what are we upto in 2024?
| Theme | Feature | Goal | Tasks |
| Analytics | |||
| Analytics | Referendum Level Analytics | To provide detailed understanding of statistics on a referendum level | 1. Break down metrics into three types - DOT used for voting, number of voters participating and the DOT used with conviction during the vote for each referendum 2. Summarize with key metrics including Total Amounts for Delegation vs Solo Split, Aye vs Nay vs Abstain split and the Turnout. - All the above metrics can be seen as per the three metrics filters the three types of metrics filters mentioned in point 1 3. Show the time period distribution of the votes / voting power / voting power with conviction 4. Show conviction distribution for Delegated vs Solo & Aye / Nay / Abstain votes 5. Allow all the charts to be interactive and easily navigable from the referendum page directly. These will also be shown as navigable from within the Analytics Tab 6. The referendum level analytics will also highlight data regarding top whales, their percent contribution in a distributed graph |
| Track Level Analytics | To provide detailed understanding of statistics on a track level | 1. Break down metrics into three types - DOT used for voting, number of voters participating and the DOT used with conviction during the vote for each of the tracks 2. Aggregate key metrics including Total Amounts for Delegation vs Solo Split, Aye vs Nay vs Abstain split and the Turnout. - All the above metrics can be seen as per the three types of metrics filters mentioned in point 1 3. Allow all the charts to be interactive and easily navigable from the track page directly. These will also be shown as navigable from within the Analytics Tab. 4. An easy to use UX will allow comparison between different number of referendum to allow easy benchmarking 5. The track level analytics will also show delegation data of # of delegates, top delegates, their received delegations and total voting power as well as their participation status and contrarian index in general |
|
| Governance Level Analytics | To provide detailed understanding of statistics across governance | 1. A separate tab will house overall governance level analytics - This will also provide the option to navigate to track and referendum level details 2. Critical stats like Amount of DOT locked in governance, # of active referenda etc will be available here 3. Navigate across referenda in a track and category agnostic manner 4. Use tags, dates, amounts, and different filters to analyze governance as per user preference 5. See overall metrics like support, issuance, Delegation vs Solo Split, Aye vs Nay vs Abstain split and the Turnout across all referendum |
|
| New Features | |||
| Reports and Accountability | Deadline | To provide an understanding of when a proposal will be delivered by | 1. Community will have clear understanding of the final deadline of the proposal 2. There will be an option to add milestones for each referendum as well with independent deadlines |
| Progress Reports (Potentially in collaboration with Subsquare) |
To provide the community with an update on what was delivered and when / with what impact? | 1. Proposers will be nudged to add progress reports when the deadlines nears 2. Each milestone will have a separate progress report to track if the proposal has been submitted as per requirements 3. The progress reports will be shown the user’s profile along with other details - These reports will be shareable to X or on social handles - Users will be able to export these reports 4. Community can rate or comment on these progress reports which will enforce accountability |
|
| Evaluation tab | To ensure each proposal is thoroughly vetted on the idea and the proposer’s merits | 1. The evaluation tab will have multiple sections including - Proposer deepdive, beneficiary deepdive, Audits and the Progress Reports 2. Proposer and beneficiary deepdive will explain whether wallets are multisig or not, have been verified or not, their date of inception, as well as their average rating on past proposals and progress reports |
|
| Expert Body | Proposal Expert Review | To enable expert reviews on proposal page and highlight these in the interface | 1. Allow experts to submit reports on a proposal on Polkassembly along with an AI generated or manually added summary of the report - The export review will be highlighted like the AI summary for users to quickly browse through the entire report or just the summary of the report 2. Allow users to interact and comment on expert reports, as well as upvote or downvote them. - There can be questions or statements regarding the expert’s views on the topic at hand - These will be linked to the main discussion view as well 3. Highlight these expert reviews on description page and integrate these with alerts, on chain notifications 4. Enable users to engage with these expert reports, tip them if need be or allow the treasury tip worthy reviews to be highlighted in case of multiple reviews 5. Complete details can be found in the work doc - Link |
| Proxy Addresses | Create Proxy Addresses | To enable users to create proxies directly in Polkassembly | 1. Allow users to create - governance, non-transfer, staking, identity, cancel, auction and nomination proxies directly from Polkassembly 2. Allow users to identify addresses where proxies are present and select from multiple proxies injected based on login wallet / selected wallet 3. Linking of proxy wallet to profile to populate activity, balance, and delegation details 4. Allow users to unlink their proxy account and free up their locked balance from Polkassembly |
| Delegation | |||
| Overview Page | Trending delegates | To ensure users can participate in quick delegation via Polkassembly | 1. We highlight the top and most frequently delegated users with their voting details on the central ui of the profile 2. Allow users to directly delegate from this UX to increase quick delegations for uninitiated users |
| How to delegate | A quick two step guide to enable smooth delegations | Give users the options to either: - Select a track to delegate and then delegate their votes or - Select one of the top delegates and then choose relevant tracks to assign delegation |
|
| Become a delegate on Polkassembly | To allow users to highlight themselves as potential delegation candidates on Polkassembly | 1. Users can add their bio, socials and make a profile if they have not done so or link their original profile if it is already created to become a delegate 2. Delegates on Polkassembly will receive a special badge which indicates their reputation as a delegate everywhere on the platform |
|
| Data points for delegators | Statistics | To ensure users can track how the ecosystem’s current delegation status looks like | 1. We highlight the top metrics including - total supply, delegated tokens, total delegated votes, total delegators and total number of delegators being tracked on the platform |
| Badges | To highlight participants with exceptional contributions | 1. Delegates who have differentiable activities will be given badges on the platform i. Maximum participation ii. Highest number of delegators iii. Highest amount of delegated DOT/KSM iv. Experts in domains / active commenters |
|
| Unlock Delegations | To allow users to understand in how much time they would be able to unlock their delegate votes | To show delegators time to unlock their votes - with details around history of conviction, voting power on track level | |
| Delegate engagement | Delegation Mandate | To allow users to independently edit delegation mandate | 1. User will have a separate bio describing how they make their voting judgements, their general delegation mandate and why they should receive additional delegations 2. Their delegation mandate will be link to the profile and will be editable from the dashboard 3. Users will be nudges to verify their addresses before becoming delegates |
| Chat with delegates | A quick way to interact with delegates | 1. Discuss the reason for voting, mandate for voting, and many more details with a user by chatting with them via the delegation dashboard | |
| Fellowship (Milestone 2) | |||
| New Features | Calendar | To show important events in the fellowship as well as expected timelines | 1. Important on chain events, execution dates and offchain events like Polkadot Blockchain Academy will be tracked here 2. Fellowship Member inductions and anniversaries will be trackable from these events |
| Micro-features | A set of mini improvements to the currently live collectives platform | 1. Addition of multiple RPC endpoints to ensure a smoother experience in different geographies 2. Dark mode customization and improvements to ensure standardization in the product 3. Tooltips and tipping for fellowship platform to allow users to quick view fellows instead of directly going to their profile 4. Trending Proposals on fellowship and their status to allow quick access to these proposals and voting on them 5. Empty States across platform and loaders to ensure a smooth experience especially in case of heavier on chain calls or images 6. Nudges for new fellows and existing ones regarding on chain activity to ensure that there is a smoother onboarding to best practices of the platform 7. All Fellowship Meeting recordings redirection and calendar events for new fellows to ensure they can access past information. — Preimage tab to find, navigate to, execute and unnote preimages allowing the execution of all detailed steps directly from the fellowship platform. — An independent pending tab for a user to show them activity that is dependent or pending on them only - making for an engaging social feed. — Allow mentioning other users and notifications for mentions in fellowship |
|
| Westend | Quick deployment and testing of features on Fellowship | 1. Westend platform deployed with equivalent functionality to the Polkadot Fellowship for fellows and non fellows to explore the product | |
| Fellow Experience | Personalization | To make the fellowship product more customized as per needs of fellows | 1. Notifications for Fellows - For all kinds of activity that they would like to follow and keep track of as per their preference on various channels including telegram, discord, mail and eventually element and slack 2. Following Fellows and receiving updates regarding them in the activity feed - Optional view for seeing votes and activity by only these fellows 3. Allowing for searches based on fellowship activities, members names and more |
| Fellowship Statistics | To show important statistics for fellows | 1. Detailed statistics for salary pallets - Total salary drawn, salary available in a cycle 2. Number of members inducted, requests created, referendum created, voting analysis on each of the referendum and more |
|
| Mobile view | Mobile experience | To allow members to access the fellowship platform on their mobiles for engaging and quick actions | 1. Each of the features available on the web view would be made available in the fellowship’s mobile version - Overview Pages - Membership Page - Proposal Pages - User profile 2. Allow users to take all offchain actions directly from the mobile view - Edit social handles - Edit About - Link Github - Add comments, reactions - Navigate through timeline |
| Integration with Github | RFC proposals | Enable ease of engagement with RFC proposals | 1. AI Summary for PRs, RFC and issues in activity to allow members to read through the details 2. Convert RFC PR to Proposal on activity tab |
| Github Integration | To allow a deepdive into contributions made by fellows as well as highlighting top fellows | 1. To import the activity done on fellowship repository and show it along with summary statistics in the fellowship platform 2. To show the top fellows in a given time period and contributions made by them 3. To have stats regarding contributions by fellows 4. Integration with Github verification identity for DOT when it goes live |
|
| Product Partnerships | |||
| Prediction markets | Zeitgeist Integration(Live) | To boost community engagement participation in Governance | 1. Twitter announcement¨ 2. Few markets around governance - Ref #303, Ref #307, Ref #350¨ 3. These markets were live on Polkassembly to drive dApp adoption as well as on Zeitgeist 4. Media coverage - Captain Altcoin, Finance Feeds, CoinGape 5. Show the interface on Polkassembly with current market prediction data from Zeitgeist, number of participants and deep linking to the ZTG market on Zeitgeist |
| To choose and create new markets via Zeitgeist & deep integration of prediction markets | 1. Polkassembly takes the responsibility of identifying new markets and ensuring that the most exciting markets are used for predictions 2. Moving towards a deeper integration of prediction markets by showing a more detailed view of predictions |
||
| Subsocial | Deeper integration with subsocial | To enable more cross platform features/data feed from subsocial | 1. Fetch relevant posts from subsocial and show with relevant proposals 2. Deeper integrate subsocial-chat with Polkassembly |
| Points & Leaderboard | |||
| Points System | Leaderboard Formulation | To enable a gamified understanding of a users contribution to governance via a single metric | 1. The first version of proposed scoring system indicates the distribution of points for various off chain and on chain activities done via Polkassembly 2. Please refer to this link for detailed understanding of how it works- It includes positive points for actions which improve governance dialogue and evaluate - Negative points for actions which are detrimental to collaboration and discussions 3. The leaderboard will have various filters including all time, weekly and monthly to ensure governance participants in different time frames are highlighted. |
| Score breakdown for each user | To enable each user to understand how their score is calculated | 1. This will be available at multiple touchpoints including the profile, quick view tooltip and in the leaderboard 2. Opening this would explain the exact distribution of points credited to a user 3. The score will be evolved over a period of time based on the inputs from various community members 4. Each existing and new activity on Polkassembly will lead to points being rewarded to users |
|
| Social | |||
| On Product Notifications | Single notification hub inside Polkassembly | To enable users to access notifications in a central system | 1. Polkassembly presently allows users to configure what kind of notifications they would like to receive off chain on mail, telegram and discord 2. We will enable users to receive all existing notification and more updates on chain, in a simple consumable interface where notifications can be marked as red / unread increasing the overall engagement on the platform as well as making it easier for users to reply to mentions and comments on their discussions 3. The feature will include microfeatures - to open notifications in a full page view, mark all notifications as read, and cluster notifications together |
| Mentions | In proposals, comments and replies | To enable users to mention users across the site | 1. Users will be able to tag any user by simply typing @ & their username - A preview will show recommended users to ensure users do not need to know the exact username - This mentions will be visible on the users profile and will be deeplinked to their on product notifications 2. Based on the configuration of the users alerts - they will also receive these on channels including telegram, discord, mail and eventually element & slack |
| Follow | Profile based following | To enable users to follow each other’s governance activity on Polkassembly | 1. Presently we allow following posts and receiving notifications for updates on them 2. We will enable users to follow each other and whale accounts setting precedent for the platform to become extremely social. - Notifications can be received on product or off product for these follower activities 3. The count for followers and following will be available on the profile 4. Users will also be able to see details of who a user follows or is being followed by |
| Timeline (Activity feed) |
Social Timeline as platform default view | To build an engaging social experience within Polkassembly | 1. Independently show users the activity which they have participated in and whatever is pending on them to participate in - especially in case of referenda 2. Show activity about users they follow in the feed¨C156C- The can choose to receive updates about votes, comments, likes, dislikes, discussions or proposals 3. Allow users to directly like, dislike, comment, reply or even vote from the feed 4. Show non governance activity in the ecosystem (events, etc. from calendar & news), directly on Polkassembly to bring more visibility to them 5. Integrate microfeatures which make the social feed more engaging and collaborate with industry partners to make this representative of activities in the entire Polkadot Community |
| Share vote on Social Media & Social NFTS | Enable NFTs for voting which are shareable | To build an experience around sharing of vote based NFTs on social media | 1. Design multiple kinds of aye, nay, split, abstain NFTs 2. Ensure each referendum vote can be stored as a separate NFT and is shareable on X or other social channels 3. Tie these NFTs with the person’s reputation. Calculate a contrarian index to evaluate how many votes were casted in negation |
| Profile NFT Integration | Enable integration of NFTs in governance profiles | To build a holistic reputation for individuals on Polkassembly | 1. POAPs, Social NFTs, Soul bound NFTs, gaming and other such NFTs will be imported into each user’s profile - Polkassembly will run a social campaign to promote this multiple ecosystem partners 2. Users would be able to identify and connect / follow users with similar POAPs of NFTs via a common listing page where the holders of each NFT will be listed - These listing pages would be linked to the NFT marketplace of other platforms and would indicate stats like # of total holders, floor price, etc |
| Badges | Gamification of user profile | To build tags which can help identify a user and understand their voting patterns | 1. Delegate, fellows, delegators will have custom badges which help identify their profiles in forum based discussions easily 2. Voters with high contrarian index, always nayers (bot voting), highest dot, high and low conviction voters could have interesting badges which gamify the experience 3. These badges will be open sourced for allowing the community to easily access them 4. Users would be able to identify and connect / follow users with similar badges via a common listing page where the holders of each NFT will be listed - These listing pages would indicate stats like # of total holders, when is the badge issued and more |
| Bounty Product (V1) | |||
| Use Cases | Social Bounties | To allow members to post collaborative bounties for community to solve in Polkadot community The product will enable the community to leverage their social network for ad hoc tasks, introductions reviews and much more |
Polkadot ecosystem presently only allows funding of bounties via the treasury. Polkassembly intends to create a social bounty product which will - 1. Allow community members to tweet for a bounty or create it directly on the platform - If tweeted, a twitter bot responds and continues to engage with the tweet ensuring that the bounty is created and there is public attention to it 2. Allow deep linking of bounties from social handles like X, & potentially social platforms like me.we & Polkaverse in the DOT ecosystem - Each user has a unique profile which is either created by signing up on the platform or auto-generated when they tag and post bounties. A unique user id is assigned to track activity and introduce social accountability on bounty payouts 3. Nudges to fund the bounty in advance - This is done by either allowing a single funder or the community to fund a public bounty 4. Initially follow a centralized approach to bounty approval - where the creator decides the best bounty 5. Eventually make the process of optionally funding bounties in a decentralized manner as well 6. Enable social engagement like upvotes, downvotes, comments and replies on the platform |
| Product Features | All Bounty Timeline | To allow users to see all published bounties and their status | 1. The list of bounties shows details including the funder, the time of creation, user profile, comments, reactions 2. The status of a bounty helps a user understand if the bounty is still accepting submissions or if it has been closed |
| Profile Page | To allow users to maintain their profile and reputations | 1. Profile level details include - Username, profile picture, total amount of bounties created, total amount of bounties funded, bounties earned, number of bounties created 2. Listing view of submissions, bounties created and submitted |
|
| Bounty Dashboard | Custom Bounty Interface | To boost the adoption and visibility for bounties in the ecosystem | 1. Highlight all open, closed and in voting bounties in a separate interface 2. Show breakdown of amounts, details of progress and potential targets for each bounty 3. A working doc for the bounty product can be found attached here — Link 4. Dashboard i. Top Level statistics on Available Bounties, Total Amount in DOT & USD, other relevant statistics ii. Bounty Cards highlighting different bounties, their status, Category, tags, amounts, no. of sub-bounties, etc. iii. Details about Polkadot bounty - educational material and video tutorials on creating bounty proposals via Polkassembly iv. Create bounty button 5. Bounty Detail page i. How to make a submission for that bounty ii. Portal to make submission for the bounty iii Tracking status of the bounty submission iv Read, review comments and update bounty submission if required Parent Bounty proposal details and discussions(comments + voting details) For curators i. Being able to view and track all active submissions ii. Manage active submissions and leave comments or communicate with bounty submitters iii. Initiate payout for sub-bounty iv. Update status for bounty v. Cancel bounty Profiles i. Number of sub-bounties created ii. Tracks/categories in which bounties were claimed iii. Total amount earned from sub-bounties, etc. |
| Maintenance - Features | |||
| Creating proposals on Polkassembly | Proposal creation for all tracks | To all the creation of different tracks of proposals on Polkassembly | 1. Currently users can use Polkassembly’s powerful interface only to create proposals in the treasury tracks 2. Users will be allowed to create proposals to kill any referendum - which would slash the decision deposit 3. Users will be allowed to cancel any referendum which will cancel the proposal and return the deposit 4. Users will also be allowed to create any kind of referendum - This would include a form which allows selection of multiple parameters to create a preimage - This preimage will be linked to the preimages tab of Polkassembly - After this a one click, seamless proposal ensures that the proposal is created on Polkassembly in a continuous manner with the descriptions as a part of the proposal - The user will also be provided the option to pay the decision deposit immediately after creation of the proposal 5. Relevant nudges on Overview page, track level pages and in FAB to allow creation of referendum from different touchpoints |
| Multiple beneficiaries on treasury proposals (Live) |
To allow users to show multiple on chain beneficiaries and request for funding in a transparent manner | 1. Based on community requests we developed and delivered a feature to easily add multiple beneficiaries while creating a proposal - a process which is very difficult on PolkadotJS 2. Each address can be added independently and the relevant amount for each address can be indicated next to it 3. There are also relevant nudges to indicate if an identity is verified or not and if the address is a multisig or not in the AI summary as well as during proposal creation process |
|
| Profile | Interface upgrades(Live) | To bring all governance statistics in a single comprehensive profile | 1. UI revamp - For votes casted, proposals created, discussions created, linking addresses, multisigs and proxies 2. Allow editing of social handles, profile pictures, cover image, user name 3. Allow actions like tipping, delegation, unlocking votes, unlocking proposal deposits directly on profile |
| Delegation integration(Live) | To integrate delegation dashboard with profile of user | 1. Show a detailed view of number of delegation received and delegations given - Allow users to view/add delegation mandate on profile - Show number of delegation received across tracks. Each user's voting power and address are shown. Details show the number of tracks on which votes have been delegated as well as amount and conviction delegated on each track - Show number of delegation given with the same details mentioned above - Allow selection of address from multiple addresses linked to profile |
|
| Detailed balance information | To show breakdown of users token balance | 1. Show user’s total token balance split across locked balance and transferable balance 2. To show user’s total voting power split across self voting and delegations 3. To show user’s vote balance locked in staking 4. Allow users to select between different addresses that are linked to a profile and show aggregate of statistics which have been mentioned above |
|
| Comments, reactions and mentions | To show users’ off chain engagement history | 1. To show comments and replies by a user. 2. To show mentions of a user 3. To show reactions of a user 4. To show timestamps as well as engagement details of other users on the above mentioned activites |
|
| Maintenance - Technical | |||
| Technical Integrations | Subsquid migration(Live) | To enable seamless transition to latest technical infrastructure offered by Subsquid | 1. Migration to the arrow squid offered by Subsquid for Polkadot & Kusama along with sdk integration changes |
| Site wide analytics | Implementing instrumentation to ensure site wide tracking and reporting of statistics in proposals | 1. All twitter posts made for engagement including # of views, # of proposals created, etc. have been done by leveraging the instrumentation implemented across the site 2. The instrumentation has been split into three phases, with only phase 1 live currently | |
| Development & Open Source Standardization | Design system integration | To ensure a seamless user experience (consistency in components) and fast development | 1. After completing the migration to NextJS the product speed, responsiveness and overall performance have been significantly improved 2. Design systems set up for components i. Buttons - - Primary button - Secondary button - Default button - Disabled button - Icon button ii. Forms - Input fields - Textareas - Select dropdowns - Checkboxes and radio buttons - Switches and toggles iii. Typography: - Heading styles (h1 to h6) - Paragraph text - Bold and italic styles - Lists (unordered and ordered) - Blockquotesiv.Navigation - Navbar - Sidebar - Breadcrumbs - Paginationv. Cards - Basic card - Image card - Actionable card vi. Modals and Popovers: - Modal dialog - Popover and tooltipsvii. Icons: - Use a library of scalable vector icons.viii. Alerts and Notifications: - Success alert - Error alert - Warning alert - Info alert ix. Loading Indicators: - Spinner/loader x. . Tabs and Accordion: - Tabbed navigation - Accordion for collapsible content xi. Progress Bars: - Linear progress bar - Circular progress bar xii. Tables: - Basic table - Data tables with sorting and filtering xiii. Badges and Tags: - Status badges - Tag labels xiv. Utilities: - Spacing and layout utilities (e.g., margin, padding, flexbox) - Color palette and theming |
| Automated Testing | To ensure continuous testing for smoother product evolution | 1. Leverage selenium to build an automation testing pipeline for all off chain features including - login, discussion, comments, replies, reactions, page views | |
| Site Experience Improvemenet | JWT Issue fixes(Live) | To ensure smooth auto logout experience for users | 1. Maintain JWT sessions between old architecture and new next JS architecture 2. Auto logout for users, helping prevent errors due to JWT timeout. |
| Cache control | To ensure smooth cache control in nextJS and cloudflare | 1. Enable caching in Cloudflare for all resources possible to reduce hosting costs and reduce load on the server, increasing server reliability. | |
| Package size(Live) | To improve load time on the platform | 1. Replace SVG files with links to reduce the package size from 3.41 mb to 2 mb and ensure image component creation to continue sustainable development by replacing 20+ files | |
| Refactoring (Live) | To improve delegation dashboard speed and experience | 1. Improve api response time and removed redundancies 2. Improved undelegation or delegation response time to 2 / 3s and optimize on chain calls |
|
| Improve Vote detail info | To allow users to see all vote details in a consumable view | 1. Allow users to see vote time, % of voting power even for non delegated votes | |
| Maintenance - Microfeatures | |||
| Description API | OpenAI API(Live) | To allow users to access Polkassembly’s AI Summary | The AI Summary API has two options 1. The format available on Polkassembly 2. A 250 character AI summary for teams looking to show a shorter summary |
| Referendum Page Mircofeatures | Quote / Share Comments | To allow users to quote a portion of a proposal, comment or reply | 1. Users will be able to see quoted replies, comments or proposals 2. These will also be shareable directly to social media |
| Status level filters(Live) | To allow users to filter proposal based on status | 1. Filtering on tags is already live 2. FIltering on statuses including timed out, confirmation, etc. to allow a deepdive into various aspects of governance 3. Creation of the all tab and allowing filtering via tracks or topics on it |
|
| Bounties | To show detailed breakdown of a newly proposed bounty or child bounty | 1. Currently visibility into the details of a bounty are very less. The feature will show % of bounty that has already been claimed, % requested and how much will remain after bounty approval - The detail will be available on the proposal detail page as well as the listing view | |
| RHS Cards with scroll on proposal page(Live) | To allow users to take contextual actions directly from the page | 1. Pay the decision deposit to ensure the proposal enters in to the voting period 2. Add a description to ensure that the community has complete details about the referendum 3. Add a deadline date for your proposed proposal so that the community has visibility about the delivery date 4. Link the referendum to an existing discussion post to import comments and description from the post 5. Show time to confirm or time to fail for a proposal on the RHS directly |
|
| Feature Scope Improvement | Verify identities on Kusama | Deploying the feature to set and verify identities on Kusama with ease | 1. Similar to Polkadot, users will be able to follow a simple two step process to set and verify their identity directly on Polkassembly |
| Reply to Subsquare Comments on Polkassembly | To enable proposers and users to complete entire conversations on Polkassembly | 1. Most users struggle with replying to comments from subsquare even though they occupy <2% of comments in the governance of Polkadot & Kusama historically. 2. We will allow users to reply to comments on Polkassembly and based on further progress they should be able to interact freely on the with the replies / comments & like / dislike / report them |
|
| New alerts for users | To allow an even larger and comprehensive set of alerts for users to configure | 1. Alerts for receiving a delegation or undelegation on chain 2. Alerts for a proposal entering into a confirmation state or leaving from it - Multiple more to be added |
|
| Mobile view improvements | To build a better mobile experience for Polkassembly | 1. Improve vote details screen on mobile - for seeing details of a vote and distribution between delegated & solo votes on mobile 2. Improved ux of proposal detail page 3. Custom overview page for mobile view to make better experience 4. Referendum page - splitting of boxes and smoother scrolling experience in mobile view |
|
| New Mircrofeatures | Show votes on listing view | To allow users to identify which proposal they have voted for directly from the listing view | 1. Users can directly see their vote type - aye, nay, abstain or split and the amount as well as conviction directly from the listing view of all / track specific pages |
| Compulsory username setup (Live) | To ensure users find a consistent experience in the platform | 1. Polkassembly earlier saw a lot of usernames not being set and hence wallet address being used as usernames 2. Now, every new users must set their username on login and can optionally set their email address to receive alerts |
|
| Cancel Preimage | To allow users to cancel erroneous preimages and receive their deposit back | 1. The option to cancel a preimage is provided on two touchpoints i. The preimage tab where different preimages created by the proposer can be canceled ii. The proposer tab(Live) 2. If a preimage has been canceled, the status should show on the referendum page as well |
|
| Proposal tagging | To enable retroactive tracking of proposal types, spends and more directly on Polkassembly | 1. Using publicly created tags and breakdown of proposals into different categories to retroactively tag proposals 2. Continue building towards the effort of treasury analytics directly on Polkassembly |
|
| Data Decentralization | Decentralizing proposal data(Potentially in collaboration with Subsquare) | Data Decentralization is an important step in progressing Polkassembly and OpenGov to decentralization | 1. Decentralizing the following data sources - discussions - comment, reply data - proposal description data - Profile bio & off chain social handles - Delegation bio - Profile Image & Cover image of a user - Off chain voting signals This will ensure the compliant storage of data as well as true decentralization for the project 2. Migrate previous data to IPFS 3. Add middleware to ensure new data moves to IPFS. Ensure collaboration with teams building in the ecosystem to subsidize costs |
| Landing page | Polkassembly landing page revamp | To ensure a better onboarding for users and provide them with more information about OpenGov and its capabilities when they land on polkassembly.io | 1. Polkassembly attracts the largest number of users to governance in the DOT ecosystem. 2. The website brandings should indicate and explain different governance mechanisms and how partners building on Polkadot can leverage the pallets as per their team’s stage 3. Show statistics about the treasury’s impact on the ecosystem, testimonials and wide coverage regarding how Polkadot’s governance has been extremely beneficial for dApps starting up 4. Coverage of initiatives from W3F to support dApp building 5. Polkassembly’s stats to build more confidence on the governance system of Polkadot and the impact that can be delivered at scale |
| Mobile App (V1) | |||
| Governance experience on Mobile | Primary Features | To enable smooth usage of governance in a PWA app | 1. Migration & Testing of all off chain features including post creation, comments, replies, likes from the PWA 2. Integration on chain features by performing integrations with wallet applications 3. Increase response rate to optimize for mobile experience 4. Implement In app notification as per mobile experience |
| Tinder style voting | To enable quicker voting for users with summarized details only | 3. Building mobile specific features like - tinder style voting and notifications to ensure a great user experience for governance i. Building in comment AI summaries to enable quicker decision making for tinder style voting with all relevant information data points ii. Leveraging existing vote & AI summary to ensure users have a good overview of the proposal iii. Highlighting expert reviews and necessary details to enable users to make a quicker decision |
Here are some new product clips from our latest work —
We are excited for the future of Polkadot and to explore the depths of OpenGov's power to support the growth of our ecosystem, powered by Polkassembly!
The complete proposal details along with the budget are all included in the document here.
- Polkassembly helps manage Polkadot and Kusama governance.
- It wants yearly funding for maintenance and new features.
- Moving to yearly funding helps focus on better updates.
- Plans include analytics, new tools, and mobile app improvements.
- Aims to make governance easier and more fun for users.
- Works with other projects like Zeitgeist for extra features.
- Includes social features like profiles and notifications.
- Budget and details are in a linked document.
Source
Polkassembly is an integral part of Polkadot and Kusama governance.
This submission proposes an annual payment as part of our social contract with the Polkadot & Kusama treasury to cover maintenance, operations and human resource costs for Polkassembly, including general maintenance, runtime upgrades changes, new feature development and could/infrastructure cost.
Why has Polkassembly moved to an annual social contract?
Polkassembly is transitioning from a quarterly proposal model to an annual one to streamline our operations and enhance the value we deliver to the Polkadot community. This strategic shift is driven by several key factors:
1. Sustained Support and Development:
Moving to an annual proposal model allows us to secure more stable and long-term support for our team. This stability is crucial for maintaining a dedicated group of developers and contributors who can focus on continuous development without the interruptions that come with frequent funding cycles.
2. Enhanced Focus on Quality and Innovation:
With a yearly cycle, our team can dedicate more time to developing high-quality features and undertaking innovative experiments that require longer gestation periods. Planned pipelines and milestones with research will help deliver high quality features beyond the quarterly milestones
3. Comprehensive Reporting and Transparency:
Annual proposals enable us to provide more detailed and impactful reports on our progress and achievements. These comprehensive reports will offer clear insights into our contributions, backed by proof of work statistics, showcasing our commitment and the tangible benefits we bring to the ecosystem.
All these metrics are attached below in the Product Statistics and social statistics where our contribution and its significance can be seen
4. Strategic Marketing and Community Engagement:
A yearly cycle affords us the opportunity to plan and execute more strategic marketing initiatives. By aligning our marketing efforts with our development milestones, we can ensure that our achievements are effectively communicated and a long term strategy to promote OpenGov and its novel developments can be highlighted within and outside the community.
5. Maximizing Common Good and Addressing Opportunity Costs:
This model allows us to align our resources more closely with the common good of the Polkadot ecosystem. By considering the opportunity costs, we can prioritize projects and features that offer the highest value and impact, ensuring that our contributions are both meaningful and timely.
So essentially, transitioning to an annual proposal model reflects our commitment to continuous contribution, high-quality development, and strategic growth. With 95%+ of our milestones already achieved in the past year and over 50 new features rolled out, we are confident that this new approach will enable us to serve the Polkadot community even more effectively.
Our story is one of unwavering commitment and proven results, and we are excited to embark on this next phase of our journey with the support of the community.
So what are we upto in 2024?
| Theme | Feature | Goal | Tasks |
| Analytics | |||
| Analytics | Referendum Level Analytics | To provide detailed understanding of statistics on a referendum level | 1. Break down metrics into three types - DOT used for voting, number of voters participating and the DOT used with conviction during the vote for each referendum 2. Summarize with key metrics including Total Amounts for Delegation vs Solo Split, Aye vs Nay vs Abstain split and the Turnout. - All the above metrics can be seen as per the three metrics filters the three types of metrics filters mentioned in point 1 3. Show the time period distribution of the votes / voting power / voting power with conviction 4. Show conviction distribution for Delegated vs Solo & Aye / Nay / Abstain votes 5. Allow all the charts to be interactive and easily navigable from the referendum page directly. These will also be shown as navigable from within the Analytics Tab 6. The referendum level analytics will also highlight data regarding top whales, their percent contribution in a distributed graph |
| Track Level Analytics | To provide detailed understanding of statistics on a track level | 1. Break down metrics into three types - DOT used for voting, number of voters participating and the DOT used with conviction during the vote for each of the tracks 2. Aggregate key metrics including Total Amounts for Delegation vs Solo Split, Aye vs Nay vs Abstain split and the Turnout. - All the above metrics can be seen as per the three types of metrics filters mentioned in point 1 3. Allow all the charts to be interactive and easily navigable from the track page directly. These will also be shown as navigable from within the Analytics Tab. 4. An easy to use UX will allow comparison between different number of referendum to allow easy benchmarking 5. The track level analytics will also show delegation data of # of delegates, top delegates, their received delegations and total voting power as well as their participation status and contrarian index in general |
|
| Governance Level Analytics | To provide detailed understanding of statistics across governance | 1. A separate tab will house overall governance level analytics - This will also provide the option to navigate to track and referendum level details 2. Critical stats like Amount of DOT locked in governance, # of active referenda etc will be available here 3. Navigate across referenda in a track and category agnostic manner 4. Use tags, dates, amounts, and different filters to analyze governance as per user preference 5. See overall metrics like support, issuance, Delegation vs Solo Split, Aye vs Nay vs Abstain split and the Turnout across all referendum |
|
| New Features | |||
| Reports and Accountability | Deadline | To provide an understanding of when a proposal will be delivered by | 1. Community will have clear understanding of the final deadline of the proposal 2. There will be an option to add milestones for each referendum as well with independent deadlines |
| Progress Reports (Potentially in collaboration with Subsquare) |
To provide the community with an update on what was delivered and when / with what impact? | 1. Proposers will be nudged to add progress reports when the deadlines nears 2. Each milestone will have a separate progress report to track if the proposal has been submitted as per requirements 3. The progress reports will be shown the user’s profile along with other details - These reports will be shareable to X or on social handles - Users will be able to export these reports 4. Community can rate or comment on these progress reports which will enforce accountability |
|
| Evaluation tab | To ensure each proposal is thoroughly vetted on the idea and the proposer’s merits | 1. The evaluation tab will have multiple sections including - Proposer deepdive, beneficiary deepdive, Audits and the Progress Reports 2. Proposer and beneficiary deepdive will explain whether wallets are multisig or not, have been verified or not, their date of inception, as well as their average rating on past proposals and progress reports |
|
| Expert Body | Proposal Expert Review | To enable expert reviews on proposal page and highlight these in the interface | 1. Allow experts to submit reports on a proposal on Polkassembly along with an AI generated or manually added summary of the report - The export review will be highlighted like the AI summary for users to quickly browse through the entire report or just the summary of the report 2. Allow users to interact and comment on expert reports, as well as upvote or downvote them. - There can be questions or statements regarding the expert’s views on the topic at hand - These will be linked to the main discussion view as well 3. Highlight these expert reviews on description page and integrate these with alerts, on chain notifications 4. Enable users to engage with these expert reports, tip them if need be or allow the treasury tip worthy reviews to be highlighted in case of multiple reviews 5. Complete details can be found in the work doc - Link |
| Proxy Addresses | Create Proxy Addresses | To enable users to create proxies directly in Polkassembly | 1. Allow users to create - governance, non-transfer, staking, identity, cancel, auction and nomination proxies directly from Polkassembly 2. Allow users to identify addresses where proxies are present and select from multiple proxies injected based on login wallet / selected wallet 3. Linking of proxy wallet to profile to populate activity, balance, and delegation details 4. Allow users to unlink their proxy account and free up their locked balance from Polkassembly |
| Delegation | |||
| Overview Page | Trending delegates | To ensure users can participate in quick delegation via Polkassembly | 1. We highlight the top and most frequently delegated users with their voting details on the central ui of the profile 2. Allow users to directly delegate from this UX to increase quick delegations for uninitiated users |
| How to delegate | A quick two step guide to enable smooth delegations | Give users the options to either: - Select a track to delegate and then delegate their votes or - Select one of the top delegates and then choose relevant tracks to assign delegation |
|
| Become a delegate on Polkassembly | To allow users to highlight themselves as potential delegation candidates on Polkassembly | 1. Users can add their bio, socials and make a profile if they have not done so or link their original profile if it is already created to become a delegate 2. Delegates on Polkassembly will receive a special badge which indicates their reputation as a delegate everywhere on the platform |
|
| Data points for delegators | Statistics | To ensure users can track how the ecosystem’s current delegation status looks like | 1. We highlight the top metrics including - total supply, delegated tokens, total delegated votes, total delegators and total number of delegators being tracked on the platform |
| Badges | To highlight participants with exceptional contributions | 1. Delegates who have differentiable activities will be given badges on the platform i. Maximum participation ii. Highest number of delegators iii. Highest amount of delegated DOT/KSM iv. Experts in domains / active commenters |
|
| Unlock Delegations | To allow users to understand in how much time they would be able to unlock their delegate votes | To show delegators time to unlock their votes - with details around history of conviction, voting power on track level | |
| Delegate engagement | Delegation Mandate | To allow users to independently edit delegation mandate | 1. User will have a separate bio describing how they make their voting judgements, their general delegation mandate and why they should receive additional delegations 2. Their delegation mandate will be link to the profile and will be editable from the dashboard 3. Users will be nudges to verify their addresses before becoming delegates |
| Chat with delegates | A quick way to interact with delegates | 1. Discuss the reason for voting, mandate for voting, and many more details with a user by chatting with them via the delegation dashboard | |
| Fellowship (Milestone 2) | |||
| New Features | Calendar | To show important events in the fellowship as well as expected timelines | 1. Important on chain events, execution dates and offchain events like Polkadot Blockchain Academy will be tracked here 2. Fellowship Member inductions and anniversaries will be trackable from these events |
| Micro-features | A set of mini improvements to the currently live collectives platform | 1. Addition of multiple RPC endpoints to ensure a smoother experience in different geographies 2. Dark mode customization and improvements to ensure standardization in the product 3. Tooltips and tipping for fellowship platform to allow users to quick view fellows instead of directly going to their profile 4. Trending Proposals on fellowship and their status to allow quick access to these proposals and voting on them 5. Empty States across platform and loaders to ensure a smooth experience especially in case of heavier on chain calls or images 6. Nudges for new fellows and existing ones regarding on chain activity to ensure that there is a smoother onboarding to best practices of the platform 7. All Fellowship Meeting recordings redirection and calendar events for new fellows to ensure they can access past information. — Preimage tab to find, navigate to, execute and unnote preimages allowing the execution of all detailed steps directly from the fellowship platform. — An independent pending tab for a user to show them activity that is dependent or pending on them only - making for an engaging social feed. — Allow mentioning other users and notifications for mentions in fellowship |
|
| Westend | Quick deployment and testing of features on Fellowship | 1. Westend platform deployed with equivalent functionality to the Polkadot Fellowship for fellows and non fellows to explore the product | |
| Fellow Experience | Personalization | To make the fellowship product more customized as per needs of fellows | 1. Notifications for Fellows - For all kinds of activity that they would like to follow and keep track of as per their preference on various channels including telegram, discord, mail and eventually element and slack 2. Following Fellows and receiving updates regarding them in the activity feed - Optional view for seeing votes and activity by only these fellows 3. Allowing for searches based on fellowship activities, members names and more |
| Fellowship Statistics | To show important statistics for fellows | 1. Detailed statistics for salary pallets - Total salary drawn, salary available in a cycle 2. Number of members inducted, requests created, referendum created, voting analysis on each of the referendum and more |
|
| Mobile view | Mobile experience | To allow members to access the fellowship platform on their mobiles for engaging and quick actions | 1. Each of the features available on the web view would be made available in the fellowship’s mobile version - Overview Pages - Membership Page - Proposal Pages - User profile 2. Allow users to take all offchain actions directly from the mobile view - Edit social handles - Edit About - Link Github - Add comments, reactions - Navigate through timeline |
| Integration with Github | RFC proposals | Enable ease of engagement with RFC proposals | 1. AI Summary for PRs, RFC and issues in activity to allow members to read through the details 2. Convert RFC PR to Proposal on activity tab |
| Github Integration | To allow a deepdive into contributions made by fellows as well as highlighting top fellows | 1. To import the activity done on fellowship repository and show it along with summary statistics in the fellowship platform 2. To show the top fellows in a given time period and contributions made by them 3. To have stats regarding contributions by fellows 4. Integration with Github verification identity for DOT when it goes live |
|
| Product Partnerships | |||
| Prediction markets | Zeitgeist Integration(Live) | To boost community engagement participation in Governance | 1. Twitter announcement¨ 2. Few markets around governance - Ref #303, Ref #307, Ref #350¨ 3. These markets were live on Polkassembly to drive dApp adoption as well as on Zeitgeist 4. Media coverage - Captain Altcoin, Finance Feeds, CoinGape 5. Show the interface on Polkassembly with current market prediction data from Zeitgeist, number of participants and deep linking to the ZTG market on Zeitgeist |
| To choose and create new markets via Zeitgeist & deep integration of prediction markets | 1. Polkassembly takes the responsibility of identifying new markets and ensuring that the most exciting markets are used for predictions 2. Moving towards a deeper integration of prediction markets by showing a more detailed view of predictions |
||
| Subsocial | Deeper integration with subsocial | To enable more cross platform features/data feed from subsocial | 1. Fetch relevant posts from subsocial and show with relevant proposals 2. Deeper integrate subsocial-chat with Polkassembly |
| Points & Leaderboard | |||
| Points System | Leaderboard Formulation | To enable a gamified understanding of a users contribution to governance via a single metric | 1. The first version of proposed scoring system indicates the distribution of points for various off chain and on chain activities done via Polkassembly 2. Please refer to this link for detailed understanding of how it works- It includes positive points for actions which improve governance dialogue and evaluate - Negative points for actions which are detrimental to collaboration and discussions 3. The leaderboard will have various filters including all time, weekly and monthly to ensure governance participants in different time frames are highlighted. |
| Score breakdown for each user | To enable each user to understand how their score is calculated | 1. This will be available at multiple touchpoints including the profile, quick view tooltip and in the leaderboard 2. Opening this would explain the exact distribution of points credited to a user 3. The score will be evolved over a period of time based on the inputs from various community members 4. Each existing and new activity on Polkassembly will lead to points being rewarded to users |
|
| Social | |||
| On Product Notifications | Single notification hub inside Polkassembly | To enable users to access notifications in a central system | 1. Polkassembly presently allows users to configure what kind of notifications they would like to receive off chain on mail, telegram and discord 2. We will enable users to receive all existing notification and more updates on chain, in a simple consumable interface where notifications can be marked as red / unread increasing the overall engagement on the platform as well as making it easier for users to reply to mentions and comments on their discussions 3. The feature will include microfeatures - to open notifications in a full page view, mark all notifications as read, and cluster notifications together |
| Mentions | In proposals, comments and replies | To enable users to mention users across the site | 1. Users will be able to tag any user by simply typing @ & their username - A preview will show recommended users to ensure users do not need to know the exact username - This mentions will be visible on the users profile and will be deeplinked to their on product notifications 2. Based on the configuration of the users alerts - they will also receive these on channels including telegram, discord, mail and eventually element & slack |
| Follow | Profile based following | To enable users to follow each other’s governance activity on Polkassembly | 1. Presently we allow following posts and receiving notifications for updates on them 2. We will enable users to follow each other and whale accounts setting precedent for the platform to become extremely social. - Notifications can be received on product or off product for these follower activities 3. The count for followers and following will be available on the profile 4. Users will also be able to see details of who a user follows or is being followed by |
| Timeline (Activity feed) |
Social Timeline as platform default view | To build an engaging social experience within Polkassembly | 1. Independently show users the activity which they have participated in and whatever is pending on them to participate in - especially in case of referenda 2. Show activity about users they follow in the feed¨C156C- The can choose to receive updates about votes, comments, likes, dislikes, discussions or proposals 3. Allow users to directly like, dislike, comment, reply or even vote from the feed 4. Show non governance activity in the ecosystem (events, etc. from calendar & news), directly on Polkassembly to bring more visibility to them 5. Integrate microfeatures which make the social feed more engaging and collaborate with industry partners to make this representative of activities in the entire Polkadot Community |
| Share vote on Social Media & Social NFTS | Enable NFTs for voting which are shareable | To build an experience around sharing of vote based NFTs on social media | 1. Design multiple kinds of aye, nay, split, abstain NFTs 2. Ensure each referendum vote can be stored as a separate NFT and is shareable on X or other social channels 3. Tie these NFTs with the person’s reputation. Calculate a contrarian index to evaluate how many votes were casted in negation |
| Profile NFT Integration | Enable integration of NFTs in governance profiles | To build a holistic reputation for individuals on Polkassembly | 1. POAPs, Social NFTs, Soul bound NFTs, gaming and other such NFTs will be imported into each user’s profile - Polkassembly will run a social campaign to promote this multiple ecosystem partners 2. Users would be able to identify and connect / follow users with similar POAPs of NFTs via a common listing page where the holders of each NFT will be listed - These listing pages would be linked to the NFT marketplace of other platforms and would indicate stats like # of total holders, floor price, etc |
| Badges | Gamification of user profile | To build tags which can help identify a user and understand their voting patterns | 1. Delegate, fellows, delegators will have custom badges which help identify their profiles in forum based discussions easily 2. Voters with high contrarian index, always nayers (bot voting), highest dot, high and low conviction voters could have interesting badges which gamify the experience 3. These badges will be open sourced for allowing the community to easily access them 4. Users would be able to identify and connect / follow users with similar badges via a common listing page where the holders of each NFT will be listed - These listing pages would indicate stats like # of total holders, when is the badge issued and more |
| Bounty Product (V1) | |||
| Use Cases | Social Bounties | To allow members to post collaborative bounties for community to solve in Polkadot community The product will enable the community to leverage their social network for ad hoc tasks, introductions reviews and much more |
Polkadot ecosystem presently only allows funding of bounties via the treasury. Polkassembly intends to create a social bounty product which will - 1. Allow community members to tweet for a bounty or create it directly on the platform - If tweeted, a twitter bot responds and continues to engage with the tweet ensuring that the bounty is created and there is public attention to it 2. Allow deep linking of bounties from social handles like X, & potentially social platforms like me.we & Polkaverse in the DOT ecosystem - Each user has a unique profile which is either created by signing up on the platform or auto-generated when they tag and post bounties. A unique user id is assigned to track activity and introduce social accountability on bounty payouts 3. Nudges to fund the bounty in advance - This is done by either allowing a single funder or the community to fund a public bounty 4. Initially follow a centralized approach to bounty approval - where the creator decides the best bounty 5. Eventually make the process of optionally funding bounties in a decentralized manner as well 6. Enable social engagement like upvotes, downvotes, comments and replies on the platform |
| Product Features | All Bounty Timeline | To allow users to see all published bounties and their status | 1. The list of bounties shows details including the funder, the time of creation, user profile, comments, reactions 2. The status of a bounty helps a user understand if the bounty is still accepting submissions or if it has been closed |
| Profile Page | To allow users to maintain their profile and reputations | 1. Profile level details include - Username, profile picture, total amount of bounties created, total amount of bounties funded, bounties earned, number of bounties created 2. Listing view of submissions, bounties created and submitted |
|
| Bounty Dashboard | Custom Bounty Interface | To boost the adoption and visibility for bounties in the ecosystem | 1. Highlight all open, closed and in voting bounties in a separate interface 2. Show breakdown of amounts, details of progress and potential targets for each bounty 3. A working doc for the bounty product can be found attached here — Link 4. Dashboard i. Top Level statistics on Available Bounties, Total Amount in DOT & USD, other relevant statistics ii. Bounty Cards highlighting different bounties, their status, Category, tags, amounts, no. of sub-bounties, etc. iii. Details about Polkadot bounty - educational material and video tutorials on creating bounty proposals via Polkassembly iv. Create bounty button 5. Bounty Detail page i. How to make a submission for that bounty ii. Portal to make submission for the bounty iii Tracking status of the bounty submission iv Read, review comments and update bounty submission if required Parent Bounty proposal details and discussions(comments + voting details) For curators i. Being able to view and track all active submissions ii. Manage active submissions and leave comments or communicate with bounty submitters iii. Initiate payout for sub-bounty iv. Update status for bounty v. Cancel bounty Profiles i. Number of sub-bounties created ii. Tracks/categories in which bounties were claimed iii. Total amount earned from sub-bounties, etc. |
| Maintenance - Features | |||
| Creating proposals on Polkassembly | Proposal creation for all tracks | To all the creation of different tracks of proposals on Polkassembly | 1. Currently users can use Polkassembly’s powerful interface only to create proposals in the treasury tracks 2. Users will be allowed to create proposals to kill any referendum - which would slash the decision deposit 3. Users will be allowed to cancel any referendum which will cancel the proposal and return the deposit 4. Users will also be allowed to create any kind of referendum - This would include a form which allows selection of multiple parameters to create a preimage - This preimage will be linked to the preimages tab of Polkassembly - After this a one click, seamless proposal ensures that the proposal is created on Polkassembly in a continuous manner with the descriptions as a part of the proposal - The user will also be provided the option to pay the decision deposit immediately after creation of the proposal 5. Relevant nudges on Overview page, track level pages and in FAB to allow creation of referendum from different touchpoints |
| Multiple beneficiaries on treasury proposals (Live) |
To allow users to show multiple on chain beneficiaries and request for funding in a transparent manner | 1. Based on community requests we developed and delivered a feature to easily add multiple beneficiaries while creating a proposal - a process which is very difficult on PolkadotJS 2. Each address can be added independently and the relevant amount for each address can be indicated next to it 3. There are also relevant nudges to indicate if an identity is verified or not and if the address is a multisig or not in the AI summary as well as during proposal creation process |
|
| Profile | Interface upgrades(Live) | To bring all governance statistics in a single comprehensive profile | 1. UI revamp - For votes casted, proposals created, discussions created, linking addresses, multisigs and proxies 2. Allow editing of social handles, profile pictures, cover image, user name 3. Allow actions like tipping, delegation, unlocking votes, unlocking proposal deposits directly on profile |
| Delegation integration(Live) | To integrate delegation dashboard with profile of user | 1. Show a detailed view of number of delegation received and delegations given - Allow users to view/add delegation mandate on profile - Show number of delegation received across tracks. Each user's voting power and address are shown. Details show the number of tracks on which votes have been delegated as well as amount and conviction delegated on each track - Show number of delegation given with the same details mentioned above - Allow selection of address from multiple addresses linked to profile |
|
| Detailed balance information | To show breakdown of users token balance | 1. Show user’s total token balance split across locked balance and transferable balance 2. To show user’s total voting power split across self voting and delegations 3. To show user’s vote balance locked in staking 4. Allow users to select between different addresses that are linked to a profile and show aggregate of statistics which have been mentioned above |
|
| Comments, reactions and mentions | To show users’ off chain engagement history | 1. To show comments and replies by a user. 2. To show mentions of a user 3. To show reactions of a user 4. To show timestamps as well as engagement details of other users on the above mentioned activites |
|
| Maintenance - Technical | |||
| Technical Integrations | Subsquid migration(Live) | To enable seamless transition to latest technical infrastructure offered by Subsquid | 1. Migration to the arrow squid offered by Subsquid for Polkadot & Kusama along with sdk integration changes |
| Site wide analytics | Implementing instrumentation to ensure site wide tracking and reporting of statistics in proposals | 1. All twitter posts made for engagement including # of views, # of proposals created, etc. have been done by leveraging the instrumentation implemented across the site 2. The instrumentation has been split into three phases, with only phase 1 live currently | |
| Development & Open Source Standardization | Design system integration | To ensure a seamless user experience (consistency in components) and fast development | 1. After completing the migration to NextJS the product speed, responsiveness and overall performance have been significantly improved 2. Design systems set up for components i. Buttons - - Primary button - Secondary button - Default button - Disabled button - Icon button ii. Forms - Input fields - Textareas - Select dropdowns - Checkboxes and radio buttons - Switches and toggles iii. Typography: - Heading styles (h1 to h6) - Paragraph text - Bold and italic styles - Lists (unordered and ordered) - Blockquotesiv.Navigation - Navbar - Sidebar - Breadcrumbs - Paginationv. Cards - Basic card - Image card - Actionable card vi. Modals and Popovers: - Modal dialog - Popover and tooltipsvii. Icons: - Use a library of scalable vector icons.viii. Alerts and Notifications: - Success alert - Error alert - Warning alert - Info alert ix. Loading Indicators: - Spinner/loader x. . Tabs and Accordion: - Tabbed navigation - Accordion for collapsible content xi. Progress Bars: - Linear progress bar - Circular progress bar xii. Tables: - Basic table - Data tables with sorting and filtering xiii. Badges and Tags: - Status badges - Tag labels xiv. Utilities: - Spacing and layout utilities (e.g., margin, padding, flexbox) - Color palette and theming |
| Automated Testing | To ensure continuous testing for smoother product evolution | 1. Leverage selenium to build an automation testing pipeline for all off chain features including - login, discussion, comments, replies, reactions, page views | |
| Site Experience Improvemenet | JWT Issue fixes(Live) | To ensure smooth auto logout experience for users | 1. Maintain JWT sessions between old architecture and new next JS architecture 2. Auto logout for users, helping prevent errors due to JWT timeout. |
| Cache control | To ensure smooth cache control in nextJS and cloudflare | 1. Enable caching in Cloudflare for all resources possible to reduce hosting costs and reduce load on the server, increasing server reliability. | |
| Package size(Live) | To improve load time on the platform | 1. Replace SVG files with links to reduce the package size from 3.41 mb to 2 mb and ensure image component creation to continue sustainable development by replacing 20+ files | |
| Refactoring (Live) | To improve delegation dashboard speed and experience | 1. Improve api response time and removed redundancies 2. Improved undelegation or delegation response time to 2 / 3s and optimize on chain calls |
|
| Improve Vote detail info | To allow users to see all vote details in a consumable view | 1. Allow users to see vote time, % of voting power even for non delegated votes | |
| Maintenance - Microfeatures | |||
| Description API | OpenAI API(Live) | To allow users to access Polkassembly’s AI Summary | The AI Summary API has two options 1. The format available on Polkassembly 2. A 250 character AI summary for teams looking to show a shorter summary |
| Referendum Page Mircofeatures | Quote / Share Comments | To allow users to quote a portion of a proposal, comment or reply | 1. Users will be able to see quoted replies, comments or proposals 2. These will also be shareable directly to social media |
| Status level filters(Live) | To allow users to filter proposal based on status | 1. Filtering on tags is already live 2. FIltering on statuses including timed out, confirmation, etc. to allow a deepdive into various aspects of governance 3. Creation of the all tab and allowing filtering via tracks or topics on it |
|
| Bounties | To show detailed breakdown of a newly proposed bounty or child bounty | 1. Currently visibility into the details of a bounty are very less. The feature will show % of bounty that has already been claimed, % requested and how much will remain after bounty approval - The detail will be available on the proposal detail page as well as the listing view | |
| RHS Cards with scroll on proposal page(Live) | To allow users to take contextual actions directly from the page | 1. Pay the decision deposit to ensure the proposal enters in to the voting period 2. Add a description to ensure that the community has complete details about the referendum 3. Add a deadline date for your proposed proposal so that the community has visibility about the delivery date 4. Link the referendum to an existing discussion post to import comments and description from the post 5. Show time to confirm or time to fail for a proposal on the RHS directly |
|
| Feature Scope Improvement | Verify identities on Kusama | Deploying the feature to set and verify identities on Kusama with ease | 1. Similar to Polkadot, users will be able to follow a simple two step process to set and verify their identity directly on Polkassembly |
| Reply to Subsquare Comments on Polkassembly | To enable proposers and users to complete entire conversations on Polkassembly | 1. Most users struggle with replying to comments from subsquare even though they occupy <2% of comments in the governance of Polkadot & Kusama historically. 2. We will allow users to reply to comments on Polkassembly and based on further progress they should be able to interact freely on the with the replies / comments & like / dislike / report them |
|
| New alerts for users | To allow an even larger and comprehensive set of alerts for users to configure | 1. Alerts for receiving a delegation or undelegation on chain 2. Alerts for a proposal entering into a confirmation state or leaving from it - Multiple more to be added |
|
| Mobile view improvements | To build a better mobile experience for Polkassembly | 1. Improve vote details screen on mobile - for seeing details of a vote and distribution between delegated & solo votes on mobile 2. Improved ux of proposal detail page 3. Custom overview page for mobile view to make better experience 4. Referendum page - splitting of boxes and smoother scrolling experience in mobile view |
|
| New Mircrofeatures | Show votes on listing view | To allow users to identify which proposal they have voted for directly from the listing view | 1. Users can directly see their vote type - aye, nay, abstain or split and the amount as well as conviction directly from the listing view of all / track specific pages |
| Compulsory username setup (Live) | To ensure users find a consistent experience in the platform | 1. Polkassembly earlier saw a lot of usernames not being set and hence wallet address being used as usernames 2. Now, every new users must set their username on login and can optionally set their email address to receive alerts |
|
| Cancel Preimage | To allow users to cancel erroneous preimages and receive their deposit back | 1. The option to cancel a preimage is provided on two touchpoints i. The preimage tab where different preimages created by the proposer can be canceled ii. The proposer tab(Live) 2. If a preimage has been canceled, the status should show on the referendum page as well |
|
| Proposal tagging | To enable retroactive tracking of proposal types, spends and more directly on Polkassembly | 1. Using publicly created tags and breakdown of proposals into different categories to retroactively tag proposals 2. Continue building towards the effort of treasury analytics directly on Polkassembly |
|
| Data Decentralization | Decentralizing proposal data(Potentially in collaboration with Subsquare) | Data Decentralization is an important step in progressing Polkassembly and OpenGov to decentralization | 1. Decentralizing the following data sources - discussions - comment, reply data - proposal description data - Profile bio & off chain social handles - Delegation bio - Profile Image & Cover image of a user - Off chain voting signals This will ensure the compliant storage of data as well as true decentralization for the project 2. Migrate previous data to IPFS 3. Add middleware to ensure new data moves to IPFS. Ensure collaboration with teams building in the ecosystem to subsidize costs |
| Landing page | Polkassembly landing page revamp | To ensure a better onboarding for users and provide them with more information about OpenGov and its capabilities when they land on polkassembly.io | 1. Polkassembly attracts the largest number of users to governance in the DOT ecosystem. 2. The website brandings should indicate and explain different governance mechanisms and how partners building on Polkadot can leverage the pallets as per their team’s stage 3. Show statistics about the treasury’s impact on the ecosystem, testimonials and wide coverage regarding how Polkadot’s governance has been extremely beneficial for dApps starting up 4. Coverage of initiatives from W3F to support dApp building 5. Polkassembly’s stats to build more confidence on the governance system of Polkadot and the impact that can be delivered at scale |
| Mobile App (V1) | |||
| Governance experience on Mobile | Primary Features | To enable smooth usage of governance in a PWA app | 1. Migration & Testing of all off chain features including post creation, comments, replies, likes from the PWA 2. Integration on chain features by performing integrations with wallet applications 3. Increase response rate to optimize for mobile experience 4. Implement In app notification as per mobile experience |
| Tinder style voting | To enable quicker voting for users with summarized details only | 3. Building mobile specific features like - tinder style voting and notifications to ensure a great user experience for governance i. Building in comment AI summaries to enable quicker decision making for tinder style voting with all relevant information data points ii. Leveraging existing vote & AI summary to ensure users have a good overview of the proposal iii. Highlighting expert reviews and necessary details to enable users to make a quicker decision |
Here are some new product clips from our latest work —
We are excited for the future of Polkadot and to explore the depths of OpenGov's power to support the growth of our ecosystem, powered by Polkassembly!
The complete proposal details along with the budget are all included in the document here.
Request
≈172.07KDOT
Status
Decision28d
Confirmation
7dAttempts
1
Tally
81.4%Aye
50.0%Threshold
18.6%Nay
Aye
≈59.62MDOT
Nay
≈13.62MDOT
- 0.0%
- 0.0%
Threshold
- 0.0%
Support
1.25%≈17.19MDOT
Issuance
≈1.37BDOT
Votes
Nested
Flattened
Calls
Check how referenda works here.
Call
Metadata
Timeline6
Votes Bubble
Curves
Statistics
Timeline
Comments
Request
≈172.07KDOT
Status
Decision28d
Confirmation
7dAttempts
1
Tally
81.4%Aye
50.0%Threshold
18.6%Nay
Aye
≈59.62MDOT
Nay
≈13.62MDOT
- 0.0%
- 0.0%
Threshold
- 0.0%
Support
1.25%≈17.19MDOT
Issuance
≈1.37BDOT
Votes
Nested
Flattened
Calls
Check how referenda works here.