proposal

Untitled - motion #420

- This proposal is about Subscan, a tool that helps people understand the Polkadot network.
- Subscan needs money to keep running, which includes costs for servers, security, and staff.
- The proposal suggests using funds from the Polkadot treasury to pay for these costs from July to December 2022.
- They are asking for a total of $190,244 to help keep Subscan operating.
- This money will be converted to DOT, a cryptocurrency, based on a specific price on submission day.
- The proposal aims to support the growth of the Polkadot network.

proposalId

> This is a follow up proposal to what we submitted before:
[#151 Subscan | Infrastructure Costs of Subscan for Polkadot & Westend & Rococo Networks](https://polkadot.polkassembly.io/treasury/151)


**Overview**

Subscan is an essential block explorer and analytics tool for the Polkadot network, providing valuable insights to the Polkadot community. However, the maintenance and operation of Subscan requires a significant investment of resources, including server infrastructure, security, and personnel costs. Therefore, we propose reimbursing the operation and maintenance fee for Subscan from July to December 2022 from the Polkadot treasury to ensure its continuous operation and maintenance.

**Total**

We believe that this reimbursement proposal will help to ensure the continuous operation and maintenance of Subscan, and benefit the growth and development of the Polkadot network. This time, we plan to apply for a total of 190,244 USD in Polkadot, the amount of DOT will be converted based on the EMA7 price on the day of the official submission.

Billing details can be read [here](https://docs.google.com/document/d/13whK83g_MXYCfQ4WyJmQuM_aTclCGsB9Ww9Pq3lP6dY/edit?usp=sharing).



Subscan | Infrastructure Costs of Subscan for Polkadot & Westend & Rococo & Statemint & Rockmine  Networks (from July to December 2022)

- Polkadot Decoded’s main event will happen in Copenhagen at the end of June 2023.
- It is the biggest yearly conference about Polkadot and brings together many people interested in it.
- There will be a special event for Asia on July 15-16, 2023, in Shanghai, China.
- This China event will help the growing Polkadot community in Asia, especially in nearby countries.
- The event will have talks, workshops, and demonstrations in Chinese and English.
- Target audience includes business and technical decision-makers, developers, and Polkadot fans.
- The goal is to have 300-500 attendees, with many speaking slots and exhibition booths available.
- The event will be hosted by a Chinese agency experienced in organizing technology events.

Polkadot Decoded’s Flagship event will be held at the end of June 2023 at the Øksnehallen in Copenhagen. This is the biggest yearly conference focused on all things Polkadot. It brings together the Polkadot community, web3 enthusiasts, new/curious DOT holders, and builders to hear about developments in the Polkadot ecosystem. To align with the global Flagship event and continue the excitement with the regional focus at the strategic local markets of the Polkadot community, a grand satellite event covering the Asian region ( China, Japan, Korea, Singapore and the rest of SEA) will be held on July 15th and July 16th at Shanghai/China (exact location is TBD and the dates will align with the rest of the regional satellite events).

The 2023 Decoded China event will therefore create pivotal experience to the fast growing Polkadot China community and the nearby markets such as Korea, Japan, Singapore, Vietnam and the rest of SEA. The China satellite event will feature presentations, panels, workshops, demos and aligned regional events (i.e. regional hackathon), delivered in the language of Chinese or English. The latest update and news of the Polkadot ecosystem teams, Parity, the Web3 Foundation and the community KOLs from Asia will be shared. The event is focusing on the content curated for a higher-level and border audience, as well as for decision makers, investors, entrepreneurs and Web3 Medias.

The target audience will be crossing over all six of our target personas: Business Decision Maker, Technical Decision Maker, both from startups and Enterprises interested in Polkadot, Builders from teams in the Polkadot ecosystem, DOT Holders, Developer, Polkadot enthusiasts and supporters. Polkadot Decoded China aims to be a general assembly for all things Polkadot/Kusama happening in Asia with a main focus of the China market.

Along with one main stage with the presentations, demos, panels and flagship event (Decoded Copenhagen) highlight playbacks, 2023 Decoded China satellite event will have networking areas, private meeting areas, exhibition areas (for parachain and ecosystem teams) and one after-party to celebrate with the community. The China satellite event aims to have between 300-500 attendees, 25 speaking slots (presentations, demos, panels and Copenhagen highlight session playbacks are all included), 20 exhibition booths (for selected parachain teams and the Substrate-based ecosystem projects), and one Substrate job fair.

The 2023 Polkadot Decoded China satellite event will be facilitated and hosted by Aitijia’er, an event agency based in China, who produced the 2020 Web3 Form @ Shanghai (Web3 rebranded towards China due to the regulation concern) and 2022 Decoded China @ Hangzhou.

More details of the proposal, please see this link [here](https://docs.google.com/document/d/1gn64J66dlZLheQxNa1R19AOqdkyboxn1vHyUOD1rmPw/edit#)

Polkadot Decoded 2023 China (Satellite Event) July 15-16, 2023 in Shanghai China

- EasyA is asking for $104,000 to work on a project involving Polkadot, which is a blockchain system.
- They have successfully completed two important tasks called Milestones 1 and 2.
- They gathered feedback from developers to make challenges for learning and improving skills.
- They created a new design for Polkadot challenges to make them more engaging.
- Dates and locations for two hackathons have been set, and they invited developers to join.
- They are planning to encourage many people to build new projects on Polkadot before the hackathons.
- They shared a detailed report about their progress for everyone to see.

**Requested Allocation:** $104,000 

*DOT amount calculated via EMA7 on 6 June 2023 at GMT+0 1100hrs: 1 DOT ~ USD$5.235. USD$104,000 ~ 19,866.2846 DOT

**Proponent:** EasyA 5FQqvRHgBEUZG17qs9cNFH6ZSSVyAwhb7D6dKjGWb8xgKFkP


Hey Everyone!

We’re delighted to give a full update on our progress so far!

**Progress Summary**

In summary, we have now successfully achieved Milestone 1 and Milestone 2! We started by opening this educational opportunity to more parachains/projects and preparing the full content framework. We have now collected key feedback from developers and parachain/project teams and utilised it to create the content for the challenges. We have also created a totally new design and UX for the Polkadot challenges to make them stand out. We are in the very final stages of approving all the content to go live in the app for release. 

We’re super excited that on the IRL hackathons side, we have also finalised the hackathon dates and locations. We have been inviting key developer groups and Polkadot parachains to attend the hackathon and will be leveraging our connections with core blockchain clubs to ensure a brilliant pipeline of builders at the hackathons!

Our next step is to make a huge push to get everyone building on Polkadot in the run-up to the IRL hackathons. We’re currently working with the participating parachains/projects on a detailed social media and activations strategy!

**Full Progress Report**

We have written up the fully comprehensive progress report for Milestones 1 and 2 [here](https://docs.google.com/document/d/1tvSCM9w8fSKxUBgTIuXNbhrdNWZUzpQHtORZxtyVAKE/edit?usp=sharing) for the community!

**Milestone 2 Requested Allocation Breakdown**

We would therefore like to request our Milestone 2 allocation so that we can proceed to Milestone 3 (hosting the 2 hackathons). 

Details for this milestone were discussed in our original discussion post [here](https://polkadot.polkassembly.io/post/1585), with the precise milestone and allocation breakdown [here](https://docs.google.com/document/d/1oyip_eVdevsjijQQSkL_GPOE5YF-AEGgE_xhwCFLnt0/edit#bookmark=id.x3kscjjklocs). Our first milestone was approved (and second milestone request discussed) [here](https://polkadot.polkassembly.io/motion/353).

We're already seeing huge excitement around #60DaysOfPolkadot and can’t wait to see what everyone builds at the hackathons! See you there!

Milestone 2 Proposal: Polkadot Developer Hackathons and Crash Course for 1,000 Developers (#60DaysOfPolkadot)

- This is a follow-up proposal about funding RPC services.
- It aims to support development and maintenance costs.
- There is one main goal called Milestone 1.
- Milestone 1 includes running services in Sweden and Tunisia.
- In Q1 2023, the Polkadot RPC node had over 3 million requests daily.
- The Statemint RPC node had about 158,000 requests daily.
- The Westend RPC node had around 69,000 requests daily.

This is a [follow-up](https://polkadot.polkassembly.io/post/1535) proposal on what we submitted in mid-January earlier this year, to further fund the development of the RPC services and to cover the maintenance costs of them.

This new proposal includes one Milestone.

Milestone 1: Continue to run the Polkadot, Statemint and Westend RPC services on dedicated hardware, located at small independent co-location sites in Sweden and in Tunisia.


### Report from Q1 2023

- Our Polkadot RPC node served on average **3,065,667** requests per day and in total **275,910,030** during the last quarter. 
- Our Statemint RPC node served on average **158,022** requests per day and in total **14,221,980** during the last quarter.
- Our Westend RPC node served on average **69,447** requests per day and in total **6,250,230** during the last quarter.

Our full proposal can be [read here](https://docs.google.com/document/d/1v5kotmRSFE6nQQghbZwZlcPgeAvTKLC60KDnu4SO4R0/edit#).

Polkadot RPC services Dwellir Q2 2023

- A proposal is asking for money to support the Open Runtime Module Library (ORML) from November 2022 to April 2023.
- The ORML was created by the co-founders of Acala in late 2019.
- It helps fix problems and create useful features for developers.
- The ORML is designed to be used by many people, not just one group.
- Community members are invited to review the proposal and ask questions.
- The goal is to help developers in the Polkadot and Kusama communities.

This proposal (link to doc [here](https://docs.google.com/document/d/1ENh6IHUbcFjNR6Js0I7VzWV5xFQeepmqS4Eipz7gVio/edit)) is seeking payment to cover development and maintenance of the widely used Open Runtime Module Library between Nov 2022 and Apr 2023.

Community members, please kindly review the proposal and ask questions you may have, we are happy to address questions before moving onto next step.

**Context**: Open Runtime Module Library, or ORML, originally created by Acala's co-founders in late 2019. It is a collection of modules that Acala team created to solve issues that we encountered, to produce features that we wish existed, at the same time making it not specific to our chain but generic, so we can share them with our fellow developers in the whole Polkadot/Kusama community and help in some way.

Retroactive funding for ORML maintenance Nov 22 to Apr 23

- The proposal is called “Boosting Developer Adoption for Polkadot Ecosystem Projects.”
- It is made by Missing Link, a company that helps find workers for blockchain jobs in Europe.
- The goal is to help the Polkadot ecosystem by placing 15 Rust developers in various companies.
- They want to use funds from a treasury to pay for recruiting services.
- They are asking for a total of $360,000 to help with this project.
- The funds will be given in three parts, or tranches, as the project progresses.
- They believe this will help the Polkadot ecosystem grow by providing skilled developers. 
- The proposal is open for community feedback before it is officially submitted.

Our proposal is “Boosting Developer Adoption for Polkadot Ecosystem Projects” and we are sharing it before the official submission for community input and feedback.

We are Missing Link, an established brand in web3 recruiting in Europe, to provide these services. Missing Link has a track record of providing high-quality recruiting services to the blockchain industry, as you can see from the full proposal linked below.

As the Polkadot ecosystem continues to expand, it is critical that there are enough skilled developers to support the growth. **We propose to place a total of 15 Rust developers to different companies and projects within the Polkadot ecosystem through three milestones.** Companies who qualify and are in the Polkadot ecosystem can utilize the funds from this treasury proposal to receive recruitment services for Rust developers for their project.

In total, we are requesting three tranches of $120k USD for a total of $360k USD from the Polkadot treasury to fund this project, with each tranche being awarded before each milestone. We believe that this investment will have a significant impact on the Polkadot ecosystem, by ensuring that there are enough skilled developers to support the growth of the network.

Thank you for your consideration of this proposal and we have incorporated the community’s feedback before submitting this proposal on-chain.

[Here is the link to the full proposal](https://docs.google.com/document/d/1zON3bX38D1MXLjaIIdc0aioosxmbQ2IDlMSouM2TLHo) with all the relevant details, processes and qualifiers.

Treasury Proposal for Missing Link: Boosting Developer Adoption

**Sub.ID** is a web application launched in 2021 that helps users manage their Substrate addresses, balances, NFTs, and other assets in the Polkadot ecosystem. It has connected to 40 Substrate chains and has a dedicated vision and roadmap.

In 2022, a Kusama treasury proposal was approved, leading to the development of new features. A demo and report are available to see these features in action.

**Batch Two** proposals include:
- **Alternative balances view**: Token-centric views and multi-account support.
- **Accounts grouping**: Group management and default groups like 'Followers' and 'Favorites'.
- **Transaction history**: List and filter transactions using Subsquid integration.
- **P&L analytics**: Dashboard and charts for portfolio analysis with CoinGecko integration.
- **Automated quality assurance**: Testing frameworks for various aspects like balances, crowdloans, and NFTs.

The full proposal with costs is available for review, and feedback is welcome.

**Sub.ID [Proposal #2](https://docs.google.com/document/d/1BgLXyCFbpcCKvv_JTBCwLR_btvFOJ0H8YArBYk5yZ_w/edit?usp=sharing)**: Alternative balances view, Account grouping, Transaction history, P&L analytics, Automated quality assurance.

Launched in 2021, the [Sub.ID](https://sub.id/) web dapp was initially designed to provide quick and convenient access to all your Substrate addresses, balances, NFTs, and other assets in one place. It was built with the Polkadot ecosystem in mind and tailored to benefit its most active members. Since then, Sub.ID has been connected to 40 Substrate chains, gained substantial traction, and got its own dedicated vision and roadmap.

In September 2022, our previous Kusama treasury [proposal for Batch One](https://docs.google.com/document/d/1RElvy5RYhnNInwnGsjibedGLI3EeBoqqazKk6Syv13M/view) was approved as [Motion #548](https://kusama.polkassembly.io/motion/548), and in February 2023 we successfully delivered the proposed features. Please refer to our [demo](https://youtu.be/FZkva4Awv4s) and [read the report](https://coda.io/@subsocial/subid-reports) to see how they look and function, or visit [Sub.ID](https://sub.id/) to try it live.

We are looking to secure funding from the Polkadot treasury for the following community-oriented features:

BATCH TWO

* **Alternative balances view**
    * UX: token-centric views (table/cards/chart), multi-account view.
    * Logic: consolidated token balances, support of multiple accounts.
* **Accounts grouping**
    * UX: list of Groups, Group management, Account page, Account management in a Group, default ‘Followers’ Group, default ‘Favorites’ Group.
    * Logic: Group entity, Group and Accounts relations, ‘Followers’ Group. members.
* **Transaction history**
    * UX: list of transactions, transaction type cards, filters section.
    * Logic: Subsquid integration.
* **P&L analytics**
    * UX: P&L dashboard, P&L charts (portfolio/tokens), multi-account aggregated view.
    * Logic: CoinGecko integration, balance changes over time.
* **Automated quality assurance**
    * Integration testing framework, balances testing, crowdloan testing, NFT testing, and real-time integration testing.

Please review the full proposal with detailed description of the costs at [https://docs.google.com/document/d/1BgLXyCFbpcCKvv_JTBCwLR_btvFOJ0H8YArBYk5yZ_w/edit?usp=sharing](https://docs.google.com/document/d/1BgLXyCFbpcCKvv_JTBCwLR_btvFOJ0H8YArBYk5yZ_w/edit?usp=sharing) 

We would love to get your feedback.

Sub.ID Proposal #2: Tx history, Token-centric view, P&L analytics, and more

- A company called OnFinality asked for money to keep their public services running for different networks like Polkadot and Westend.
- They have a special service that helps people use high-quality data from these networks.
- In the first few months of 2023, they served over 4.3 billion responses to users.
- Their services help developers by providing important information and making sure everything works smoothly.
- They improved their system to add more storage automatically, so it doesn't break.
- They also worked with other companies to help more people join the Polkadot community.
- Their public API service had very high uptime, which means it was working almost all the time.
- You can learn more about their services and track their performance on their public pages online.

**Proponent:** 12mRyiCp9zdh1wEVW5gLLiFBxDPKks72rRXmSupyEK3VAMLf (OnFinality)

**Date:** 2nd May 2023

**Requested DOT:**  12,141.2773 (USD $64,834.42)

**Short description:** Ongoing costs for the running of high performance, scalable, and reliable public infrastructure for Polkadot, Statemint, Collectives, Westend, and Encointer.

**Full Report:** [Polkadot Q1 2023 Full Report/Proposal](https://docs.google.com/document/d/1T9LnHNap-81QswfQ2yur80rISJAPcHkVzQfc0U54PNM/edit?usp=sharing)

**Raw Data:** [Polkadot Data Q1 2023](https://docs.google.com/spreadsheets/d/1iJpJZlqeeLqMJgmk9zNT-RKx_h1HNbMkFs1PMNySOGk/edit?usp=sharing)

* * * * *

Original Motivation
===================

Over the last 3 months (January, February, and March 2023) we've provided a scalable free public API service so that everyone can access public pools of managed Polkadot, Statemint, Westend, Collectives, and Encointer nodes. This provides the following three outcomes:

-   Grow the ecosystem by reducing the barriers to entry to access a high performance nodes

-   Help scale existing projects in the ecosystem by providing reliable infrastructure services

-   Assist with the testing of all networks by providing valuable data back to the community on how nodes are running, what calls are causing errors, and where traffic is originating from

Service Details
===============

During Q1 of 2023, we've made a large number of stability improvements to our Ultimate API service to allow us to add a large number of new parachains over the last quarter as well as support for multiple chains outside of Polkadot.

For customers that do sign up for paid API keys, we've been adding more and more features to provide a better experience. Geolocation insights provide statistics about where in the world communities are to help influence decisions around where to expand infrastructure and to view the effectiveness of regional BD initiatives.  We can also now automatically upsize the storage on nodes to prevent the risk of any downtime.

Our customers are building cross-chain wallets, running some of the largest block explorers, and are indexing multiple networks - they've all benefited from these API access restrictions, improved monitoring, and the larger number of supported Polkadot chains.

Between 2023-01-01 and 2023-03-31 our Polkadot API service has:

-   Served a total of 4.3 billion responses

-   Accumulated over 50,000 GB of data egress 

-   The highest daily total was 62 million responses in a single 24 hour period for Polkadot only

-   Our rolling 7 day average at the end of this period was over 49 million responses each day

-   Westend had over 110 million API responses in the period

-   Statemint had over 102 million API responses in the period

-   All time totals for Polkadot is 97,192,546,788 (97 Billion) since November, 2020

-   At the end of this period the 90 day uptime for Polkadot, Statemint, Westend, Encointer and Collectives was 99.98%, 99.99%, 99.96%, 99.74%, 99.95% respectively

Enhancements
------------

Additionally, we are proud to have delivered some key service enhancements that benefit the Polkadot ecosystem in the last quarter. This includes:

-   [Auto Expand Storage](https://blog.onfinality.io/onfinality-developer-update-auto-expand-storage-for-dedicated-nodes/) - When the node's storage reaches 85% utilisation, the storage size will be automatically increased by 10%. Saves developers and devOps time on having to constantly check on and manually upgrade their node storage size

-   [Partnership with POKT network](https://blog.onfinality.io/onfinality-partners-with-pocket-network-to-unlock-access-to-unstoppable-infrastructure/) to bring in more external developers into the Polkadot ecosystem

-   [Geographical Insights](https://blog.onfinality.io/onfinality-adds-geolocation-insights-for-dapps-and-api-apps/) - API key owners can view statistics about where in the world your community are to help influence decisions around where to expand infrastructure and to view the effectiveness of regional BD initiatives

-   [Clarify our IP address handling](https://blog.onfinality.io/how-does-onfinality-deal-with-personal-information/) - OnFinality does not, and will never, correlate or link specific wallet addresses to the IP address or request origin making the RPC request

-   We're testing access to various unsafe methods like traceBlock and subscribeStorage that will help developers create applications that utilise XCM - contact us if you would like to be part of the beta

-   Reduced our exposure to any single cloud provider - Progressively migrated resources away from AWS to other cloud providers for lower cost and exposure.

-   Expanded our OnFinality for Startups Programme to support teams from the Substrate Builders Programme and Scytale Ventures

-   Added support for a number of new networks, including Ajuna, Unique, Clover, SORA, Composable Finance, Collectives, xx network, as well as Polygon, BNB, Fantom, Gnosis and Evmos from outside the ecosystem. OnFinality is a new one stop shop for all of your RPC needs from multiple ecosystems.

-   A variety of improvements to our health metric collection tools and automated recovery scripts to ensure our 99.9% SLA is exceeded.

-   Scale improvements to our team, processes, and systems to allow us to provide this same service to any  substrate team

You can always see live data on our API service on our public [status page](https://status.onfinality.io/) and [network analytics page](https://onfinality.io/networks).

**Full report can be read here:** [https://docs.google.com/document/d/1T9LnHNap-81QswfQ2yur80rISJAPcHkVzQfc0U54PNM/edit?usp=sharing](https://docs.google.com/document/d/1T9LnHNap-81QswfQ2yur80rISJAPcHkVzQfc0U54PNM/edit?usp=sharing)

OnFinality - High Performance Public Infrastructure (Q1 2023)

This is a proposal for four parachains to open HRMP channels with Statemint. Each channel opening consists of:

- A `forceTansfer` of 20 DOT from the Treasury to Statemint sovereign account.
- A `forceOpenhrmpchannel` from Statemint (1,000) to `ParaID`.
- A `forceOpenhrmpChannel` from `ParaID` to Statemint (1,000).

ParaIDs for each parachains requesting the channels and proposals requesting this by the parachain teams:

Litentry: 2,013
Composable: 2,019
Polkadex: 2,040
Zeitgeist: 2.092

Batch of HRMP Channels with Statemint

- Motion 410 is a new plan to create a special tool called a light client for Ethereum 2.0.
- This tool will work with all parachains in the Polkadot ecosystem.
- It will help Polkadot and Ethereum talk to each other, allowing people to share assets, data, and applications.
- The plan includes technical details based on official guidelines for how the light client should work.
- The proposal will need approval from the Council and then from the community to move forward.
- There is more information about costs and the team involved in the links provided.

**Motion 410** is now up for vote: an ambitious proposal aiming to implement a trustless Ethereum 2.0 light client as a Substrate Pallet, which will be compatible with all parachains in the ecosystem. Connecting Polkadot to Ethereum enables the interoperability between two of the largest and most established blockchain networks, allowing for the transfer of assets, data and applications across the two networks. The technical specifications for the Ethereum 2.0 Light Client Pallet are based on the  official Consensus Eth2 Light Client specs and encompass various aspects of the client, which can be reviewed on [the proposal’s contextual information](https://polkadot.polkassembly.io/motion/410): along with budget, team information and more. 
###
Please note that, given the allocation request, this proposal is submitted as an external motion: meaning if/after Council approves, the community will have the final decision in democracy module.
###
Treasury Proposal and Contextual Information: [https://polkadot.polkassembly.io/treasury/261](https://polkadot.polkassembly.io/treasury/261)

External Motion: Development of a trustless Ethereum 2.0 Light Client as a Substrate pallet

- This proposal extends the maintenance and support contract for the Polkadot Ecosystem from January 1, 2023, to March 31, 2023.
- The Polkascan Foundation provides infrastructure services and maintains open-source software for the Polkadot ecosystem.
- Their Python libraries are used by 213 GitHub repositories.
- Previous activity reports are available from October 2020 to the first quarter of 2023.
- The proposal includes links to the Social Contract Mechanism, the Python Libraries support contract, and the business plan.
- The Polkascan Foundation is ready to answer questions from the Polkadot Council.

Term: 1 January 2023 - 31 March 2023

This Treasury Proposal is an extension of our current maintenance & support contract with the Polkadot Ecosystem. The extension of the maintenance & support contract covers term: 1 January 2023 until 31 March 2023.

* [Current report that account for maintenance & support contract activities](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-2023Q1.md)

[Polkascan Foundation](https://polkascan.org) is a not-for-profit infrastructure service provider and maintainer of Polkadot ecosystem open source software, such as the Polkascan Explorer and Python libraries. The Python libraries were initially funded by Web3 Foundation grants, they have a generalized nature, suitable for adoption by any Python-based project in the broader Polkadot ecosystem. 

At the time of writing [213 Github repositories](https://github.com/polkascan/py-substrate-interface/network/dependents?package_id=UGFja2FnZS04OTc2NTczNTM%3D) are depending on our libraries.


Previous activity reports can be found here:

* [October 2020](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202010.md)
* [November 2020](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202011.md)
* [December 2020](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202012.md)
* [January 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202101.md)
* [February 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202102.md)
* [March 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202103.md)
* [April 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202104.md)
* [May 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202105.md)
* [June 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202106.md)
* [July 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202107.md)
* [August 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202108.md)
* [September 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-202109.md)
* [Quarter 4 2021](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-2021Q4.md)
* [Quarter 1 2022](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-2022Q1.md)
* [Quarter 2 2022](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-2022Q2.md)
* [Quarter 3 2022](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-2022Q3.md)
* [Quarter 4 2022](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-2022Q4.md)
* [Quarter 1 2023](https://github.com/polkascan/social-contract/blob/master/polkadot/treasury-proposal-008-report-2023Q1.md)

Links and further details:

* [The Social Contract Mechanism](https://github.com/polkascan/social-contract/blob/master/README.md)
* [The Social Contract for Maintenance & Support of Python Libraries](https://github.com/polkascan/social-contract/blob/master/polkadot/social-contract-002.md)
* [Business Plan](https://polkascan.org/wp-content/uploads/2022/03/Business-Plan-Polkascan-Foundation-v20220218.1030.pdf)

We will be available to answer the Polkadot Council's questions.

Continuation of Maintenance & Support for Python Libraries

- A proposal was made to improve trading for a project called Statemint by allowing fast and safe swaps for large amounts of money.
- The proposal asks for 74,785 DOT, which is about $495,000.
- It aims to help with payment processes, like giving out money for projects and salaries and managing funds for special needs.
- The current trading systems called Automated Market Makers (AMMs) can be slow and make it easy for others to interfere with trades.
- A new method called TWAMM (Time Weighted Automated Market Maker) is suggested to make it safer to trade large amounts without interference.
- The proposal includes plans for new tools, research, and security checks to ensure everything works well.
- The contact person for this proposal is William Freudenberger, and there’s a link to a discussion about it online.

**Proponent:** 12wWLUd5qMzLFGqBsMnHLVFeTuYJwuo5ygMAxuSywrBX1XSF

**Date:** 2023.03.30

**Requested DOT:**  74,785 DOT ($495,000)

**Contact:** William Freudenberger (william@k-f.co)

**Discussion Post:** [https://polkadot.polkassembly.io/post/1754](https://polkadot.polkassembly.io/post/1754)

---

The [ongoing discussion](https://forum.polkadot.network/t/statemint-update-roadmap/1200/) about automated market makers (AMMs) in the Statemint roadmap is mainly focused on improving the user and custodian experience by allowing small atomic swaps natively and making Statemint a central hub for asset deposits. This addresses important pain points by enabling transaction fees to be paid in non-native tokens and facilitating interaction with the entire asset variety of the ecosystem without requiring to run custom nodes or infrastructure.

However, we believe that one aspect has been overlooked: the slow swaps of large volumes, which can be easily front-run or sandwiched. This is particularly relevant in the context of trades proposed through governance for use cases such as
1. Paying out treasury grants, bounties or even [salaries](https://github.com/paritytech/substrate/pull/13378) in less volatile currencies (ie. stablecoins).
2. Enabling parachains to build a DOT reserve which can be used to acquire a parachain lease, pay XCM fees, or [increase availability cores](https://forum.polkadot.network/t/parachain-scaling-by-parablock-splitting/341) during times of high demand (once supported).
3. Governance deciding to invest part of the treasury into a token to diversify their treasury

What we need is the opposite of what a traditional AMM provides: atomic swaps with immediate execution, even in relatively illiquid assets. A governance vote is unable to time the market and is highly predictable. Therefore, executing such a transaction as a market order on an AMM is problematic, as it will be guaranteed to be front-run. A better solution is to "dollar-cost-average" over a long period of time making it harder for price manipulation to affect the purchase.

At Centrifuge, we have researched distinct approaches of how to achieve hard-to-front-run slower transactions. In our opinion, the most elegant solution is [TWAMM (Time Weighted Automated Market Maker](https://www.paradigm.xyz/2021/07/twamm). We are of the firm conviction that the implementation of this model represents the most efficacious approach for executing token swaps in the context of slower and passive procedures, such as governance.

TWAMM (Time Weighted Automated Market Maker) eliminates front-running vulnerabilities of traditional AMMs when executing large orders, especially in the context of passive procedures, such as governance. The proposed solution will be executed as a seamless extension to [pallet-asset-conversion](https://forum.polkadot.network/t/statemint-e-swap-discussion), thereby enhancing its capabilities as an embedded AMM.

The deliverables of the proposal contain the TWAMM-pallet,  associated runtime APIs, associated research for further optimizing and extending the pallet, a security audit of the pallet and a frontend.

The full proposal can be found [here](https://centrifuge.hackmd.io/Q4AZOW2WRPq7Q0Ti3ee8Og?view).

**EDIT**
* Link discussion post

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

- Dot.alert() is a project that helps people manage their digital money safely.
- They want to get funding of 7,654 DOT, which is around $41,402.
- This funding is for the second and third quarters of 2023.
- Dot.alert() has worked with the Polkadot Treasury before to cover costs for their operations.
- They have made plans with goals for the year.
- You can find more details about their proposal and past successes online.

**Proponent:** 12uokSRn2hmEWPZuzHK1xqnFxRgyoApLtXRBd4jFan2x2T1P

**Date:** 13.05.2023

**Requested:** 7,654 DOT (i.e USD $41,402 calculated from the [7-day EMA price](https://polkadot.subscan.io/tools/price_converter?value=41402&type=time&from=USD&to=DOT&time=1683944268) of DOT)

**Short description:**

[Dot.alert()](https://dot-alert.gitbook.io/dot.alert/) is a knowledgebase that provides practical guidelines for managing assets safely across the Polkadot ecosystem. 

As part of its mission, Dot.alert() has previously established a social contract with the Polkadot Treasury to fund its quarterly operational costs:

- Motion 263: [Treasury proposal: Dot.alert() operational costs](https://polkadot.polkassembly.io/motion/263)  |  [Q4 2022 Milestones report](https://docs.google.com/document/d/1xdOWf7m7MC9oul54q-I8bWRZ2b6zZGam/edit?usp=sharing&ouid=112859871373269428690&rtpof=true&sd=true)
- Motion 318: [ Treasury proposal: Dot.alert() operational costs - Q1 2023](https://polkadot.polkassembly.io/motion/318)  |  [Q1 2023 Milestones report](https://docs.google.com/document/d/1kMaSz59IVMfcfbu6BMml6eFfjpfs7K06/edit?usp=sharing&ouid=112859871373269428690&rtpof=true&sd=true)

Dot.alert() is seeking funding for its Q2 & Q3 2023 operations, so that it can continue to make progress on the objectives laid out in its annual strategic plan.

You can find the discussion related to this proposal here: [https://polkadot.polkassembly.io/post/1743](https://polkadot.polkassembly.io/post/1743)

You can find the full details of the proposal (including milestones, tasks, and costs for the period April – September 2023) here: [Polkadot Maintenance Proposal Q2-Q3 2023 – Dot.alert()](https://docs.google.com/document/d/1hyqtzlnTYQb5oBFop76n_PIWmaYgvI3v/edit?usp=sharing&ouid=112859871373269428690&rtpof=true&sd=true).



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

- Cervera is the creator of a YouTube channel called Cryptonitas.
- He started making educational videos for Polkadot and Kusama since April 19, 2021.
- Cervera helps the community by answering questions online and joining events.
- He organized a special event called Decoded 2022 in Valencia.
- The main goal of his work is to create a knowledgeable and helpful community.
- His new proposal aims to continue making over 85 pieces of content.
- He encourages everyone to read more details in his complete proposal.

Hi everyone! I'm Cervera, creator of [Cryptonitas](https://www.youtube.com/channel/UCsP0zGvvzB4RGyDYHkDdmUA), and I've been creating educational video tutorials for the Polkadot and Kusama community since April 19, 2021. In addition to creating educational content, I have been contributing to the community in different ways: supporting the community by answering questions on the Telegram channels and YouTube; through participation in different events (both as a speaker and as a member of the organizational team); with the creation of events, such as the Decoded 2022 viewing party in Valencia; and the creation of a Nomination Pool on both Polkadot and Kusama, among other things.

This proposal intends to continue the content creation of the [previous proposal](https://kusama.polkassembly.io/treasury/213), which includes the production of 85+ pieces of content. The main objective of this proposal is to have an informed, educated and valuable community that knows how to make real and appropriate use of the network. For more information, I invite you to read the complete proposal [here](https://docs.google.com/document/d/1gdjk6TH4nl6OA0MJe93Ok4uw6NcVVh8RXFfg8Gam2CE/edit?usp=sharing).

You can read the original discussion post [here](https://polkadot.polkassembly.io/post/1745).

Polkadot education content production extension by Cryptonitas

- Tommi, also known as Alice und Bob, creates educational content about Polkadot on YouTube.
- He developed a tool called Subscrape to help with tax reporting related to data on Polkadot.
- Tommi is building Polkalytics, a service that helps analyze Polkadot data similarly to Google Analytics.
- He wants to connect people working on data projects in the Polkadot ecosystem.
- He proposes to create a Github repository to list all data-related projects in Polkadot.
- A website will also be made to share this information in a clear way.
- Tommi is open to feedback to improve his project.

**Short description: To create a comprehensive overview of the current state of all things data in the Polkadot ecosystem. Funding includes the research, a Github repo, and a Website.**

Hi everyone. This is Tommi, aka Alice und Bob. You might know me from my YouTube channel [Alice und Bob](https://www.youtube.com/@alice_und_bob/videos), where I educate on the edge of edutainment and technology within Polkadot, or from [publicly talking about DeFi in Polkadot](https://www.youtube.com/watch?v=NGnD3LhpHEI) (and specifically [Mangata Finance](https://www.mangata.finance/), where I lead Growth) or from my [occasional tweets](https://twitter.com/alice_und_bob) on the bird app.

Early last year I did my taxes and started building [Subscrape](https://github.com/ChaosDAO-org/subscrape), a Python scraper for Substrate chain, to help me in the process. Over time, things became more serious and I started building [Polkalytics](https://polkaverse.com/10716/polkalytics-a-google-scale-analytics-service-for-polkadot-37079), a Google-scale analytics service for Polkadot. I have built an indexer for Polkadot that writes the complete chain into Google BigQuery and later derives additional tasks to create account reports for the purpose of filing taxes.

During my work, I discovered that there are A LOT of data-related projects in Polkadot, it's just hard to find them at first glance. I had great conversations with people from the Parity Data Team, Apexti, Subwallet, and Apillon, and think that all the people working on data in the ecosystem deserve to be much better connected so that we can make everyone's life easier.

Therefore this submission is a proposal to create a Github repository that contains a survey of the Polkadot Data Ecosystem and an accompanying website. A complete overview of everything that exists in terms of data in Polkadot.

In preparation for this proposal I opened a [discussion](https://polkadot.polkassembly.io/post/1726) and had conversations with the Parity data team, a Polkadot Wiki maintainer and a member from the Subwallet team. There were two primary requests: To publish the work as structured data and to publish the work as website. Therefore I have decided to follow both approaches, disseminate the data in a repo with structured data and then publish a website that embeds the structured data (which will also work as a proof of concept)

I am still open to any feedback and will work to integrate it if it is in line with the intention of this proposal.

[Polkadot Treasury Proposal - A Survey of the Polkadot Data Ecosystem](https://docs.google.com/document/d/1MNxSf6rWOt_z6D884K_QvQpxpwahavHwarA7M79JLmE/edit#)

A companion video for this proposal can be found [here](https://www.youtube.com/watch?v=qYlpLdnZ8gY).

Best,
Tommi

Proposal: A Survey of the Polkadot Data Ecosystem

- The proposal is to upgrade the Polkadot network to a new version called runtime v9420.
- This upgrade includes changes from earlier versions and has four migrations for the Relay Chain.
- A big part of this upgrade is adding something called OpenGov to Polkadot.
- For OpenGov to work, another proposal about collectives needs to be approved first.
- There are many improvements in the Relay Chain, such as new features and fixing some issues.
- This upgrade also helps developers by making it easier to see account balances.
- The proposal needs to be approved by the Council before the community can vote on it, which will take 28 days.

This proposal aims upgrade the Polkadot network to runtime [v9420](https://github.com/paritytech/polkadot/releases/tag/v0.9.42): the specific details on this upgrade please check the release notes. This runtime contains the changes from v9370 to v9420. Please note there are 4 runtime migrations for the Relay Chain in this release (details below). In addition to the migrations mentioned above, all the migrations included in runtimes since v9380 have been included in this release, allowing to jump over a few runtimes. 

- Call Hash: `0x0352127d49a9cb7794251a4caeb9c6b729444f1f40a9ebd2284dfbc168319363`
- Preimage is submitted.

### Relay Chain

Among other things, this proposal includes the inclusion of OpenGov on Polkadot. Note that, in order for OpenGov to be fully operational, [the proposal upgrading collectives parachain](https://polkadot.polkassembly.io/motion/403) needs to be approved and enacted (this is ongoing). If this happens, Fellowship will be created in the Collectives parachain. The Technical Fellowship is an integral part of OpenGov model.

#### Relay Chain Changes

- [S] ✅ audited [#12951](https://github.com/paritytech/substrate/pull/12951) Low - Deprecate Currency; introduce holds and freezing into fungible traits

- [S] ✅ trivial [#13287](https://github.com/paritytech/substrate/pull/13287) Low - Metadata v15: expose api to fetch metadata for version

- [P] ✅ trivial [#6897](https://github.com/paritytech/polkadot/pull/6897) Low - Update weights

- [P] ✅ audited [#6701](https://github.com/paritytech/polkadot/pull/6701) Low - Introduce opengov into polkadot

- [P] ⏳ pending non-critical audit [#5974](https://github.com/paritytech/polkadot/pull/5974) Low - Kusama: enable dispute slashes

- [S] ✅ trivial [#13558](https://github.com/paritytech/substrate/pull/13558) Low - Getcallindex trait

- [P] ✅ trivial [#6928](https://github.com/paritytech/polkadot/pull/6928) Low - Vstam1/xcm admin origin

- [P] ✅ trivial [#6937](https://github.com/paritytech/polkadot/pull/6937) Low - Inherent disputes: remove per block initializer and disputes timeout event

- [S] ✅ audited [#12287](https://github.com/paritytech/substrate/pull/12287) Low - Emit event when changing total locked value in pallet-balances

- [S] ✅ trivial [#13704](https://github.com/paritytech/substrate/pull/13704) Low - Frame: fix the referenda confirming alarm

- [S] ✅ audited [#13715](https://github.com/paritytech/substrate/pull/13715) ‼️ HIGH - Reward pool migration fix

- [S] ✅ trivial [#13648](https://github.com/paritytech/substrate/pull/13648) Low - Contracts: add host function tracing

- [P] ✅ trivial [#6846](https://github.com/paritytech/polkadot/pull/6846) Low - Proxy for nomination pools

- [P] ✅ trivial [#6980](https://github.com/paritytech/polkadot/pull/6980) Low - Tighter bound on asset types teleported so that weight is cheaper

- [S] ✅ trivial [#13702](https://github.com/paritytech/substrate/pull/13702) Low - [contracts] overflowing bounded deletionqueue

- [S] ✅ trivial [#13610](https://github.com/paritytech/substrate/pull/13610) Low - Refactor: inconsistent balanceconversion fn

- [S] ✅ trivial [#13798](https://github.com/paritytech/substrate/pull/13798) Low - Uniform pallet warnings

- [S] ✅ trivial [#13722](https://github.com/paritytech/substrate/pull/13722) Low - Implement #[pallet::composite_enum]

- [S] ✅ trivial [#13699](https://github.com/paritytech/substrate/pull/13699) Low - Deprecate v1 weights

- [S] ✅ trivial [#13835](https://github.com/paritytech/substrate/pull/13835) Low - removepallet migration utility struct

- [S] ✅ trivial [#13302](https://github.com/paritytech/substrate/pull/13302) Low - Metadata v15: add runtime api metadata

- [S] ✅ trivial [#13851](https://github.com/paritytech/substrate/pull/13851) Low - Fix fungible and fungibles set_balance return value

- [S] ✅ trivial [#13724](https://github.com/paritytech/substrate/pull/13724) Low - Contracts: add sr25519_verify

- [P] ⏳ pending non-critical audit [#6934](https://github.com/paritytech/polkadot/pull/6934) Low - Enable changing executor params through governance

- [P] ✅ audited [#6843](https://github.com/paritytech/polkadot/pull/6843) Low - Xcm: properly set the pricing for the dmp router

- [S] [#13779](https://github.com/paritytech/substrate/pull/13779) Low - Add freeze/thaw events and tests

- [P] [#6662](https://github.com/paritytech/polkadot/pull/6662) Low - Xcm: remote account converter

- [S] ✅ trivial [#13827](https://github.com/paritytech/substrate/pull/13827) Low - Pallet-democracy: do not request the proposal when scheduling

- [S] ✅ audited [#13936](https://github.com/paritytech/substrate/pull/13936) ❗️ Medium - Removes reportsbykindindex

- [P] [#7114](https://github.com/paritytech/polkadot/pull/7114) ❗️ Medium - Offences migration v1: removes reportsbykindindex

- [S] ✅ trivial [#13988](https://github.com/paritytech/substrate/pull/13988) ❗️ Medium - Pallet collective: fix genesis member sort order

- [P] ⏳ pending non-critical audit [#7098](https://github.com/paritytech/polkadot/pull/7098) Low - Xcm: implement a blocking barrier

- [S] ⏳ pending non-critical audit [#13932](https://github.com/paritytech/substrate/pull/13932) Low - Frame: inherited call weight syntax

- [P] ✅ trivial [#7150](https://github.com/paritytech/polkadot/pull/7150) Low - Update weights

### System Parachain Runtimes

This Polkadot system parachain upgrade includes changes since v9370, which has several major updates. For one, it includes XCM v3.

On Statemint, this does not include NFT 2.0 or Foreign Assets as the Statemine release does, although with the audits completed these will be in an upcoming release. It does include the new runtime API to [query account balances](https://github.com/paritytech/cumulus/pull/2455), which will return all the fungible assets (under the Balances pallet and both instances of the Assets pallet) that an account owns in a single RPC call. This should be particularly useful for front end developers.

### External Motion

Please note this proposal is submitted as an external motion: meaning after/if Council approves, this submission will be up for vote in referenda queue for the community to have the final decision. It is a general expectation, given the size of the upgrade, for the community to vote on this for a complete launch period (28 days). 

Make sure to vote at your convenience!

Runtime Upgrade v9420 on Polkadot Network

- The proposal is to upgrade the Collectives system to a new version called v9420.
- This upgrade includes important changes and improvements since version v9370.
- It introduces XCM v3 and the Technical Fellowship for managing votes and membership.
- The Fellowship will work with the Relay Chain to make decisions using messages.
- There are four runtime migrations for the relay chain included in this upgrade.
- The community will get to vote on this proposal after the Council approves it.
- For more details, you can check the linked release notes.

This proposal aims to upgrade Collectives system parachain to runtime [v9420](https://github.com/paritytech/cumulus/releases/tag/parachains-v9420): the specific details on this upgrade please check the release notes. This release contains the changes from v0.9.41 to v0.9.42. Please note there are 4 runtime migrations for relay chain on this release (details below), in addition to the migrations mentioned above, all the migrations included in runtimes since v9380 have been included in this release, allowing to jump over a few runtimes. Preimage is submitted:

`0x89902130dbc0b878d643e0367f5b9cc85c1b8ac80c4f6cceed9013491177da15`

This Polkadot system parachain upgrade includes changes since v9370, which has several major updates. For one, it includes XCM v3.

On Collectives specifically, this update includes the [Technical Fellowship](https://github.com/paritytech/cumulus/pull/2186). It corresponds to the launch of Open Gov on Polkadot, which is included in the Relay Chain runtime. The Fellowship will manage its membership and referenda voting on the Collectives chain, while sending its decisions (e.g. to whitelist a call for the `WhitelistedCaller` track) in an XCM message to the Relay Chain.

For specific PRs included on this release, please visit: [https://github.com/paritytech/cumulus/releases/tag/parachains-v9420](https://github.com/paritytech/cumulus/releases/tag/parachains-v9420). 

This proposal is submitted as an external motion: meaning if/after Council approves, the community will have the final decision via referenda queue. 

Make sure to review and vote at your convenience!

Runtime Upgrade for Collectives Parachain To v9420

- The Polkadot Community is proposing a tool to help experts and leaders get more people involved in voting and making decisions.
- This tool will make it easier for voters to understand proposals and participate in governance.
- The proposal includes forming a group of experts who will analyze and summarize the proposals for everyone.
- Voters will use a system where they can trust these expert reviews, which will save time and improve decision-making.
- There is a plan to reward these experts based on how helpful their analyses are to the community.
- The goal is to make Polkadot's governance stronger and more efficient by encouraging collaboration.
- Grabber is a platform supporting this initiative and is ready to engage more voters with its features.

Dear Polkadot Community! 
We are submitting a proposal for a governance incentivization tool, that helps incentivize experts and leaders within the community to boost governance engagement and voter activity.

**[Get the detailed Proposal here >>](https://docs.google.com/document/d/1go3e3yeuXN31nuDtqabvMr_LM70cdtTqXZT_WqsF0Ks/edit)**

### **Overview**
While the concept of cryptocurrencies can be considered validated, the concept of cryptocurrency governance is still evolving. The objective of “basic” cryptocurrency governance (as a decentralized management system for that particular cryptocurrency ecosystem) is to perform decentralized control over the process, support developments, and manage the ecosystem's existence. The main goal is to ensure the long-term sustainability, security, and adaptability of a network while increasing the wealth locked in the ecosystem and the holdings of its participants, which are directly connected to the ecosystem's overall wealth. “Basic” cryptocurrency governance refers to the “tactical” decision-making processes. It helps address critical issues such as protocol upgrades, funding for development, conflict resolution, and network security. Even at this level, governance encounters numerous issues and opportunistic behavior from users, such as fraud, Sybil attacks, vote borrowing, voting manipulation, and participants' opportunism, among others. 

Polkadot's governance model is designed to prioritize the growth and development of the platform's ecosystem, rather than focusing solely on partnerships or marketing. This strategic approach stems from Polkadot's L0 vision as a foundation for future Layer 1 (L1) blockchains and its Substrate framework, which simplifies the process of building and deploying customized blockchains (also platform).
We can refer to Polkadot governance as "builders" governance, which emphasizes the platform's commitment to nurturing and supporting the creation of a robust ecosystem. This type of governance fosters collaboration and innovation within the community by allocating resources from the treasury to projects that contribute to the platform's growth, enhance its functionality, or expand its capabilities. In essence, "builders" governance concentrates on strategic objectives rather than tactical ones, prioritizing the development and evolution of the ecosystem over merely maintaining its current state. This approach ensures that Polkadot continues to evolve and adapt, making it a more resilient and future-proof platform that can support a diverse range of blockchain applications and use cases.

Polkadot's governance requires voters to have deep expertise and take on significantly higher risks, both within the large ecosystem and the market as a whole. Additionally, due to the break in cause-and-effect relationships, voters must make decisions without the possibility of receiving feedback or personal benefits. Furthermore, voters must also lock up their funds in the process. This is an important aspect of the system, as it helps to ensure voters' commitment and alignment with the long-term interests of the ecosystem. 
[You can learn more about "builder" governance in our proposal >>](https://docs.google.com/document/d/1go3e3yeuXN31nuDtqabvMr_LM70cdtTqXZT_WqsF0Ks/edit#)

However, it can be confidently said that one of the biggest challenges of this type of DAO is the enormous amount of time that needs to be spent collectively on studying community proposals. If we assume that each proposal takes 5.5 hours for adequate study (the average time spent on studying a scientific paper by an expert), then 1000 voters will spend 5,500 hours on a single proposal (excluding those who could not handle it, did not study it, or did not vote).
Then 20 proposals will take up 110,000 hours. That is 68+ full-time experts working on this exclusively.
Hence, an obvious task is to reduce the time it takes for a community member to study one proposal. The organization and simplification, preferably with added interest, can be improved in the scheme of such governance.

There are several ways to lower the barrier to entry for studying proposals and increase the chances of engaging a voter:
- Train the required number of voters  
- Delegate votes to the most motivated members, who are ready to do deep research 
- Add formal proposal compliance analyses
- Provide volunteer analyses and reports.

[Each of these solutions has its pros and cons, and you can learn more about them by following the link >>](https://docs.google.com/document/d/1go3e3yeuXN31nuDtqabvMr_LM70cdtTqXZT_WqsF0Ks/edit#)


### **The ideal concept proposes the following solution**
Drawing from existing experience, we can create a decentralized group of competing experts who can generate reviews of proposals. Their work will significantly reduce the need for ordinary voters to deeply engage with proposals, as they will be able to prepare reports that allow for direct insight. Decentralization and competition will facilitate the formation of diverse opinions and prevent an unconstructive approach. Moreover, these experts can become vote delegates who are also in competition. This work should be minimally incentivized, as reviewers provide a public good.

### **Grabber incentivization challenge concept.**
To implement commitment, user reputation, and actual actions and delegation of allocations and payments, have a reputation system within the system. It will be able to collect and analyze experts in the system and commitment. Based on this reputational tool, collective incentivization can work: bounties will be allocated, for which different experts will compete. Users will be able to vote on whose impact was more useful to them, thereby distributing the bounty. The results of their voting will again generate on-chain events that will enrich the participants' reputations.
The general scheme of work will be as follows:

1. For each proposal, a research budget is allocated, which allows compensation for researchers' expenses (bounty). For this, an event with conditions is created in the system.
2. Researchers can register in the system and conduct research, uploading links to them in the interface. Research is done within a specific timeframe.
3. After that, the proposed posts are reviewed, and points are assigned. Together with the relevance of their experience, they receive accruals from the allocated fund. When considering the researcher's relevance, it is visible how often they vote/voted/parachain auctions/funds in the system, etc.
4. The experience of researchers improves with the number of payments they receive (this is also collected on-chain and displayed).
5. The result is deep, non-formal research from multiple authors, which significantly reduces the workload for the community.



### **Grabber: A tool with an experienced team and Polkadot traction.**

Team:
Dev: Experienced with RUST, WASM/EVM (DOT) smart-contracts, Polkadot.js, and Polkadot features.
Community: Well-connected in the Polkadot community, with existing DOT/eco communities event traction and a large existing community.

### **Battle-tested flow**

We already have:
1. User onboarding flow 
2. Community UI
3. Administration UI
4. Parachain-ready (EVM/WASM ready)

### **Interface sketches**

Track selection
![](https://ipfs.thirdwebcdn.com/ipfs/QmevBAAarxd4rTTCRySkXyhFPt4Ev6z1fbTshtHBWGoaNi/1.jpg)

Project selection
![](https://ipfs.thirdwebcdn.com/ipfs/QmevBAAarxd4rTTCRySkXyhFPt4Ev6z1fbTshtHBWGoaNi/2.jpg)

Project Interface
![](https://ipfs.thirdwebcdn.com/ipfs/QmevBAAarxd4rTTCRySkXyhFPt4Ev6z1fbTshtHBWGoaNi/3.jpg)

Voting “Back office” and “event” UX
![](https://ipfs.thirdwebcdn.com/ipfs/QmevBAAarxd4rTTCRySkXyhFPt4Ev6z1fbTshtHBWGoaNi/4.jpg)

The voting manager creates an event and provides all necessary info to Grabber through our “back office”. 
![](https://ipfs.thirdwebcdn.com/ipfs/QmevBAAarxd4rTTCRySkXyhFPt4Ev6z1fbTshtHBWGoaNi/5.jpg)

There are many competitions that can be managed
![](https://ipfs.thirdwebcdn.com/ipfs/QmevBAAarxd4rTTCRySkXyhFPt4Ev6z1fbTshtHBWGoaNi/6.jpg)

Results control 


User UX:

Users apply for the claim. To apply, they bind their source wallet (DOT) and their distribution wallet (Smart-contract based parachain wallet/EVM wallet). Grabber's system aggregates crowdloan and voting activity of the users and proposes to save it on-chain. (in the smart-contract based parachain).
![](https://ipfs.thirdwebcdn.com/ipfs/QmevBAAarxd4rTTCRySkXyhFPt4Ev6z1fbTshtHBWGoaNi/7.jpg)

Grabber front-end already supports major Polkadot/EVM wallets, detects extensions and helps these wallets receive new users (check grabber.network). Also additional popups added
![](https://ipfs.thirdwebcdn.com/ipfs/QmevBAAarxd4rTTCRySkXyhFPt4Ev6z1fbTshtHBWGoaNi/8.jpg)

### Grabber | Algem
- Fully qualified (scored) users found to fit all criteria requested by the company: 532
- Users registered in Grabber for event: >5100
- Verified their wallets in Grabber: >3100 (60.87%)
- Event registrations (on-chain): **2735**
- Impressions for event-related Tweets from [@Grabberofficial](https://twitter.com/grabberofficial): >20K
- Increase in the number of Algem’s followers after the event: 16.48%
- Grabber x Algem smart-contract: [https://blockscout.com/astar/address/0xC00ba642fbB807B6e7A45fDAC4D2061d961fd272](https://blockscout.com/astar/address/0xC00ba642fbB807B6e7A45fDAC4D2061d961fd272)

### Grabber | Astar
- Fully qualified (scored) users found to fit all criteria requested by the company: 148
- Users registered in Grabber for the event: >2100
- Verified their wallets in Grabber: >1420 (67.62%)
- Event registrations (on-chain): **957**
- Impressions for event-related Tweets from @Grabber :>41K
- Grabber x Astar smart-contract: [https://blockscout.com/astar/address/0x76d46248F66Afb7767BA7C449748550926908DC4](https://blockscout.com/astar/address/0x76d46248F66Afb7767BA7C449748550926908DC4)

[More numbers about this evets available in the Detailed Proposal: ](https://docs.google.com/document/d/1go3e3yeuXN31nuDtqabvMr_LM70cdtTqXZT_WqsF0Ks/edit)


### **Grabber's Potential Impact**

1. Better communication with the voters
2. Engaging the audience through the activation of existing KOLs and creating new ones 
3. Significant expansion of the voting audience
4. Easier onboarding for new voters and reactivation of those who dropped out
5. A platform for spreading the vote delegation system


**[Get detailed Proposal here. ](https://docs.google.com/document/d/1go3e3yeuXN31nuDtqabvMr_LM70cdtTqXZT_WqsF0Ks/edit)**

All the best, the Grabber team! 

Grabber, a tool that incentivizes experts and leaders within the community to boost governance engagement and voter activity.

- Integritee wants to create private transaction sidechains.
- These sidechains will work on Statemine and Statemint.
- The proposal includes two main phases of development.
- They aim to deliver a beta version of these sidechains.
- More information can be found in their blog.
- There is a discussion thread for talking about this proposal.
- A detailed proposal document is available for people to read.

Integritee proposes developing and deploying private transaction sidechains on both Statemine and Statemint. This proposal covers the first two phases we outlined in [our blog](https://medium.com/integritee/a-privacy-sidechain-for-all-polkadot-kusama-chains-1bb52dc9b0d7). The delivery will be operational beta sidechains. 

[Discussion thread on polkassembly](https://polkadot.polkassembly.io/post/1739)

[Detailed Proposal Document](https://docs.google.com/document/d/1W9OjcwHKYqKzA0wmobN5HMf1cyiF3AHmRMvLs1K2hLU/edit?usp=sharing)



Privacy Sidechains on Statemin*

- The Acala Foundation wanted to renew their parachain lease with a new parachain called 3336.
- They won the auction for this new parachain, but a bug in Polkadot stopped it from working properly.
- The plan is to swap the lease between Acala’s old parachain (2000) and the new one (3336).
- Creating the new parachain required special coding, which was difficult and took time.
- After winning the auction, they updated the new parachain's code, but a signal from the bug caused problems.
- The new parachain tried to work but failed, leading to an error because it wasn't set up correctly.
- Now, they need help from the relaychain to fix this issue.

Acala Foundation have registered para id 3336 and won a parachain slot auction by bidding with the intention to use the new lease to renew Acala para lease.

However, due to [bug in Polkadot](https://github.com/paritytech/polkadot/issues/7202), parachain 3336 can never produce valid block and therefore unable to perform lease swap action.

This proposal aims to perform lease swap between 2000 (Acala) and 3336 (parachain bid by Acala Foundation).

---

## Technical Details

In order to participate parachain auction, we need to register a parathread, which requires a genesis state and geensis wasm. However, it is time consuming to prepare those as the provided template project is not suitable for production usage and therefore we used a dummy wasm during registration.

Once we won the auction, we have created a new valid parachain wasm and use [`register.schedule_code_upgrade`](https://polkadot.subscan.io/extrinsic/15425400-2) and[ `register.set_current_head`](https://polkadot.subscan.io/extrinsic/15425407-2) to update the genesis wasm and genesis state for para 3336.

The state and wasm is correctly updated. However, there is an unexpected side effect. Due to bug [polkadot#7202](https://github.com/paritytech/polkadot/issues/7202), this set the upgrade go ahead signal. 

When the parachain is onboarded, the collator for para 3336 starts try to produce block but it failed with error:

`[Parachain] panicked at 'No new validation function found in storage, GoAhead signal is not expected', /home/build/.cargo/git/checkouts/cumulus-59522f43471fa161/a3d6cd4/pallets/parachain-system/src/lib.rs:396:21`

This is because parachain received the upgrade go ahead signal and expecting it is during the runtime upgrade process, which is not the case. This caused the inherent to panic.

It is not possible to rescue the parachain from this state without intervene from relaychain and therefore we proposed this propsoal.

Lease swap for Acala

- Polkadot Decoded is a big conference about Polkadot and will happen on June 28th and 29th, 2023.
- This year, it will take place in Copenhagen, Denmark, and will have online and in-person events.
- There will also be smaller events in the USA, Europe, Latin America, and China in July.
- The conference will feature presentations, panels, workshops, and discussions.
- The main audience includes business leaders, technical experts, developers, and Polkadot fans.
- The goal is to share important information and attract companies interested in Polkadot.
- More details about the event can be found in a linked document.
- This is the second request for funding to support the conference.

Polkadot Decoded is the Flagship conference and the the biggest yearly event focused on all things Polkadot. And it's back for its fourth edition on June 28th and 29th, 2023, with a fully hybrid experience of online and in-person events. Decoded aims to evolve into a general assembly for all things Polkadot/Kusama.

In 2023 we will come to Copenhagen, Denmark with an increased capacity and there will be simultaneous satellite events hosted regionally in the USA, Europe, LatAm and China in July. These satellite events are aimed to be regionally focused. Whereas the Flagship event will be globally focused.

The program line up will be featuring presentations, panels, workshops, demos, fireside and barcamp chats. We are focusing on curating content that is more high-level for a broader audience as well as attracting decision makers and enterprises into the room. The target audience will be crossing over all six of our target personas: Business Decision Maker, Technical Decision Maker, both from startups and Enterprises interested in Polkadot, Builders from teams in the Polkadot ecosystem, DOT Holders, Developer, Polkadot enthusiasts and supporters. Polkadot Decoded aims to be a general assembly for all things Polkadot/Kusama. However, we are mainly focusing on decision makers and enterprises.

Further information on the proposal, including milestones, budget, agenda, participants and more can be found under this [LINK](https://docs.google.com/document/d/15OgE-hsNGepFpN-xgLDG1x5cHWJ55ltYroMGHaQnYQM/edit?usp=sharing).

This is the 2nd tranche request. The first tranche has been discussed under #255 and approved with Motion #382.

Polkadot Decoded 2023, tranche 2/3 (June, Copenhagen, DK)

- A proposal called referendum 112 wants to increase the number of validators in Polkadot to 500.
- The community discussed this and thought it was a good idea, but suggested increasing the number of validators slowly.
- They proposed increasing to 400 validators first, by adding 5 every era.
- Core developers agree and see that increasing the number to 500 will lower the amount of DOT needed for each validator.
- They plan to first increase the count by 3 to reach 400 after 20 eras.
- This proposal is submitted by a group of validators and will need community votes after the Council approves it.

After the submission of [referendum 112](https://polkadot.subsquare.io/democracy/referendum/112), seeking to increase the validator active set to 500, the community discussed the possibility and the need of Polkadot increasing the validators set. 

Feedback from the proposals indicates two points:

- There's interest with increasing the number of validators of the active set **but with increments**;

- There needs to be some analysis on the effects of the increase to ensure there's no security concerns.

The results indicate that participating members would like to increase the active set to 400 with increments of 5 per era. They believe that this increase would not compromise the security of the chain and allow for natural (opportunistic) leveling as the set increases. Core developers have also agreed on similar increases by value: 

“With increasing to 500, the amount of DOT needed to acquire a validator will sharply reduce from 1.7 mDOT now, to just around 370 kDOT. We think this is overall unavoidable, but we would personally suggest first increasing to 400 and re-evaluate”

This proposal aims to increase the active set of validators by 5 per era, for 20 eras. The call also executes a one-time increase by 3 to reach 400 validators by the end of the 20 eras. Note that this initiative is submitted on behalf of a coalition of 1kvP validators.

- Preimage Hash: `0xbacad43f5467717cb1edfba6317524dc1d24fe3246afbe6a8cea7ed5fae1ba5f`
- Call data: [HERE](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fpolkadot-rpc.dwellir.com#/extrinsics/decode/0x1a0408070a0c010401000000014038000014000000fe070a14)

Please note this proposal is submitted as an external motion: meaning if/after Council approves, the community will vote in referenda queue for the final decision. 

Make sure to review and vote!

1kvP Validators Initiative: Increase Validators Active Set to 400

- There is a proposal called motion 383 for costs from March to August 2023.
- The original amount requested was 16,655 DOT.
- This amount was approved, but there was a mistake in the application.
- Instead of writing 16,655 DOT, 500 DOT was written by mistake.
- Now, they are asking for the remaining 16,155 DOT.
- They hope the additional amount can be approved quickly.
- They appreciate everyone's understanding and support.

This is a supplementary proposal for [motion 383](https://polkadot.polkassembly.io/motion/383).
In motion 383, we applied for a 2023/3-2023/8 operational cost of 16655 DOT, which was approved at the time. The details of the proposal can be found [here](https://docs.google.com/document/d/1oJjtkZD8mgv5vRpBh_aoGmWqWlLK9tomGhP8M9esMng/edit?usp=sharing). However, when we filled in the amount of application on chain, we mistakenly wrote 500 DOT instead of 16655 DOT. Therefore, we are applying again for the remaining 16155 DOT, and we hope that the rest of the amount can be voted through as soon as possible. We appreciate your understanding and support.

Treasury Proposal：A supplementary proposal for the 2023/3-2023/8 operating cost for the nonprofit organization Polkadot Ecology Research Institute

- RockX wants to provide free services to help the Polkadot community grow in 2023.
- They are asking for about $93,063 to support this project.
- RockX already offers free APIs for Polkadot and Kusama with up to 100,000 requests daily.
- They plan to add 3 new parachains every quarter until mid-2023, totaling 6 parachains.
- Developers can create up to 10 free API keys to help with their projects.
- RockX aims to make it easier for developers by providing tools and a dashboard for updates.
- They have been reliable since 2021, with 99.9% service reliability reported in late 2022.

**Proponent:** RockX Official

**DOT Account:** 14tm4js6PgrDGZttNzyy7CM4pnYiPu3LxxZDb1zhJWUc5Wpj

**Date:** 28/04/2023

**Requested allocation:** USD $93,063 (15,485 DOT)

**Proposal Summary:** Provide free RPC service for the community in 2023 across multiple parachains to encourage growth and development.

### **Project Summary**

RockX currently provides free APIs on Polkadot and Kusama up to 100,000 requests per day. However, we would like to accelerate the ecosystem’s growth by expanding our offering to eventually include free packages for more parachains.

With the Treasury’s support, we plan to add 3 Parachains every Quarter from the start of 2023 until mid-2023 for a total of 6, where we will evaluate the current ecosystem status and adjust our processes accordingly. After the initial 6 chains have been onboarded, we aim to conduct an open call with other parachains to understand levels of interest before submitting a new proposal to add more parachains. We will also expand our Polkadot node offering to include a free archive node solution.

In addition to free API requests, RockX also provides a developer-friendly portal that allows users to set up APIs across all supported chains with just a few clicks, reducing the complexity and set-up time drastically. Last but not least, developers can also subscribe to our blockchain maintenance dashboard so that they will be able to receive the latest blockchain update information about Polkadot and its ecosystem.

To support the development of the Polkadot ecosystem, RockX will be offering free plans for developers that include 100K requests per day (or 3 million requests per month) for each blockchain supported above. This will be sufficient for most developers and users. Developers can access this free API service by creating their own API Key on the RockX portal and using the provided tools to optimize their development efforts. Up to 10 API keys can be generated for free for each blockchain. If any customization is needed, RockX can also assist with setting up custom archive nodes or full nodes. Every quarter, RockX strives to improve and enhance our product offerings and infrastructure for developers in the Polkadot ecosystem, including front-end UI, connectivity, security, and reliability. New product releases can be found on RockX’s Twitter page.

In summary, we’re here to take on all the complexities of node operations and utilize economies of scale and scope to lower the developers’ barriers (time and money) to adoption.

**History & Reliability**

RockX has been providing RPCs for Polkadot and Kusama since Oct 2021 and has achieved service reliability of 99.9% for Q4 2022 ([Link](https://access.rockx.com/product/polkadot-blockchain-api-for-web3-builders)).

The duplicate Polkadot nodes setup and the automatic failover system ensure the stability of the Polkadot node. In case of a node failure incident or during the Polkadot mainnet upgrade period, the automatic failover system directs users' requests to a backup node, ensuring continuous network operation.

**Notable Recent Enhancements & Support:**

Q3/22

Upgraded analytics dashboard to provide users more visibility on API usage
Uploaded videos about "How to build on a blockchain with Access Node"
Launched IP whitelist, and origin whitelist feature to enhance user’s security when using the RPC services

Q4/22

Wrote blog post to introduce Polkadot staking. In this post, RockX delves into the details of how staking Polkadot works, and why it's important for the success and growth of the Polkadot network. RockX will continue to -create new and educational content across the Polkadot ecosystem
Launched maintenance notification dashboard to keep users informed as soon as possible on any blockchain upgrades
Launched an incognito mode that will not store user’s IP address or browser information to further protect user's privacy

Our full report including data and links can be viewed [here](https://docs.google.com/document/d/1QTP7xPki6CAar-X2Uey-yGOYprAIaru83mibcSlen5g/edit).

Our previous community post with feedback on this proposal can be viewed [here](https://polkadot.polkassembly.io/post/1630).

Council Motions