Close Menu
Polkadot governance report - subdaily

Executive Summary

Spotlight proposal

The Polkadot spotlight proposal for this report is the
runtime Upgrade of Polkadot to v9420 (Ref #121), whose enactment introduces OpenGov to Polkadot.

Governance changes

There are currently 8 proposals on Polkadot that were either open for discussion within the last 7 days, or currently up for voting.

Top 5 delegates

Applicable once Opengov ship to Polkadot

Spotlight proposal

The Kusama spotlight proposal for this report is Subsocial's OpenComms proposal - an "Open Communication Layer" for the Polkadot ecosystem

Governance changes

There are currently 9 proposals on Kusama that were either open for discussion within the last 7 days, or currently up for voting.

Top 5 delegates

Governance activity overview

Number of proposals

There are currently 8 proposals on Polkadot that were either open for discussion within the last 7 days, or currently up for voting.

Treasury vs Non-treasury

Status

Number of proposals

There are currently 9 proposals on Kusama that were either open for discussion within the last 7 days, or currently up for voting.

Treasury vs Non-treasury

Status

Reports and Interesting discussions

Polkadot

Encode Club x Polkadot Education Series and Hackathon Tranch 1 report

Encode club has released a summary report for Tranch 1 of their series/Hackathon to request funding for tranches 2 and 3. 

The Encode x Polkadot Educate Series was met with great success, engaging over 1200 participants with an eight-part series, covering a wide range of topics from Polkadot basics to more advanced subjects like Wasm smart contract development. Notable sponsors such as Acala, Subsocial, Astar, and others delivered a wealth of insights into the Polkadot ecosystem.

Post education series, the Encode x Polkadot Hackathon took the stage, attracting 350 participants to this four-week online event. During this period, participants got the chance to build and submit their projects for judgement while learning, networking, and attending several related events. This hackathon, aimed at fostering learning, collaboration, and innovation, has drawn strong attention to the potential of the Polkadot ecosystem.

You can check out their report here.

Grabber passes council vote

The proposal by Grabber, a tool that incentivizes experts and leaders within the community to boost governance engagement and voter activity, has passed council vote. 

Grabber aims to improve Polkadot’s governance system by incentivizing deep community engagement and expert involvement. Given the complex nature of governance decisions within the Polkadot ecosystem, the community requires tools to streamline the analysis and voting process on governance proposals.

The current system requires a significant time investment from voters who must thoroughly understand and evaluate each proposal, which is both inefficient and challenging. Grabber proposes the formation of a decentralized group of experts who will review and report on these proposals, thereby reducing the time and expertise required from ordinary voters.

This model introduces an incentivization mechanism, offering bounties to these experts based on a reputation system. Their reports would allow the broader community to gain direct insights into the proposals, fostering informed voting. Through this system, Grabber seeks to bolster efficient, informed governance within the Polkadot ecosystem.

 

Kusama

Polkassembly launches new edit history feature

Polkassembly has launched the edit history feature which gives complete visibility into the off chain history of user’s comments, posts and proposals data. This will be available for all edits done on or after 13th May, 2023.

Opensquare bounty for vesting pallet scan

Opensquare has created another bounty for vesting pallet scan on Subsquare, dedicated to the development of a tool that will allow users to access information about their vesting schedules on substrate chains. This information includes the status and details of all vesting schedules on the chain, as well as vesting records pertaining to specific accounts or schedules. The tool is intended to support user functionalities such as viewing vesting statistics, checking the locked balance for current vestings, and exploring historical vesting records.

The development work involves querying from the blockchain storage to obtain an account’s vesting information, extracting extrinsics/events for business handling from chain RPC queried blocks, handling these events or extrinsics to extract business data, and normalizing and saving this data to MongoDB.

Implementers need to have a basic understanding of blockchain concepts like transactions, events, state, and contract, as well as experience with Node.js programming. The bounty is funded by the Kusama treasury and curated by the OpenSquare team, who will provide necessary guidance. Links to the parent bounty and the issue on GitHub are provided for reference.

Polkasafe docs are live

Polkasafe has launched their Docs to help users navigate the app better and provide information on multisig, proxies, etc.

Polkasafe offers a secure, efficient way to manage assets in the Polkadot ecosystem. The Polkasafe docs is a dedicated guide divided into several sections, providing instructions and insights for users to fully utilize the features of Polkasafe.

You can check out the Docs here.

 

On-chain treasury proposals

Polkadot

Motion #405

Proposal: Polkadot education content production extension by Cryptonitas

Details

This proposal is authored by Cervera, the creator of Cryptonitas, a channel focused on providing Spanish-language content about the Polkadot and Kusama networks. The main goal of this initiative is to address the lack of accessible and user-friendly information about these networks for Spanish-speaking users. The proposal recaps past efforts, which include the creation of step-by-step video tutorials, organization of community events, and support for the community through a dedicated Telegram group. The content creator is also a curator for Polkadot and Kusama, evaluating and rewarding Spanish-language content produced by the community.

Past strategies involved search engine optimization (SEO) of the content, resulting in high views and watch time. However, attempts at paid advertising led to higher views but lower user engagement. As a result, the proposal aims to return to a SEO-focused strategy. Metrics from past initiatives show the significant impact of the educational videos, with an example given of over 2,800 views for a video on pool participation and an associated increase in pool membership and staking.

The proposal outlines several sections for the next stage of content development. These include educational tutorials about Polkadot and Kusama’s features, news updates on network governance, live shows for user support and community discussions, and short informative clips. A new feature to be tested is interviews with key members of the Polkadot and Kusama ecosystem. The content will be free and accessible, and distributed through various channels, including the Cryptonitas Telegram channel, Polkadot en Español and Kusama Español channels. The proposal includes a detailed budget breakdown for the production of the different types of content.

Status: Gov 1.0 vote ongoing

Results

Brief analysis

The proposal pertain to the development and delivery of digital content, primarily through a YouTube channel, to educate and inform a cryptocurrency-based community. The comments provided by the reviewers offer a range of opinions and raise pertinent questions that address different aspects of the proposal. The major themes and issues revolve around the proposed budget, content planning, and team transparency.

The proposal’s budget has come under scrutiny from several reviewers. The main contention lies in the perceived discrepancy between the proposed costs and the perceived value or quality of the proposed content. One reviewer suggested a different remuneration model based on performance rather than a fixed sum. The proposer should provide a detailed and itemized breakdown of costs to address these concerns and justify the proposed budget.

Some reviewers highlighted potential redundancies or inefficiencies in the content plan. Suggestions to consolidate certain topics into singular videos, or to dub over existing content instead of creating new content, are worth considering. Concerns were also raised about the proposed live shows’ format and the potential benefit of using Twitter Space to reduce overheads. Furthermore, the absence of specifics on the interviews to be featured on the channel adds a degree of uncertainty to the proposal’s value proposition.

There were also some queries about the face-to-face meetups. It is crucial to demonstrate that these meetups meet a real demand and target audience based on prior research.

The proposal, as it stands, has both strengths (in its attempt to create educational and engaging content for the Polkadot community) and weaknesses, particularly in the areas outlined above. More clarity, detail, and justification are required in these areas to strengthen the proposal and to reassure community members of the proposal’s value and the team’s commitment to delivering on their promises.

Motion 406

Proposal: Dot.alert() operational costs – Q2-Q3 2023

Details

Dot.alert() is a project designed to simplify the complexity of the Polkadot ecosystem, alert users to potential risks, and provide context for various tools and software relevant to the ecosystem. It aims to expand the understanding of Polkadot by developing a comprehensive knowledgebase, ensuring content is open-source and accessible to a global audience, and designing a platform for community expertise sharing.

Launched in August 2022, the Dot.alert() team consists of a blend of team members, active contributors, and volunteers. To date, the platform has published over 30 articles on various topics within the Polkadot ecosystem, such as Relay chains, Parachains, and different use cases. It also promotes engagement with its content through monthly quizzes testing participants’ knowledge of the Polkadot ecosystem.

In this proposal, Dot.alert() is seeking funding to continue its operations for Q2 and Q3 of 2023.

The platform’s goal is to maintain its growth and outreach as per the objectives outlined in its annual strategic plan. The detailed proposal, including milestones, tasks, and costs for April to September 2023, can be accessed from the proposal page.

In addition, Dot.alert() has made available its reports for Q1 2023 and Q4 2022 milestones for review.

Status: Gov 1.0 vote ongoing

Results

Brief analysis

Dot.alert() is an initiative targeted at the Polkadot ecosystem with a focus on creating accessible and engaging content for both experienced users and newcomers. The platform effectively covers a broad range of subjects, including the technologies involved, security practices, user-friendly tools, and the broader context of Polkadot’s development.

Dot.alert()’s extensive strategic plan for Q4 2022-Q4 2023 demonstrates a thoughtful and proactive approach to its future development. The organization’s aim to recruit more writers, improve SEO, provide detailed user analytics, and promote the platform across multiple channels suggests a strong commitment to growth and user engagement.

However, given the complexity of the Polkadot ecosystem, ensuring that content remains accessible to a non-crypto audience may be a challenging task. The balance between comprehensiveness and comprehensibility will be crucial.

Overall, Dot.alert() appears to be a well-conceived and efficiently run platform, contributing positively to the Polkadot ecosystem by filling a vital need for user-oriented, easily understandable, and comprehensive educational content partaining to security practices and blockchain regulations. Its future plans indicate a strong potential for growth and increased community engagement.

Motion #407

Proposal: A Survey of the Polkadot Data Ecosystem

Details

In this proposal, Polkalytics, a data analytics service for Polkadot, intends to create a comprehensive knowledge base about all data-related aspects in the Polkadot ecosystem. This is in response to the challenge of navigating through the vast and complex world of Polkadot data.

The plan includes creating a website and a Github repository that will act as an information hub for both newcomers and existing stakeholders. It aims to offer a standardized format of research and data that can be easily reused by other projects.

The knowledge base will include Polkadot-specific terms and definitions, reports, actors, tools, websites, libraries, datasets, schemas, and metrics relevant to Polkadot. The data will be collated through meticulous research, including review of Polkadot and Kusama Treasury and Web3 grants, interaction with teams, and investigation of Github repositories.

The ultimate goal is to ensure the Polkadot Data Ecosystem is more connected and discoverable. It is anticipated this initiative will fast-track onboarding, enhance information distribution, aid in constructing multi-chain dApps, and encourage institutional adoption.

All the work will be released in the public domain, and Polkalytics plans to maintain the repository for at least half a year after the project’s completion. This proposal, estimated to take up to 108 hours of work, requests a funding amount of 2128 DOT / 12k EUR, and the project is expected to be completed within two months of approval.

The motion for this proposal is currently ongoing here.

Status: Gov 1.0 vote ongoing

Results

Brief analysis

The Polkalytics proposal to create a comprehensive knowledge base about all data-related aspects of the Polkadot ecosystem is an ambitious and significant undertaking that addresses several key challenges in the Polkadot ecosystem.

The proposal recognizes the current disconnect and lack of discoverability within the Polkadot Data Ecosystem. Creating a hub for researchers, builders, and investors to access and contribute to a centralized repository of information will increase collaboration and facilitate the development of new applications and solutions.

The proposed budget and timeline seem reasonable given the scope of the project. However, the broadness of the project, coupled with the vast and rapidly evolving nature of the Polkadot ecosystem, may pose challenges in terms of staying up-to-date and maintaining the repository in the long term.

Overall, the proposal has the potential to significantly enhance the Polkadot data ecosystem. However, its success will likely depend on the degree of community engagement and contribution, as well as the ability of the Polkalytics team to effectively manage and maintain the repository over time.

Motion #408

Proposal: Centrifuge On-Chain Automated Treasury Management (with TWAMM)

Details

This proposal is from k/factory, a core development team contributing to the Centrifuge project, for the development of an On-Chain Automated Treasury Management system using a Time Weighted Automated Market Maker (TWAMM). TWAMM is designed to eliminate front-running vulnerabilities of traditional Automated Market Makers (AMMs) when executing large orders, especially in the context of governance.

The project will be completed in four milestones:

  1. Implement TWAMM pallet for Substrate: This will use pallet-asset-conversion to provide basic AMM functionality and the handling of long-term orders that split orders into infinitesimally small suborders over a given time interval. This phase is estimated to cost $190,000.

  2. Protocol improvements: This phase includes optimizing Virtual Order Execution data structures for Substrate, supporting generic embedded AMMs, adding fuzzy tests, and providing documentation. This phase is estimated to cost $80,000.

  3. Security Audit: The project will undergo a security audit from SR Labs, which will cost $120,000.

  4. Frontend development: A react.js-based frontend will be set up to handle various treasury operations. The frontend development is estimated to cost $94,500.

The team is requesting a total of $494,500 (~80,999 DOT based on EMA7) to fund the development of this system.

Status: Gov 1.0 vote ongoing

Results

Brief analysis

This proposal from k/factory appears well-structured and backed by a team with a successful track record in the Polkadot/Kusama ecosystem. The team has worked extensively on launching the Centrifuge and Altair parachains and delivered multiple grants.

The aim of implementing a Time Weighted Automated Market Maker (TWAMM) is to address a crucial shortcoming in the current Automated Market Maker (AMM) model. Specifically, the TWAMM is designed to eliminate front-running vulnerabilities of traditional AMMs when executing large orders. This is significant as it will enhance security and efficiency in executing large transactions, especially those related to governance and treasury operations.

The proposal is thorough and detailed with well-articulated milestones. The inclusion of a security audit in their roadmap demonstrates an understanding of the importance of robust security measures in blockchain implementations. The development of a frontend interface is also beneficial, enhancing user-friendliness and accessibility.

On the budget side, the request is quite substantial, though it seems commensurate with the scale of the work to be undertaken, especially given the hourly rates for development, the complexity of the proposed solutions, and the security considerations involved. The payment is also divided into tangible deliverables, allowing for accountability at each stage.

The main risk comes from the inherent complexities of developing such a system, including the technical challenges in implementing a TWAMM, optimizing its operation, and ensuring it works seamlessly with other systems. The successful execution of the proposal would also depend heavily on the skills and efficiency of the team. However, given the team’s track record and the detail provided in their plan, they seem well-placed to handle these challenges.

Ref #121

Proposal: Runtime Upgrade v9420 on Polkadot Network

Details

This external referendum aims to upgrade the Polkadot network to runtime v9420, incorporating various changes from the v9370 to v9420 runtimes. Notable inclusions in this upgrade are four relay chain migrations and several features and changes that have been introduced since v9380.

Among the changes, the proposal highlights the incorporation of OpenGov on Polkadot. However, for OpenGov to function fully, an upgrade to the collectives parachain needs to be approved and enacted, leading to the creation of the Fellowship in the Collectives parachain. The runtime upgrade of the Collectives parachain is currently up for vote here.

The proposal details various changes to the relay chain, marked with either [S] for Security-related changes, or [P] for Performance-related changes. Some of the significant changes include introducing opengov into Polkadot, updating weights, enabling dispute slashes, adding host function tracing, fixing issues with pallet-balances, and others. Certain changes are still pending non-critical audits.

On the system parachain runtimes, this upgrade includes Cross-Consensus Message (XCM) v3 and a new runtime API to query account balances for all fungible assets. It does not include Non-Fungible Token (NFT) 2.0 or Foreign Assets for Statemint, but these will be part of an upcoming release.

The public referendum is currently up for vote, sequel to council approval.

Status: Passing

Results

Kusama

Ref. #192

Proposal name: Gigamind.app

Details

This proposal is for the funding of GigMind.app, a platform designed to operate within the Kusama ecosystem, allows users to create, engage in, and monetize various educational and recreational workshops or sessions. GigMind.app plans to foster learning and knowledge-sharing through interactive features such as real-time audio and video calls, quizzes, tests, and NFT 2.0 -based proof of achievements. The platform aims to provide a solution to challenges related to accessing quality education and training resources, bridging the gap between educators and learners.

GigMind.app is an open platform operating on the Rococo testnet, where anyone can create a session or post. A more exclusive platform, MasterSubstrate.app, which operates on the Westend testnet, allows only fellowship members to create and post. This platform is currently under development.

The app’s key features include real-time audio and video calls, user-created workshops, personalized learning experiences, and multilingual support. It also plans to offer NFT certification for knowledge validation. The platform is built as a progressive web app (PWA), making it mobile-friendly and easily accessible.

The platform is planned to be launched in several development stages or milestones: Research and Planning, Development and Testing, Beta Testing, Official Launch, and Post-launch Support. The requested treasury funds will be used for these development phases, marketing, community building, and the formation of partnerships within the ecosystem for long-term sustainability.

Status: Failing

Results

Ref. #194

Proposal name: Monitoring of public RPC/WSS Endpoints & Node Database Analytics

Details

This proposal by the ParaNodes team outlines an initiative to provide vital data relating to Database Sizing, Restoration, and RPC Endpoint Monitoring to address three gaps in the current ecosystem. It proposes two methods of execution, one involving renting all necessary hardware, and another that involves procurement of some servers.

The key aspects of the proposal include:

  1. Monitoring of node database sizes and growth rates, node database synchronisation times and the uptime & performance of WSS endpoints.

  2. Making the collected data available to the public via the ParaNodes website and Polkadot’s Official Wiki as live data.

  3. The team’s budget estimate for the project ranges between $71,515.50 and $85,375.50, depending on whether some servers are procured or all are rented.

  4. This proposal’s target audience includes current and potential infrastructure providers, end-users, and funders of WSS services.

  5. The solutions offered in the proposal aim to guide node operators in server hardware procurement, help in database restoration strategies, and provide an independent system to measure the uptime and performance of public RPC endpoints.

  6. The proposal also details about the team, comprising three individuals, all with extensive experience in IT and the Polkadot ecosystem.

The proposal suggests that this initiative could be beneficial for the treasury, operators, and the general public, assisting in better funding allocation, uptime visibility, and informed RPC selection, respectively.

Status: Failing

Results

Brief analysis

The Paranodes team proposal is essentially proposing to develop a holistic system to monitor the health and performance of public WebSocket Secure (WSS) nodes on the Kusama network. This includes monitoring node performance, ping times, database sizes, and restoration times across various database configurations. However, this proposal has elicited a mixed response from commentators, with the primary point of contention being whether such a monitoring system constitutes a judicious use of the Kusama treasury funds.

Staker Space, in their comments, posits that the proposal, while well-intended, may not offer a value-for-money return on the proposed investment. They note that the IBP network already has a similar monitoring tool in place, making this proposed system seem redundant. They also questioned the necessity of monitoring all public WSS nodes, suggesting this might only be of interest to a niche community within Kusama. Similarly, they also challenge the need to monitor database sizes and restoration times, given these metrics are not as volatile and could be recorded and updated periodically in a cheaper manner.

Paradox, counters these arguments by indicating the ongoing need for full nodes, despite the emerging trend of light clients. They suggest that, at least for the foreseeable future, the majority of Kusama’s community will continue to rely on full nodes. Hence, having a comprehensive monitoring system in place will be beneficial for the entire community. Paradox also alludes to the planned inclusion of monitoring for bootnodes and other critical node types at no additional cost, further enhancing the value of their proposed project.

From an analytical perspective, the debate seems to pivot on the utility versus cost argument. The Paranodes team’s proposal might offer significant value in ensuring the overall health and performance of the Kusama network, particularly given the current prevalence of full nodes. However, the perceived redundancy with the existing IBP network monitor presented counterarguments. Ultimately, the community needs to consider whether the increased resilience, reliability, and transparency that could come from such a proposal outweigh its cost and potential overlap with existing tools.

Ref. #198

Proposal name: OpenComm - The Communication Layer Of Web3 - Milestone 1

Details

Subsocial has proposed the integration of an “Open Communication Layer” for the Polkadot ecosystem, known as OpenComm, which includes the development of the GrillChat tool. The proposal, if successful, is expected to enhance the communication functionality of Web3 applications and promote user engagement and retention.

The core purpose of this integration is to eliminate the need for using Web2 services such as Discord and Telegram for communication, which Subsocial believes create friction for users. To ensure smooth user interaction, the OpenComm layer would enable features like in-app messaging, chats, and other social tools across different projects within the Polkadot ecosystem.

GrillChat, a proof of concept built with OpenComm, aims to provide a frictionless user experience with features including anonymous communication, easy integration, and free access for end-users. It eliminates the need for token transactions, wallet confirmations, or extensions, which are often seen as barriers in decentralized applications (dApps).

The proposal also involves integrating the Open Communication Layer into Sub.ID, which will provide a discussion space for Polkadot projects. Projects such as Astar, Kodadot, Moonsama, Zeitgeist, Polkassembly, RMRK, Ternoa, and Imbue have already shown interest in this solution.

This proposal has two milestones. The first milestone, currently in progress, includes the development of the base chat functionality, account generation, real-time updates for messages, integration with Crust Web3 Buckets for content storage, the first batch of UX improvements based on user feedback, and integration of various other tools and systems. The proposal plans to fund the completed Stage 1 retroactively, while Stage 2, expected to be completed in July 2023, will receive the proposed funds.

Future milestones will be mapped out based on community feedback and may include features like NFT avatars, embedding of web3 assets, NFT/token-gated chats, encrypted direct messages, off-chain posting, and support for various digital identities.

The proposal requests $72,640 in KSM, to be converted using the EMA-7 KSM price from Subscan on the submission day. The completion timeline is between April 2023 and July 2023.

Status: Failing

Results

Brief analysis

The OpenComm proposal by Subsocial represents a considerable leap forward for the Polkadot ecosystem, addressing a key gap in communication infrastructure for Web3 applications. By aiming to develop a frictionless, user-friendly communication layer for decentralized applications (dApps), Subsocial seeks to enhance the user experience and increase user engagement and retention. The proposed approach could significantly streamline user interaction, reducing the current reliance on Web2 platforms such as Discord and Telegram, which often prove to be a hurdle for seamless user experience in the Web3 environment.

The GrillChat tool, a proof of concept developed with OpenComm, embodies the core objectives of this proposal. By eliminating the need for token transactions, wallet confirmations, or extensions, GrillChat aims to provide a smooth user experience that parallels those of traditional social media platforms.

The proposal’s objective to integrate the Open Communication Layer into Sub.ID is particularly noteworthy. This integration could help foster a unified communication infrastructure across various Polkadot projects, potentially enhancing overall ecosystem cohesiveness. The interest expressed by several prominent projects in the ecosystem, such as Astar, Kodadot, and Zeitgeist, underscores the potential value and impact of the proposed solution.

However, the project isn’t without its risks and potential pitfalls. For one, the adoption of OpenComm across the Polkadot ecosystem will rely heavily on the successful implementation of the proposed features and the project’s ability to gain the trust and acceptance of users and developers alike. The new communication layer will also need to be resilient and secure against potential attacks to protect user data and maintain the integrity of communication across different dApps.

It is also crucial to note that Subsocial is requesting funding for both completed and in-progress work, with some of the requested funds meant to retroactively cover the already finished parts of the project. While it’s not uncommon to fund completed work, it’s essential for all stakeholders to understand this arrangement clearly.

Overall, while  adopting a new layer of communication may not be easy, the potential benefits to the Polkadot ecosystem could be significant. The OpenComm proposal represents a substantial step towards a more connected, user-friendly, and vibrant ecosystem.

On-chain non-treasury proposals

Polkadot

#Ref 121

Proposal name: Runtime Upgrade v9420 on Polkadot Network

Details

This external referendum aims to upgrade the Polkadot network to runtime v9420, incorporating various changes from the v9370 to v9420 runtimes. Notable inclusions in this upgrade are four relay chain migrations and several features and changes that have been introduced since v9380.

Among the changes, the proposal highlights the incorporation of OpenGov on Polkadot. However, for OpenGov to function fully, an upgrade to the collectives parachain needs to be approved and enacted, leading to the creation of the Fellowship in the Collectives parachain. The runtime upgrade of the Collectives parachain is currently up for vote here.

The proposal details various changes to the relay chain, marked with either [S] for Security-related changes, or [P] for Performance-related changes. Some of the significant changes include introducing opengov into Polkadot, updating weights, enabling dispute slashes, adding host function tracing, fixing issues with pallet-balances, and others. Certain changes are still pending non-critical audits.

On the system parachain runtimes, this upgrade includes Cross-Consensus Message (XCM) v3 and a new runtime API to query account balances for all fungible assets. It does not include Non-Fungible Token (NFT) 2.0 or Foreign Assets for Statemint, but these will be part of an upcoming release.

The public referendum is currently up for vote, sequel to council approval.

Status: Passing

Results

Ref #120

Proposal name: Runtime Upgrade for Collectives Parachain To v9420

Details

This referendum aims to update the Collectives system parachain to runtime version v9420, which features several significant changes from v0.9.41 to v0.9.42. Among these changes are four runtime migrations for the relay chain and other migrations included in runtimes since v9380, allowing for skipping over several runtimes.

One of the primary updates in this proposal is the introduction of XCM v3, a cross-chain messaging format that enables different blockchains in the Polkadot ecosystem to communicate with each other.

The proposal also introduces a new feature specifically for Collectives – the Technical Fellowship. The Fellowship is part of the launch of Open Gov on Polkadot, included in the Relay Chain runtime. It will manage its membership and referenda voting on the Collectives chain, with its decisions communicated to the Relay Chain via XCM messages.

Sequel to a successful council motion, this proposal is now up as a public referendum.

Status: Passing

Results

Kusama

Ref #195

Proposal name: Update `relayVrfModuloSamples` in Parachain Config

Details

Sequel to the approval of the referenda to Increase Parachain Validators to 250, this referendum proposes to lower the relayVrfModuloSamples to 6 in the parachain validation configuration.

This modification is made feasible due to the activation of the disputes protocol. In essence, the disputes protocol being live permits a more efficient allocation of resources in the validation process, thus allowing for this reduction in relayVrfModuloSamples. This change will likely result in an optimized parachain validation process on the Kusama network.

Status: Passing

Results

Governance metrics

Polkadot

Treasury status

The treasury is 2.2% down from last week USD-wise, and down 0.75% DOT-wise

Kusama

Treasury status

The Kusama treasury is 1.12% down from last week USD-wise, and down 0.06% KSM-wise

Trends, Insights and other news

Polkadot

Idea: Collective-based, Multi-Asset Treasuries

An idea was share on the Polkadot forum regarding how the treasury may evolve with respect to OpenGov, in response to issues that were identifies, namely treasury mismanagement and limitations associated with a single-asset treasury.

It was suggested that the treasury issues can be addressed by decentralizing decision making, drawing parallels to how Polkadot’s technical structure delegates information and functionality to the edges of the system (the parachains). It was recommended integrating this approach with new collectives emerging on Polkadot, such as the Technical Fellowship, the Ambassador Program, Polkadot Media, and Anti-Scam Team. Each of these collectives would have its own treasury, funded by the main Treasury which is populated by DOT inflation and transaction fees.

This approach provides more flexibility and transparency compared to the bounty mechanism, by allowing multiple privilege levels and the ability to change membership. This would also reduce the number of referenda presented to all token holders and allow experts elected by the network to make decisions in their domain of expertise.

Expanding the concept of a treasury was also suggested, proposing that there could be multiple accounts with treasuries across various chains, holding multiple assets, with logic dictating how these assets are spent.

Overall, the vision is to create a more decentralized, efficient, and flexible treasury system, where decision-making is pushed to expert groups, allowing for a broader focus on more significant issues. He also sees the benefit of having these groups manage their own budgets and assets across various chains to better meet their needs. The community is invited to provide feedback on these ideas in the forum post.